Update CI to inject bitcoin binary version and expected SHA256 into called workflows and actions, move tests up to bitcoin binary 31.1 (was 26.0) - #7700
Open
dhaney-stacks wants to merge 5 commits into
Conversation
dhaney-stacks
requested review from
aaronb-stacks,
brice-stacks,
cylewitruk-stacks and
federico-stacks
October 2, 2026 17:06
dhaney-stacks
force-pushed
the
main
branch
4 times, most recently
from
October 2, 2026 17:30
8a63492 to
abbe2f0
Compare
…alled workflows and actions, move tests up to bitcoin binary 31.1 (was 26.0)
… because 31.1 has a different fee estimation than 26.0
dhaney-stacks
force-pushed
the
main
branch
2 times, most recently
from
October 2, 2026 19:05
44b1c86 to
81f1d13
Compare
… in one place and reference it
dhaney-stacks
enabled auto-merge
October 2, 2026 19:37
Collaborator
Author
|
Note: I've gotta leave this in place until this PR merges, at which point I can delete it via another PR. I have fixed this "chicken and the egg" problem permanently by allowing an actor to specify the bitcoin binary version (and hash) when manually triggering cache builds off Details: |
|
coverage: 85.687% (+0.02%) from 85.668% — dhaney-stacks:main into stacks-network:main |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update CI to inject bitcoin binary version and expected SHA256 into called workflows and actions, move tests up to bitcoin binary 31.1 (was 26.0)
Applicable issues
N/A
Additional info (benefits, drawbacks, caveats)
Moving to bitcoin binary 31.1 keeps us current with our L1 provider code and ensures things are working as expected.
Note: I've gotta leave this in place until this PR merges, at which point I can delete it via another PR. I have fixed this "chicken and the egg" problem permanently by allowing an actor to specify the bitcoin binary version (and hash) when manually triggering cache builds off main which will allow us to upgrade in the future without having to do any weird stuff like this.
Details:
https://github.com/stacks-network/stacks-core/pull/7700/changes#diff-8cf7f1d9842e5c571ad948417fa7fa400504ef4bc5c02d6ac52233e5cf814b18R35-R42
Checklist
N/A