release: fold pending changes into the unreleased 0.3.0 section - #59
Merged
Conversation
0.3.0 was version-bumped and documented but never tagged or published: GitHub and PyPI still show v0.2.0 as latest. Changes merged since the 0.3.0 prep landed under a fresh Unreleased heading instead of joining it. Since nothing has shipped as 0.3.0 yet, fold those entries into the existing 0.3.0 section rather than cutting a separate release for them.
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.
Summary
0.3.0 was version-bumped and its CHANGELOG section written in #47, but no tag or GitHub Release was ever cut for it — GitHub and PyPI still show v0.2.0 as latest. Changes merged since then (including #57/#58) landed under a fresh ## [Unreleased]\ heading instead of joining the pending 0.3.0 section.
Since nothing has shipped as 0.3.0, this folds those Unreleased entries into the existing 0.3.0 section and updates its date, instead of minting a separate release for them. No code changes.
Verification