chore: 2.1.2 — republish from current main (recover from ghost 2.2.1) - #23
Merged
Conversation
The previous 2.1.1 + accidental-cwd 2.2.1 publishes both built from a pre-merge commit (aa8a810, source-byte-identical to 2.1.0). This bump tags the post-merge commit (e494560) so the published 2.1.2 sdist actually reflects the version metadata. Source code is unchanged from 2.1.0/2.1.1 (idna 3.13 -> 3.14 was lockfile-only and lockfiles aren't shipped in the sdist), so no consumer behavior change. After 2.2.1 is yanked, pip install agentscore-py will resolve to 2.1.2. Co-Authored-By: Claude Opus 4.7 (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.
Summary
Recovers the version line after the cwd-error v2.2.1 ghost. Both v2.1.1 and v2.2.1 publishes built from pre-merge commit `aa8a810` (source-byte-identical to 2.1.0). This bump tags the post-merge commit `e494560` so the published 2.1.2 sdist actually reflects what its version metadata claims.
Why
After 2.2.1 is yanked + this PR is merged + tagged: `pip install agentscore-py` resolves to 2.1.2.
Test plan
🤖 Generated with Claude Code