-
Notifications
You must be signed in to change notification settings - Fork 10
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
Please tag the release commits #106
Comments
Seems reasonable. Though I've never done it. Do you know how to do this/automate it? Interested in submitting a PR? Probably it should go in the automated build script action |
Tagging / ReleasingTag for a past release: https://git-scm.com/book/en/v2/Git-Basics-Tagging.
Or even easier, make a release using the button on the Website: AutomationIf I read your workflow correctly, you update PyPI on every push to the main branch changing |
Thanks for the info! It sounds like (unlike me) you are quite familiar with how all the python packaging stuff works. I was vaguely aware this repo uses an older version, but I never had time to dig into updating/upgrading it. If you are interested in making a Pull request that updates this, I'd be happy to merge it
Yes, that's right |
From a packager viewpoint it would be great if you add git tags to the commits used for releasing a version on PyPI. For example, I need the test files corresponding to the released sdist.
The text was updated successfully, but these errors were encountered: