ci: Fix `Release` action failure due to change in `.asc` suffix
What changed, and why it matters
This is a one-line change to the project's GitHub release automation. It removes a command that renamed a checksum signature file. The change fixes a release-script failure caused by an earlier commit that already changed the output filename. There is no indication this affects running Lightning nodes, user funds, network security, or introduces any vulnerability.
No security action required. Treat as routine CI maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit removes mv release/SHA256SUMS.${{ env.version }}.asc${{ steps.gpg.outputs.keyid }} release/SHA256SUMS.${{ env.version }}.asc from .github/workflows/release.yml. The referenced prior commit (ea2f7607b8ff08c6312e09caab22e07f1d0853e7) changed the build script so the signed checksum file is already produced with the .asc suffix, making the rename step fail because the source file no longer exists. This is a CI/release-pipeline maintenance fix.
Changed components
.github/workflows/release.ymlInspect captured patch +0 / −1
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index b71af21e..989f088a 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -148,7 +148,6 @@ jobs:
sudo apt-get install -y lowdown
./configure
tools/build-release.sh --without-zip sign
- mv release/SHA256SUMS.${{ env.version }}.asc${{ steps.gpg.outputs.keyid }} release/SHA256SUMS.${{ env.version }}.asc
- name: Upload signed artifact
uses: actions/upload-artifact@v4
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.