-
Notifications
You must be signed in to change notification settings - Fork 49
Use autorelease check instead of custom script
#1173
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
Use autorelease check instead of custom script
#1173
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1173 +/- ##
==========================================
- Coverage 81.51% 81.51% -0.01%
==========================================
Files 147 147
Lines 15806 15806
==========================================
- Hits 12885 12884 -1
- Misses 2921 2922 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
autorelease check instead of customs scriptautorelease check instead of custom script
|
This is ready for review and comment. Without review, I will merge this after at least 24 hours, no sooner than Mon 12 May 21:00 GMT (16:00 my local). |
autorelease check instead of custom scriptautorelease check instead of custom script
sroet
left a comment
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.
LGTM!
We recently bumped up to setuptools 80 in our default builds. This is causing problems because of major changes in how
setuptoolstreats thedevelopcommand.In any case, instead of having a custom script that uses autorelease, it is better to use the
autorelease checkcommand, available since autorelease 0.3.0 (2021). That's what this PR will do.autorelease checkfixes (otherwise, fix might be needed upstream in autorelease)devtools/autorelease_check.py