Completes the final steps immediately prior to branching:
- Bump version to 31.99
- Update bips.md
- Remove release note fragments
Completes the final steps immediately prior to branching:
Add 327, 328, 373, and 390
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | ryanofsky, davidgumberg |
If your review is incorrectly listed, please copy-paste <code><!--meta-tag:bot-skip--></code> into the comment that the bot should ignore.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
Possible typos and grammar issues:
<sup>2026-03-06 21:29:42</sup>
ready for review, branching soon(tm)
Code review ACK 48b952cbb67e4a59e1f036375240bbb23ae21648
ACK https://github.com/bitcoin/bitcoin/commit/48b952cbb67e4a59e1f036375240bbb23ae21648
Not a big deal, but it would be nice to use the same PR title format as the ones used for 30 (https://github.com/bitcoin/bitcoin/pull/33347) and 29 (https://github.com/bitcoin/bitcoin/pull/32041):
"build: bump CLIENT_VERSION_MAJOR to 31"
As a reviewer who is unfamiliar with the release process, my first step is to search for what was done in previous releases. I see that this PR does more than just bump the CLIENT_VERSION_MAJOR, so maybe just in the commit message or somewhere in the PR description (this comment will probably do :) )
feel-free-to-disregard-nit: forgotten colon in 1b3d58f128a5b917b9b33d255e2cd77a3f6188cf commit message
Milestone
31.0