Skip to content

Conversation

@PhoenixBound
Copy link
Contributor

This is required for now because of how setuptools_scm relies on tags and the number of commits since that tag (via git describe, I guess) to determine the version number string. (Without that info, the version will be named "0.1.dev1+g(hash)" every time, possibly even for actual releases.)

A more efficient solution may be possible in the future; see actions/checkout#249 and pypa/setuptools-scm#480

I've pushed the official v4.2 tag to my forked repo to make sure that this works before merging it.

This is required for now because of how setuptools_scm relies on tags
and the number of commits since that tag to determine the version number
string. (Without that info, the version will be named "0.1.dev1+g(hash)"
every time, possibly even for actual releases.)
@PhoenixBound PhoenixBound merged commit cb8a739 into pk-hack:master Dec 13, 2024
1 check passed
@PhoenixBound PhoenixBound deleted the ci-version-fix branch December 13, 2024 02:16
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