Repository navigation
Bump master to 0.4.0-dev, release policy follow-ups from 0.3.0 - #45
Merged
Merged
Conversation
master tracks Bitcoin Core master, which will become the 33.x branch and the 0.4.x crate line. It still said 0.2.1, older than the released 0.3.0. Use a pre-release version so it is never picked up by ^0.3 or ^0.4 requirements, mirroring Bitcoin Core's 32.99.0 on master.
- master is never released, and carries a -dev pre-release of the next line. - A release is cut from the maintenance branch that owns the line, and tested against the matching Bitcoin Core release tag. CI builds the Core branch tip, which can be ahead of the tag. - Publish from a clean checkout of the release tag, so the crate records its source commit (0.3.0 was published without .cargo_vcs_info.json).
plebhash
added a commit
that referenced
this pull request
Oct 23, 2026
- master is never released, and carries a -dev pre-release of the next line. - A release is cut from the maintenance branch that owns the line, and tested against the matching Bitcoin Core release tag. CI builds the Core branch tip, which can be ahead of the tag. - Publish from a clean checkout of the release tag, so the crate records its source commit (0.3.0 was published without .cargo_vcs_info.json). Github-Pull: #45 Rebased-From: bf1358c
plebhash
added a commit
that referenced
this pull request
Oct 23, 2026
[32.x] Backport #45 release policy
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
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.
Bump master to
0.4.0-devmasterstill said0.2.1, which is older than the released0.3.0. It tracks Bitcoin Coremaster, which becomes the33.xbranch and the0.4.xcrate line.Bitcoin Core marks its own
masteras32.99.0. The crate equivalent,0.3.99, would match^0.3, so this uses a pre-release instead. Cargo only resolves pre-releases when they are requested explicitly.RELEASE_POLICY.mdGaps found while releasing
0.3.0(#39, #43):master, but under the maintenance branch rules (doc: clarify backport policy, mention 32.x branch #36) every version line belongs to anN.xbranch.masternow carries the next line's-devversion and is never released.32.xbranch, which was already ahead ofv32.0when0.3.0was cut.0.3.0was tested manually against av32.0build. A0.N.0release also waits for that tag.0.3.0crate has no.cargo_vcs_info.json, so crates.io does not record its source commit.The
RELEASE_POLICY.mdcommit should be backported to32.xafterwards. The version bump should not.