-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add script to create a release on GitHub Actions from a tag #2338
Conversation
So I decided to take inspiration from this PR and put together a routine in a library to do the work in jaraco/jaraco.develop@178c073 But when I ran it on a recent release of keyring, I got a 403 Forbidden.
So I went to keyring and see that releases are generated automatically from tags: I double-checked that the token I'm using has all |
Aha, after emitting the error message in jaraco/jaraco.develop@85b9c5e, it became clear that the request was being rejected for a missing Now the command runs without error. And the releases page now looks different: But that still doesn't explain why keyring is getting tags automatically reflected as releases but Setuptools isn't. |
Thanks for drafting this PR. I was able to adapt the technique into a re-usable solution in jaraco/skeleton#23 which I hand-cherry-picked in 17cb9d6. Future releases should get Github releases. Let me know if you find otherwise. |
Good stuff, thank you! |
Summary of changes
Add a script to create a release on GitHub Actions from a tag.
Usage:
Calls
finalize.get_version
and prependsv
to get the default tag.Needs a
GITHUB_TOKEN
environment variable.public_repo
permission is neededExample in my fork with explicit args:
API docs: https://docs.github.com/en/rest/reference/repos#create-a-release
I'd need some guidance if this is to go in https://github.com/jaraco/skeleton first.
A
body
parameter can be used to add release notes, I'd suggest this be added in a follow-up once the general flow is working.Closes #2328.
Pull Request Checklist