doc: Bump version number v7 -> v8 #241

1. 
   ryanofsky commented at 7:10 pm on January 21, 2026: collaborator

   Increase version number after previous version was added to bitcoin core. Also update version history and documentation.
2. doc: Bump version number

   Increase version number after previous version was added to bitcoin core. Also
   update version history and documentation.

   0ade1b40ac
3. 
   DrahtBot commented at 7:11 pm on January 21, 2026: none

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   Reviews

   See the guideline for information on the review process.

   Type	Reviewers
   ACK	Sjors

   If your review is incorrectly listed, please copy-paste <!–meta-tag:bot-skip–> into the comment that the bot should ignore.

4. 
   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:

   • https://github.com/bitcoin/bitcoin/blob/29.x/doc/dependencies.md#optional
   • https://github.com/bitcoin/bitcoin/blob/30.x/doc/dependencies.md#optional
   • https://github.com/bitcoin/bitcoin/blob/master/doc/dependencies.md#optional
5. ryanofsky force-pushed on Jan 22, 2026
6. 
   ryanofsky commented at 1:54 am on January 22, 2026: collaborator

   Updated 34c3d043b5b0ca04909ef5361779e8924239e04e -> 0ade1b40ac5ab2118bea580c12cbe16fae9d452f (pr/v8.3 -> pr/v8.4, compare) to fix llm typos
7. 
   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_VERSION we can’t retroactively adjust the tags.

   ACK 0ade1b40ac5ab2118bea580c12cbe16fae9d452f

   I did not check the PR links to earlier subtree updates.

8. 
   ryanofsky commented at 10:58 am on January 22, 2026: collaborator

   Thanks for the review!

   Since the version is encoded in MP_MAJOR_VERSION we can’t retroactively adjust the tags.

   Exactly yes. I added the v5.0-pre1 tag when I wanted to tag a version between v4.0 and v5.0 and I added a v7.0-pre1 tag when I wanted to tag a version between v6.0 and v7.0. This seemed less awkward than renumbering due to MP_MAJOR_VERSION being present. In the future, it shouldn’t be necessary to have any more -pre tags as long as the version number is bumped consistently. When I initially created the v0..v7 tags, I just didn’t create enough of them and didn’t leave space between them.

9. ryanofsky merged this on Jan 22, 2026
10. ryanofsky closed this on Jan 22, 2026

    ---

11. 
    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…

Contributors
ryanofsky DrahtBot Sjors