Update versioning scheme#2562
Merged
Merged
Conversation
hawkw
approved these changes
Jun 16, 2026
hawkw
left a comment
hawkw
left a comment
Member
There was a problem hiding this comment.
thank you for taking this on <3
emilyalbini
force-pushed
the
ea-versioning
branch
from
3096a74 to
ed34ebf
Compare
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
2 participants
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.
This PR updates Brussels and the release workflow to support the proposed versioning scheme in RFD 705 (tl;dr moving the version number to the minor number rather than the patch, to support backports). The new "Custom version number" field in the release workflow will allow both to migrate to the new versioning scheme, and to issue patch releases (where we'll want to bump the patch number rather than let Brussels bump the minor number).