Increase version number after previous version was added to bitcoin core. Also update version history and documentation.
doc: Bump version number v7 -> v8 #241
pull ryanofsky wants to merge 1 commits into bitcoin-core:master from ryanofsky:pr/v8 changing 2 files +42 −19-
ryanofsky commented at 7:10 PM on January 21, 2026: collaborator
-
0ade1b40ac
doc: Bump version number
Increase version number after previous version was added to bitcoin core. Also update version history and documentation.
-
DrahtBot commented at 7:11 PM on January 21, 2026: none
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
Reviews
See the guideline for information on the review process.
Type Reviewers ACK Sjors If your review is incorrectly listed, please copy-paste <code><!--meta-tag:bot-skip--></code> into the comment that the bot should ignore.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
-
ryanofsky commented at 1:43 AM on January 22, 2026: collaborator
Note: a good followup for this PR would be to port willcl-ark's change https://github.com/bitcoin/bitcoin/pull/33623 from the 29.x branch to the 30.x and master branches, adding libmultiprocess and capnproto version information to the dependencies documents:
- ryanofsky force-pushed on Jan 22, 2026
-
Sjors commented at 8:21 AM on January 22, 2026: member
If I understand correctly 7.0-pre1 are all in Bitcoin Core 30.x, while 7.0 changes will go in 31.x, unless they're backported. So I guess we should have bumped the version earlier? Since the version is encoded in
MP_MAJOR_VERSIONwe can't retroactively adjust the tags.ACK 0ade1b40ac5ab2118bea580c12cbe16fae9d452f
I did not check the PR links to earlier subtree updates.
-
ryanofsky commented at 10:58 AM on January 22, 2026: collaborator
Thanks for the review!
Since the version is encoded in
MP_MAJOR_VERSIONwe can't retroactively adjust the tags.Exactly yes. I added the
v5.0-pre1tag when I wanted to tag a version betweenv4.0andv5.0and I added av7.0-pre1tag when I wanted to tag a version betweenv6.0andv7.0. This seemed less awkward than renumbering due toMP_MAJOR_VERSIONbeing present. In the future, it shouldn't be necessary to have any more-pretags as long as the version number is bumped consistently. When I initially created thev0..v7tags, I just didn't create enough of them and didn't leave space between them. - ryanofsky merged this on Jan 22, 2026
- ryanofsky closed this on Jan 22, 2026
-
Sjors commented at 11:23 AM on January 22, 2026: member
and didn't leave space between them.
Oh this brings back memories of BASIC line numbering...