-
Notifications
You must be signed in to change notification settings - Fork 44
Set the version number on the development branches to one minor version more than the previous release #1854
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
main branch to one minor version more than the previous release
Codecov Report
@@ Coverage Diff @@
## main #1854 +/- ##
=======================================
Coverage 91.59% 91.59%
=======================================
Files 203 203
Lines 10989 10989
=======================================
Hits 10065 10065
Misses 924 924 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
zklaus
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. Should also be cherry-picked into the release branch, right?
|
cheers @bouweandela - do we have to pin setuptools_scm be with |
|
also, if you turn on GA you can directly see the version after the test runs |
|
this looks noice 😁 |
|
@ESMValGroup/technical-lead-development-team Could one of you please do a final check and merge? |
Description
This sets the version number on the
mainand feature branches so it starts withv2.8.0.dev(considering that the current release isv2.7.0). To make a release branch for a previous release, call itv2.7.xand the version number will be automatically correct (e.g. something starting withv2.7.1-devif branched of thev2.7.0tag). This approach avoids the need to merge micro releases back into themainbranch just to get the version number right.@ESMValGroup/technical-lead-development-team
See https://pypi.org/project/setuptools-scm/ for the details.
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
To help with the number pull requests: