Repository navigation
Take the package version from the git tag - #11
Merged
Merged
Conversation
shuckc
force-pushed
the
version-from-tag
branch
2 times, most recently
from
November 9, 2026 21:30
ea9e2e6 to
c60da3c
Compare
The version was read from rollingmill/__init__.py, so the 0.1.1 release built a 0.1.0 wheel and
PyPI rejected it ("File already exists"). hatch-vcs now derives the version from the tag, so the
package no longer defines __version__: nothing used it, and the installed version is available
from importlib.metadata. The publish workflow fetches full history so the tags are present.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
shuckc
force-pushed
the
version-from-tag
branch
from
November 9, 2026 21:31
c60da3c to
ce25de1
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.
Problem
The PyPI publish for the `0.1.1` release failed: the tag built a `0.1.0` wheel because the version was hard-coded in `rollingmill/init.py`, and PyPI rejects re-uploading an existing version.
Change
Verification
Release note
The existing `0.1.1` tag/release points at a commit without this change. After merging, delete and recreate the `0.1.1` release on the new `main` (nothing was ever published as `0.1.1`), or release as `0.1.2`.
🤖 Generated with Claude Code