docs: release notes for 2.0.2#15
Merged
Merged
Conversation
Add planning/releases/2.0.2.md — the verbatim GitHub Release body the tag-driven Release workflow will publish. Maintenance release: internal _collect_fixtures refactor, atomic-collision behavior on the error path, planning-convention adoption (repo-only). No public API change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Release notes for 2.0.2, added at
planning/releases/2.0.2.md. The tag-driven Release workflow publishes this file verbatim as the GitHub Release body when the2.0.2tag is pushed.Release scope (since 2.0.1)
_collect_fixturesseam extraction (internal refactor) + atomic collision on the error path. No public API change.Patch bump: no public API surface change;
expose/modern_di_fixturesignatures unchanged.Next step after merge
Tag
2.0.2on the merge commit and push it →just publish(version from$GITHUB_REF_NAME) publishes to PyPI, then the GitHub Release is created from this notes file.🤖 Generated with Claude Code