What the developer wrote
Authored by Nick Johnson
ci: run kani on LTS branches
What changed, and why it matters
This commit only changes the project's automated daily testing setup so that a verification tool called Kani also runs against an older long-term support branch (0.32.x) in addition to the main branch. It does not modify any library code, user-facing behavior, or security-sensitive logic. There is no indication this is a security fix or introduces a vulnerability.
No security action needed. Treat as routine CI maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates .github/workflows/cron-daily-kani.yml to add a matrix strategy that checks out either master or the 0.32.x branch before running the Kani model checker. It is a pure CI configuration change with no code changes to the rust-bitcoin crate itself.
Changed components
.github/workflows/cron-daily-kani.ymlInspect captured patch +5 / −0
diff --git a/.github/workflows/cron-daily-kani.yml b/.github/workflows/cron-daily-kani.yml
index 18191a5b..387ac396 100644
--- a/.github/workflows/cron-daily-kani.yml
+++ b/.github/workflows/cron-daily-kani.yml
@@ -9,10 +9,15 @@ jobs:
runs-on: ubuntu-24.04
permissions:
contents: read
+ strategy:
+ matrix:
+ # Run on master as well as LTS branches.
+ branch: [master, 0.32.x]
steps:
- name: 'Checkout your code.'
uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
with:
+ ref: ${{ matrix.branch }}
persist-credentials: false
- name: 'Run Kani on your code.'
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.