docs(changelog): close 0.3.1 for release - #54
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
1 participant
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.
Why
0.3.1 is the first release that exercises the automatic cask bump end to end. The changelog has to name the version before the tag is cut, otherwise the entries stay under Unreleased with no release to belong to.
What
Renames
## [Unreleased]to## [0.3.1] - 2026-08-31. No other change — the app binary is identical to 0.3.0, this release carries the CI and documentation work only.Verification
Tag
v0.3.1is pushed right after this merges; the release workflow and thebump-caskjob are what this release is meant to prove.