Skip to content

Regenerate poetry.lock (fixes 2.0.0-rc3 release build) - #458

Open
bradyyie wants to merge 1 commit into
mainfrom
fix/relock-poetry-lock
Open

Regenerate poetry.lock (fixes 2.0.0-rc3 release build)#458
bradyyie wants to merge 1 commit into
mainfrom
fix/relock-poetry-lock

Conversation

@bradyyie

Copy link
Copy Markdown
Contributor

The 2.0.0-rc3 publish-release-at-pypi job fails at the Docker python_test_base stage:

pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock` to fix the lock file.

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.

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

codecov Bot commented Jul 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants