docs: record the 25.5.1 release in the changelog - #9
Open
blaipr wants to merge 1 commit into
Open
Conversation
25.5.1 is tagged, published on PyPI and released on GitHub, but every entry describing it still sits under Unreleased, so the file offers no way to tell what shipped from what is waiting for the next release. The entries are unchanged; they move under a version heading dated the day the release went out, and Unreleased stays at the top for what comes next.
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
25.5.1 is tagged, published on PyPI and released on GitHub on 2026-08-17, but the changelog still carries every entry describing it under
## [Unreleased]. There is no way to read the file and tell what shipped from what is waiting for the next release, which is the one job the Unreleased section has.This adds a
## [25.5.1] - 2026-08-17heading under an empty## [Unreleased]. No entry text changes; everything currently listed is in the released tag, and nothing else is.Merge order note: #6, #7 and #8 each add an entry under
[Unreleased]. Whichever of them lands after this one needs its entry moved down into the new[Unreleased]section, which I will take care of.Type of Change
Component
Documentation (
CHANGELOG.md).Checklist
pytest tests/unit): 351 passed, unaffectedblack --check ascenderkit tests setup.py,flake8 ascenderkit)Unreleased: not applicable, this is the changelog itself