CI: don't run configure on *host* for release.
What changed, and why it matters
This is a routine fix to the project's automated release build script on GitHub. It removes an unnecessary step that installed a documentation tool and ran a configuration script on the build host. The change only affects how release binaries are produced internally and does not change any code that users run.
No security action required. Treat as a normal CI/maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies .github/workflows/release.yml, removing a ‘Prepare base environment’ step that installed lowdown and ran ./configure on the GitHub Actions host. The build-release.sh check requiring lowdown was already removed, so this step was redundant and caused failures when host configuration detected missing libsodium. No application source code, network protocol, cryptography, or wallet logic is changed.
Changed components
.github/workflows/release.ymlInspect captured patch +0 / −6
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 989f088a..73a03c1b 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -68,12 +68,6 @@ jobs:
- name: Git checkout
uses: actions/checkout@v4
- # tools/build-release.sh requires lowdown
- - name: Prepare base environment
- run: |
- sudo apt-get install -y lowdown
- ./configure
-
- name: Build environment setup
run: |
distribution=$(echo ${{ matrix.target }} | cut -d'-' -f3)
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.