Skip to content

Bump master to 0.4.0-dev, release policy follow-ups from 0.3.0 - #45

Merged
plebhash merged 2 commits into
2140-dev:masterfrom
plebhash:2026/10/master-0.4.0-dev
Oct 23, 2026
Merged

plebhash merged 2 commits into
2140-dev:masterfrom
plebhash:2026/10/master-0.4.0-dev

Conversation

@plebhash

Copy link
Copy Markdown
Collaborator

Bump master to 0.4.0-dev

master still said 0.2.1, which is older than the released 0.3.0. It tracks Bitcoin Core master, which becomes the 33.x branch and the 0.4.x crate line.

Bitcoin Core marks its own master as 32.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.md

Gaps found while releasing 0.3.0 (#39, #43):

  • Releases come from maintenance branches only. The checklist still offered master, but under the maintenance branch rules (doc: clarify backport policy, mention 32.x branch #36) every version line belongs to an N.x branch. master now carries the next line's -dev version and is never released.
  • Test against the Bitcoin Core release tag. CI builds the tip of Core's 32.x branch, which was already ahead of v32.0 when 0.3.0 was cut. 0.3.0 was tested manually against a v32.0 build. A 0.N.0 release also waits for that tag.
  • Publish from a clean checkout of the release tag. The 0.3.0 crate has no .cargo_vcs_info.json, so crates.io does not record its source commit.

The RELEASE_POLICY.md commit should be backported to 32.x afterwards. The version bump should not.

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).

@bit-aloo bit-aloo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! Thanks. ACK

@plebhash
plebhash merged commit 9397c0f into 2140-dev:master Oct 23, 2026
1 check passed
@plebhash
plebhash deleted the 2026/10/master-0.4.0-dev branch October 23, 2026 13:57
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants