Correct the 0.6.0 release date - #26
Closed
tvanreenen wants to merge 1 commit into
Closed
Conversation
Owner
Author
|
Deferring this cosmetic date correction to later documentation work; it is not required to publish v0.6.0. |
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
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 this fixes
The 0.6.0 release-preparation PR merged on August 22, 2026, but its changelog heading still recorded August 21, when the release notes were drafted. This updates the heading to the actual release date before
v0.6.0is tagged and published.Why fix it before publishing
The changelog date should identify when users can obtain the release, and the repository's earlier entries follow that convention. Leaving the previous date would make the permanent changelog disagree with the Git tag, GitHub release, and PyPI publication history.
User impact
This is a one-line documentation correction. It does not change package code, version metadata, dependencies, supported runtimes, archive compatibility, or runtime behavior.
Verification
v0.6.0tag, GitHub release, or PyPI 0.6.0 publication exists yet.git diff --checkpasses.Release note
Once this correction is squash merged, the resulting exact
maincommit can be tagged asv0.6.0and used to publish the GitHub and PyPI releases.