Repository navigation
chore(release): v0.9.0 - #72
Merged
Merged
Conversation
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.
Summary
Release v0.9.0. In
CHANGELOG.md, the Unreleased section becomes[0.9.0] - 2026-10-22, a fresh empty Unreleased section goes on top, and the compare links are updated.Why 0.9.0 (MINOR): there are new features since v0.8.0 and nothing that breaks.
Main changes
The project stores its version only in tags, so there is no version file to bump.
Type of change
Checklist
CHANGELOG.mdupdatedNotes for the reviewer
After the merge I tag the merge commit
v0.9.0, and the Release workflow builds the binaries and creates the GitHub Release.