What the developer wrote
Authored by Nick Johnson
ci: drop unused prerelease step
This step isn't used and messing with the post-merge job.
What changed, and why it matters
This is a routine cleanup of a GitHub Actions CI workflow. It removes one unused 'git fetch' step that was reportedly causing problems after code merges. There is no change to the actual Bitcoin library code, no security fix, and no vulnerability.
No security action needed. Treat as normal CI hygiene.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit removes a single step from .github/workflows/rust.yml that fetched the master branch into the CI runner. The pre-release check now relies on the existing checkout (fetch-depth: 0) and the baseline SHA passed to cargo rbmt. This is purely a CI maintenance change with no effect on the rust-bitcoin crate’s logic, API, or attack surface.
Changed components
.github/workflows/rust.ymlInspect captured patch +0 / −2
diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml
index 62af540a..29207412 100644
--- a/.github/workflows/rust.yml
+++ b/.github/workflows/rust.yml
@@ -54,8 +54,6 @@ jobs:
with:
persist-credentials: false
fetch-depth: 0 # History required for version bump detection.
- - name: "Fetch master branch"
- run: git fetch origin master:master
- uses: rust-bitcoin/rust-bitcoin-maintainer-tools/.github/actions/setup-rbmt@64715bab0d6fa1f3ebd6f9be336c4c5089bb5eb9
- name: "Run pre-release checks"
run: cargo rbmt prerelease --baseline ${{ github.event.pull_request.base.sha || github.event.before }}
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.