chore(changelog): open 0.0.17 instead of an Unreleased bucket - #402
Merged
Conversation
An Unreleased heading defers the versioning decision to whoever cuts the release, long after the person who understood the change has gone. In practice it just accumulated: ten PRs merged above this section while it stayed empty. A bare version number with no date says the same thing and forces the decision at the moment of the change. The missing date is what marks it unreleased, so releasing means adding a date rather than renaming a section and moving entries.
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
Replaces the
## Unreleasedchangelog heading with## 0.0.17, the next release.Why
An
Unreleasedbucket defers the versioning decision to release time, so it gets made by whoever cuts the release rather than the person who understood the change. It also accumulates silently: ten PRs merged above this section while it stayed empty, which turns release prep into archaeology throughgit log.A bare version number with no date carries the same meaning and forces the decision while the change is fresh. The missing date is what marks it unreleased, so releasing is adding a date rather than renaming a section and migrating entries.
Entries for the ten PRs already merged since 0.0.16 are still written at release time as usual; this only changes where they land.
Verification