-
Notifications
You must be signed in to change notification settings - Fork 13
Adding steps to pypi workflow - bot commit version bump #588
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
Conversation
adding two extra steps to commit version bump to pyproject
for more information, see https://pre-commit.ci
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #588 +/- ##
=======================================
Coverage 96.19% 96.19%
=======================================
Files 29 29
Lines 1865 1865
=======================================
Hits 1794 1794
Misses 71 71
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
These changes look good to me. I'd like Ben or Peter to also comment to make sure we all know what is going on in this logic. I don't think most of us are used to auto-updating packages during a release. I like it, because now when you check it out you get the right version in your code.
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 OK with this.
I added a couple of steps in
pypi.yml
to commit the version bump when a release is created.I also changed the version tag replacement using
sed
.There was an extra white space being introduced. This would cause the reggex search to fail on the next release event.
This should fix the doc building issue (currently showing the wrong release tag) automaticaly for next releases.
This garantees
pyproject.toml
in master is consistent with the distributed package tag.I also manualy set the version to 3.1.1 since that release is published.
Tested with pre-releases on the feat/version-bump-gha branch, and the github bot correctly comits the version bump.