Repository navigation
build(ci): publish the protocol as agentenv-framework-protocol on the CircleCI index too - #28
Merged
Merged
Conversation
… CircleCI index too The CircleCI publish renamed the protocol distribution back to agentenv-protocol and pinned the framework to that name, so the package had one name on PyPI and another there. Both jobs now publish the same metadata: agentenv-framework-protocol, with agentenv-framework pinned to its exact version. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
earakely-scale
requested review from
a team and
polakamtejas
as code owners
September 30, 2026 21:02
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
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.
The CircleCI
publishjob uploads to a second package index alongside PyPI. Until now it renamed the protocol distribution back to its former name,agentenv-protocol, and pinnedagentenv-frameworkto that name, so the same package had two names depending on where it was installed from.This drops both rewrites. The CircleCI job now builds the same metadata as
publish-pypi.yml:agentenv-framework-protocolagentenv-frameworkpinned toagentenv-framework-protocol==<its version>I checked this by running the two edited steps on a copy of
mainand reading the wheels'METADATA:Name: agentenv-framework-protocol(0.1.270), andRequires-Dist: agentenv-framework-protocol==0.1.270onagentenv-framework0.9.1255.For installs from that index. From this release on, pin
agentenv-framework-protocol==instead ofagentenv-protocol==. Both distributions install the sameagentenv_protocolpackage, so never pin both. Before upgrading an existing environment across this release, runpip uninstall -y agentenv-protocol(or use a fresh one). Otherwise both distributions stay installed, and uninstalling the old one later deletes the new one's files. PyPI installs are unaffected.Labelled
bump-version: the merge cuts the first release published under the new name on both indexes.🤖 Generated with Claude Code
This PR appears safe to merge; the two CodeArtifact packages now use matching protocol names.
What we checked:
Summary
CircleCI now publishes the protocol as
agentenv-framework-protocoland pinsagentenv-frameworkto that package’s exact version. This matches the package names used by the PyPI publishing workflow.Reviews (1) · Last reviewed commit: "build(ci): publish the protocol as agent..."