Skip to content

Commit uv.lock, enforce it in CI, and fix PyPI publish version bug#501

Merged
dknowles2 merged 1 commit into
mainfrom
fix/commit-uv-lock
Jun 26, 2026
Merged

Commit uv.lock, enforce it in CI, and fix PyPI publish version bug#501
dknowles2 merged 1 commit into
mainfrom
fix/commit-uv-lock

Conversation

@dknowles2

Copy link
Copy Markdown
Owner

Summary

  • Commits uv.lock and enforces it stays in sync with pyproject.toml in CI
  • Fixes the PyPI publish workflow: actions/checkout defaulted to a shallow clone, which prevented 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 rejected with a 400 Bad Request. Added fetch-depth: 0 so the full history (and tags) are available.

Test plan

  • CI passes on this branch
  • Next PyPI release run succeeds with the correct version string

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>
@dknowles2 dknowles2 force-pushed the fix/commit-uv-lock branch from 7ec1e70 to d4196c0 Compare June 25, 2026 17:29
@dknowles2 dknowles2 merged commit 40bd3c7 into main Jun 26, 2026
12 checks passed
@dknowles2 dknowles2 deleted the fix/commit-uv-lock branch June 26, 2026 03:41
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.

1 participant