Skip to content

Conversation

@pcarleton
Copy link
Member

Summary

  • Change uv sync --locked to uv sync --frozen in the release workflow's publish-pypi job

The release script bumps the version in pyproject.toml, which causes uv to complain that the lockfile is out of sync (uv includes the package's own version in the lockfile).

Using --frozen skips the lockfile freshness check while still using the pinned dependency versions from the lockfile.

Test plan

  • Re-run the release workflow after merging

🤖 Generated with Claude Code

pcarleton and others added 2 commits December 18, 2025 16:19
When the release script bumps the version in pyproject.toml, it needs
to also regenerate the uv.lock file. Otherwise the lockfile becomes
out of sync and `uv sync --locked` fails in CI with:
"The lockfile at uv.lock needs to be updated"

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
The release script bumps the version in pyproject.toml, which causes
the lockfile to be out of sync (uv includes the package's own version
in the lockfile). Using --frozen skips the lockfile freshness check
while still using pinned dependency versions.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@pcarleton pcarleton merged commit c7d60d6 into main Dec 18, 2025
23 checks passed
@pcarleton pcarleton deleted the fix-release-uv-lock branch December 18, 2025 16:25
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.

3 participants