ci: add explicit git ref for prerelease
What changed, and why it matters
This is a one-line change to the project's GitHub Actions CI workflow. It adds an explicit git reference (the previous commit SHA) when running pre-release checks, so the check can run correctly after a pull request is merged into the master branch. There is no change to the Rust library code, no security fix, and no vulnerability.
No security action needed. This is a routine CI maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies .github/workflows/rust.yml. The prerelease job command is changed from cargo rbmt prerelease to cargo rbmt prerelease --baseline ${{ github.event.pull_request.base.sha || github.event.before }}. This supplies a baseline git ref for the rust-bitcoin-maintainer-tools prerelease action when github.event.pull_request.base.sha is unavailable post-merge, falling back to github.event.before. It is purely a CI configuration convenience.
Changed components
.github/workflows/rust.ymlInspect captured patch +1 / −1
diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml
index 3d0b460a..f4302db0 100644
--- a/.github/workflows/rust.yml
+++ b/.github/workflows/rust.yml
@@ -58,7 +58,7 @@ jobs:
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
+ run: cargo rbmt prerelease --baseline ${{ github.event.pull_request.base.sha || github.event.before }}
# Non cargo-rbmt jobs manage their toolchain version directly.
Prepare:
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.