docs: add 2.1.0 release notes#16
Merged
Merged
Conversation
Notes for the 2.1.0 release (action_scope feature + planning-convention adoption). Read verbatim as the GitHub Release body by release.yml when the 2.1.0 tag is pushed. 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.1.0, read verbatim as the GitHub Release body by
release.ymlwhen the2.1.0tag is pushed.Version rationale
Last published is
2.0.3.action_scopeis a new, additive, backward-compatible public API → minor bump to 2.1.0 (semver).Headline
action_scope(ctx)— resolveScope.ACTIONdeps without injectingContainer/build_child_container()by hand (#15).@injectalways builds + stashes the per-command container onctx.meta; adopted the planning-convention; 100% coverage on 3.10–3.14.Cutting the release (after merge)
The release is tag-driven. Once this merges to green
main:git tag 2.1.0 && git push origin 2.1.0release.ymlthen runsjust publish(PyPI first, irreversible) and creates the GitHub Release usingplanning/releases/2.1.0.mdas the body.🤖 Generated with Claude Code