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
automate release process #1138
automate release process #1138
Conversation
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 is amazing! I love it!! As mentioned in our discussion, one line / a link about how to setup the pypi token on github for authentication added to our release notes would be great.
Codecov Report
@@ Coverage Diff @@
## master #1138 +/- ##
=======================================
Coverage 86.98% 86.98%
=======================================
Files 220 220
Lines 19379 19379
=======================================
+ Hits 16856 16857 +1
+ Misses 2523 2522 -1
Continue to review full report at Codecov.
|
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.
looks great! will be a nice addition to the pipeline :)
.github/workflows/make_release.yml
Outdated
echo "::set-env name=release_filepath::$RELEASE_FILEPATH" | ||
- name: Create Release | ||
id: create_release | ||
uses: jbolda/create-release@v1.1.0 # switch to actions/create-release@latest once PR merged |
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'm assuming you mean PR actions/create-release#50 ? can you add that url for easy lookup?
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 included a shorthand instead of the full url, hope that's okay :)
@jni When I made this, I didn't realize that we stopped uploading wheels to PyPI. Just because I'm curious, what's the advantage of this? Could you make a suggestion to this PR so that it does not build the wheels? Sorry, I'm not super experienced at packaging! :P |
huh? We should definitely upload wheels, though they should be noarch. I can't remember how to limit wheels to certain Python versions, but that should be done also. |
Maybe I've been messing up there, my bad - glad the new process will fix that. I'm very excited about this!! |
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.
Love this. Thank you @kne42! What do you think about doing the same for scikit-image??? 😬😬😬😬
Description
Automate the release process using GitHub Actions.
Upon pushing a tag beginning with
v
tonapari/napari
, the CI will: