AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

Merge rust-bitcoin/rust-bitcoin#7003: Fix creusot cache by running on push to `master`

Public commit record

What the developer wrote

Authored by Andrew Poelstra

100/100 · Strong
Merge rust-bitcoin/rust-bitcoin#7003: Fix creusot cache by running on push to `master`

8f9a6dec87f84c5b125b144b8d6144d8437af5cb Fix creusot cache by running on push to `master` (Martin Habovstiak)

Pull request description:

According to the [documentation], PRs don't get to share their cache for security reasons which severely limits its usefulness to us. They can however restore the cache of the base branch which solves the issue but to have any cache on base branch we have to run Creusot on push.

This commit enables the cache on pushes to `master`. It is expected that this will require a full re-build but all subsequent builds which do not modify the dependencies should get faster.

[documentation]: https://docs.github.com/en/actions/reference/workflows-and-actions/dependency-caching#restrictions-for-accessing-a-cache

Adding P-high label because not having this wastes a lot of time on every PR and fills our cache storage.


ACKs for top commit:
apoelstra:
ACK 8f9a6dec87f84c5b125b144b8d6144d8437af5cb; successfully ran local tests
jamillambert:
ACK 8f9a6dec87f84c5b125b144b8d6144d8437af5cb


Tree-SHA512: e7bc82bd71d8e5f8851aa247b051b745301f43f7aa7fdd1e58dbf944849d4722e045eb538502136fccb7d18c522cd177c10b29c32cea05c90c5a65824c4dcc7f
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This change simply tells GitHub to run the Creusot verification workflow whenever code is pushed to the master branch, in addition to running it on pull requests. The goal is to populate a build cache for the master branch so that future pull requests can reuse it and run faster. There is no change to the actual Bitcoin library code, no bug fix, and no security patch.

Recommended action

No security action needed. This is a CI optimization. Reviewers may verify the workflow trigger does not introduce unintended permissions, but permissions are already set to {} (none).

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.