Regenerate poetry.lock (fixes 2.0.0-rc3 release build) - #458
Open
bradyyie wants to merge 1 commit into
Open
Conversation
pyproject.toml changed (jsonschema >=4.23 in the test group, agentspan-testing -> conductor-agents-testing plugin rename) without re-locking, so the release image build fails the lock-hash check: 'pyproject.toml changed significantly since poetry.lock was last generated' This broke the 2.0.0-rc3 publish-release-at-pypi job.
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
v1r3n
approved these changes
Jul 30, 2026
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 2.0.0-rc3 publish-release-at-pypi job fails at the Docker
python_test_basestage:pyproject.toml was changed after the last lock regeneration (jsonschema >=4.23 added to the test group; pytest plugin renamed agentspan-testing -> conductor-agents-testing) without running
poetry lock. Poetry validates the lock content-hash before any install, so every release build from a tag containing this state fails.This PR contains only the regenerated lock (+19/-19, mechanical). Verified locally with
poetry check --lock.After merge: cut 2.0.0-rc4 targeting this commit to re-trigger CD.