ci: build from the release tag, not branch HEAD#11
Merged
Conversation
hatch-vcs derives the version from git describe; on a manual re-run main can be ahead of the tag, producing a rejected dev/local version (0.16.2.dev1+g…). Check out refs/tags/<tag> before building so the exact release version is used.
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.
Re-dispatched publish built
0.16.2.dev1+g…(rejected by PyPI as a local version) because it checked out main HEAD, which had advanced pastv0.16.1. hatch-vcs needs to build exactly on the tag. Addsgit checkout refs/tags/<tag>before the build.