Bump to 0.3.0 and guard release tag/version drift - #25
Merged
Conversation
The v0.3.0 release built 0.2.0 artifacts because pyproject.toml was never bumped, so PyPI rejected the upload with "400 File already exists". Bump the version, and fail the build job up front when a release tag doesn't match the packaged version instead of letting it surface as an opaque error at upload time.
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
1 participant
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.
Why
The v0.3.0 publish run failed. Tests and
uv buildpassed, but the upload got:pyproject.tomlwas never bumped before the v0.3.0 tag was cut, souv buildproducedlokf-0.2.0.*and PyPI correctly refused to overwrite the existing 0.2.0 files. Nothing was wrong with the package itself.What
0.2.0→0.3.0(pyproject.toml+uv.lock, viauv version 0.3.0).buildjob inpublish.yml. On areleaseevent it compares the tag (minus thev) touv version --shortand fails immediately on mismatch, so a missed bump reads as "bump the version, merge, then re-tag" instead of an opaque PyPI 400 two jobs later. Skipped onworkflow_dispatch, which has no tag.Verification
uv run --group dev pytest -q→ 158 passeduv build→lokf-0.3.0.tar.gz,lokf-0.3.0-py3-none-any.whluvx twine check dist/*→ PASSED on bothv0.3.0, fails on a mismatched tagAfter merge
The existing v0.3.0 tag/release point at the un-bumped commit, so they get deleted and recreated at the merge commit to retrigger publish.