Commit uv.lock, enforce it in CI, and fix PyPI publish version bug#501
Merged
Conversation
actions/checkout defaults to a shallow clone, which prevents setuptools_scm from seeing git tags. This caused the publish job to build a bogus dev version (0.1.dev1+g<sha>) instead of the real release version, which PyPI then rejected with a 400 Bad Request. Fetching full history lets setuptools_scm compute the correct version. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
7ec1e70 to
d4196c0
Compare
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.
Summary
uv.lockand enforces it stays in sync withpyproject.tomlin CIactions/checkoutdefaulted to a shallow clone, which preventedsetuptools_scmfrom seeing git tags. This caused the publish job to build a bogus dev version (0.1.dev1+g<sha>) instead of the real release version, which PyPI rejected with a 400 Bad Request. Addedfetch-depth: 0so the full history (and tags) are available.Test plan