-
Notifications
You must be signed in to change notification settings - Fork 36
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
Automatically create GitHub Release #138
Conversation
A suggestion from online was to additionally trigger publishing to pypi. https://x.com/ljharb/status/1713294633676239275 |
I added steps to publish to PyPI. I also realized that the GitHub release action I was using doesn't support publishing the release, so I refactored to use a different one. Finally, I added a step to attach the builds to the release. I'm not sure how to QA this aside from merging and going YOLO. Might go and do that? Will probably be a mess. |
.github/workflows/release.yaml
Outdated
echo "python_version=[${VERSION}]" > "${GITHUB_OUTPUT}" | ||
# See: https://stackoverflow.com/questions/58177786/get-the-current-pushed-tag-in-github-actions | ||
- name: Get release version | ||
run: echo "release_version=$(GITHUB_REF#refs/*/}" >> "${GITHUB_OUTPUT}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could also grab this from pyproject.toml
- it's a matter of what I want to be the source of truth.
on: | ||
push: | ||
tags: | ||
- 'v*' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This means releases are now tagged vx.y.z
instead of x.y.z
. I'm OK with that.
This is an attempt to address #129. I haven't reviewed or tested it, but I think this would be pretty close to working.
My intent is to wait until I do the next pyee release, then self-review and decide if I like it or not.