chore: record 0.3.0 in the changelog on main - #50
Open
RobertoIskandarani wants to merge 1 commit into
Open
Conversation
Rename the released notes to their 0.3.0 section header (matching the v0.3.0 tag byte-for-byte) and open a fresh Unreleased section, so the next release cut starts from a clean slate.
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.
What
Renames the released notes on
mainto their## [0.3.0] - 2026-07-24section header — a byte-for-byte match of the section in thev0.3.0tag'sCHANGELOG.md— and opens a fresh## [Unreleased]section above it.Why
When 0.3.0 was cut, the record-on-main step was skipped, so the released notes still sit under
## [Unreleased]. Left as-is, the next release cut would fold the already-shipped 0.3.0 notes into the next version's section.Two-line, docs-only change.