Repository navigation
chore(release): prepare 2.5.4 for publication - #120
Merged
Merged
Conversation
Changelog-Plan: f1ac95ca1d4f12adaffe71dc1a4460b6ec9736928064e02872a438dc7169d186 Changelog-Base: b230ea1 Changelog-Output: 98ac2234480873232b2bf026af4f074a988495b0ed7e788aaf422102dcd5fe5f Changelog-Options: 068128a44150e29cb35f86e11ce479fd10c34efc262f07c0ed7e771846cc7a09
Contributor
Author
Changelog✅ Contribution check passed. Head: Base: Contribution: 0 new valid fragment(s). Policy: managed-version. |
This was referenced Oct 20, 2026
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
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.
Prepare release 2.5.4.
Plan:
f1ac95ca1d4f12adaffe71dc1a4460b6ec9736928064e02872a438dc7169d186Base:
b230ea1e7305a8a5a18d04c6583649bf27276334Consumed fragments: 1
Updates the changelog and removes the consumed fragments.
Preparing this PR does not publish a tag or release.
After the approved merge, the full lifecycle publishes its tag and GitHub release by default.
An explicit
publish: falsecreates neither; later plans still continue from the consolidated history.Older consolidations without publication are not published retroactively.