script: Add Fedora as target for SHASUMS verification
What the developer wrote
Authored by ShahanaFarooqui
script: Add Fedora as target for SHASUMS verification
What changed, and why it matters
This commit simply adds 'Fedora' to the list of Linux distributions whose release binaries are checked against published checksums during the release verification script. It is a build-process expansion, not a code change, and introduces no security vulnerability.
No security action required. Treat as normal build/maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In tools/build-release.sh, the ALL_TARGETS variable inside the VERIFY_RELEASE=true branch is changed from ‘bin-Ubuntu’ to ‘bin-Fedora bin-Ubuntu’. This causes the release verification step to also look for Fedora release artifacts when validating SHA256SUMS. The change is one line, affects only release verification logic, and does not alter cryptographic checks, network behavior, or wallet/node code.
Changed components
tools/build-release.shInspect captured patch +1 / −1
diff --git a/tools/build-release.sh b/tools/build-release.sh
index 4789db66..d1b9fa41 100755
--- a/tools/build-release.sh
+++ b/tools/build-release.sh
@@ -117,7 +117,7 @@ echo "Parallel: $MAKEPAR"
if [ "$VERIFY_RELEASE" = "true" ]; then
if [ -f "SHA256SUMS-$VERSION.asc" ] && [ -f "SHA256SUMS-$VERSION" ]; then
- ALL_TARGETS="bin-Ubuntu"
+ ALL_TARGETS="bin-Fedora bin-Ubuntu"
else
echo "Unable to verify. File SHA256SUMS-$VERSION or SHA256SUMS-$VERSION.asc not found in the root."
exit 1
Why this scored 17/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.