-
Notifications
You must be signed in to change notification settings - Fork 56
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
Move release pipeline to a separate file | chore(release) #619
Conversation
publish-dev: | ||
needs: [release] | ||
runs-on: ubuntu-latest | ||
environment: PyPI Dev |
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.
Different environments are used here
Codecov Report
@@ Coverage Diff @@
## main #619 +/- ##
=======================================
Coverage 74.54% 74.54%
=======================================
Files 107 107
Lines 11302 11302
Branches 1177 1177
=======================================
Hits 8425 8425
Misses 2557 2557
Partials 320 320 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Shall we still add some tests after publishing wheels? Testing the built wheel can still be useful.
Just curious: which test is flaky? #567 this issue?
I moved the release pipeline out because the tests are sometimes flaky but we may not want them to block the scheduled release. I separated the dev and official releases to use different environments so the official releases can be manually reviewed before uploading to pypi.
Updated requirements-dev.txt