-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Dynamic Versioning is not taking the tag in GitHub Actions #78
Comments
Hi! By default, the workflow only downloads the latest commit without the rest of the history. That also means it won't know about any tags, unless the latest commit has one. You can fix this by setting the following option: - uses: actions/checkout@v2
with:
fetch-depth: 0 |
Mmmm, it's still Because this is the workflow that publishes on test PyPI, in the official release workflow I expect it to run when a tag is pushed, so in that case, it should be fine... 🤔 |
It has fetched the tag now, but still the version output is |
Could you share a link to the repository and branch? I took a guess and checked the oktagon-python branch Also, with |
Yeah sorry, I removed the changes yesterday to have something working for the time being. |
Thanks, that makes more sense now. |
I changed now, here and put everything into the GitHub action now, but still is trying to push |
Hmm, I see you're using |
Looks like switching to In regards to the new error from Poetry:
You can set Also, this may be intentional, but just in case: Since you're using the Semantic Versioning output, you have a |
Change from semver to PEP440 and remove the git hash part of the version string when uploading to TestPyPI. Based on mtkennerly/poetry-dynamic-versioning#78 (comment). Prevents errors like `'0.0.0.post15+f899e49' is an invalid value for Version. Error: Can't use PEP 440 local versions. See https://packaging.python.org/specifications/core-metadata for more information`.
Building the binary wheel and source tarball packages with `poetry build` and publishing to TestPyPI and PyPI via GitHub Actions. * 📦 Publish to TestPyPI and PyPI using GitHub Actions Automating the binary wheel and source tarball publishing to TestPyPI and PyPI. Based on https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows but using `poetry` to do the build. * 💚 Fix version string to be PEP440 compliant for TestPyPI Change from semver to PEP440 and remove the git hash part of the version string when uploading to TestPyPI. Based on mtkennerly/poetry-dynamic-versioning#78 (comment). Prevents errors like `'0.0.0.post15+f899e49' is an invalid value for Version. Error: Can't use PEP 440 local versions. See https://packaging.python.org/specifications/core-metadata for more information`. * 💬 Include TestPyPI installation instructions So that people can get the latest development package from https://test.pypi.org/project/zen3geo. Also centering the title on the webpage. * 💬 Update dev status from 1 planning to 3 alpha Jumping two steps ahead, why drive when you can fly?
This fixes the `0.0.0` version issue on GitHub Actions. See: mtkennerly/poetry-dynamic-versioning#78 (comment)
This fixes the `0.0.0` version issue on GitHub Actions. See: mtkennerly/poetry-dynamic-versioning#78 (comment)
Hi
This is an amazing project and I would like to integrate in my little package, everything is working fine locally but when I run with GitHub actions it is taking the placeholder version
0.0.0
...I don't understand what I'm doing wrong... :(
this is the pyproject.toml
The ci:
but it will build the package with 0.0.0:
Can you help me understand why is not taking correctly the version from the tag that is
0.0.16
atm?The text was updated successfully, but these errors were encountered: