-
Notifications
You must be signed in to change notification settings - Fork 18
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
New publish workflow #568
New publish workflow #568
Conversation
with: | ||
files: | | ||
dist/* | ||
generate_release_notes: true | ||
|
||
- name: Publish distribution on PyPI | ||
uses: pypa/gh-action-pypi-publish@release/v1 |
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.
It certainly looks like we would publish to PyPI even if the tag did not start with v
. I think the new code is correct. Also I've switched the order of PyPI publish and GitHub release. This was, if the PyPI release fails for any reason, we do not create a release on Github.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #568 +/- ##
=======================================
Coverage 87.07% 87.07%
=======================================
Files 27 27
Lines 4649 4649
=======================================
Hits 4048 4048
Misses 601 601
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
The biggest fix here is to stop a release to PyPI if the tag does not start with
v
.We now also automatically skip the publish if we are in a fork (it would fail anyway since the secrets are not available on forks).
I've verified the new behaviour on my fork.