-
-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for full hatchling versioning. #1026
Comments
If you tag your releases then an alternative workaround to consider might be to switch the backend from [project]
#version = "dynamic"
dynamic = ["version"]
[build-system]
requires = ["setuptools>=69", "setuptools_scm>=8"]
build-backend = "setuptools.build_meta"
[tool.setuptools_scm]
# can be empty if no extra settings are needed, presence enables setuptools_scm |
Hatchling supports that directly and the maintainer uses this as well https://github.com/ofek/hatch-vcs |
It looks like hatchling is being used under the hood. In my use case I'd like to utilize test.pypi and when I was using poetry I could do
.dev
versions.The first one here was uploaded with
rye
but I found I couldn't easily support.dev
versionsHowever to the best of my knowledge you are using hatchling under the hood.
I did the following:
Modified my pyproject:
Then I ran
So it looks like it wouldn't be to hard to implement a -dev version flag somehow.
The text was updated successfully, but these errors were encountered: