chore(release): date the 1.1.6 changelog entry#34
Merged
Conversation
The 1.1.6 entry in HISTORY.rst still read `(unreleased)` because it was not dated before the release tag was cut. Set it to the release date so the tagged changelog is accurate.
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
The
1.1.6entry inHISTORY.rststill read(unreleased).It was never dated before the release tag was cut,
so the tagged changelog would have shipped as "unreleased".
Set it to
1.1.6 (2026-07-13), matching the dated style of every prior entry.Why now
The
v1.1.6tag was cut, then deleted (the release run was cancelled before it was greenlit — nothing published to PyPI).Once this merges,
v1.1.6will be re-cut on the merge commit so the released changelog is accurate.