chore: bump python_runtime __init__.py to 0.34.0 (publish-fix)#85
Merged
Conversation
The 0.34.0 release tag failed publish.yml's version-lock check — clients/python/src/agent_eval_rpc/__init__.py still had the 0.32.0 fallback string (the in-process __version__ when the installed package metadata isn't available). The workflow asserts this matches the npm version. Bumping in lockstep.
tangletools
approved these changes
May 22, 2026
Contributor
tangletools
left a comment
There was a problem hiding this comment.
Verified — 1-line fix to unblock publish.yml's lockstep version check. The python runtime's init.py version fallback was 0.32.0; publish refused to ship 0.34.0 with a mismatched python runtime. Now aligned.
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.
0.34.0 release tag failed publish.yml's version-lock check —
clients/python/src/agent_eval_rpc/__init__.pystill had the0.32.0fallback string for__version__when the installed package metadata isn't available. The workflow asserts this matches the npm version.Pure 1-line bump. After merge, the v0.34.0 tag needs to be re-pushed (or workflow_dispatch'd) to retry the publish.