docs: label the new changelog section 0.0.38, and record 0.0.37 - #49
Merged
Conversation
I filed the language-policy changes under v0.0.37. That version was published on 2026-08-14, before any of them - the CI dev build for the merge commit is already named 0.0.38, which is the version they actually ship in. v0.0.37 itself had no changelog section at all; its release notes came from pull request titles. A stub records it so the file does not silently skip a published version.
Xerolux
marked this pull request as ready for review
August 20, 2026 11:44
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
2 participants
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.
Correcting a mistake in #48.
I filed the language-policy changes under
## v0.0.37. That version was published on 2026-08-14, before any of them — so the section described changes that are not in the release it names. The CI dev build for the merge commit is alreadyv0.0.38-dev.43b03bf, which is the version they actually ship in.Two fixes:
pyproject.tomlstays at 0.0.37: the release workflow computes the next version itself from the last tag (auto-patch), which is where the 0.0.38 dev build came from.28 language-policy tests still pass.
Generated by Claude Code