Set the version number on the development branches to one minor version more than the last release

[bouweandela]

Description

This uses the next minor release as the development version. E.g. because we are currently developing v2.8, this sets the version number of development branches so it starts with v2.8.0-dev. See setuptool-scm for more detailed information.

Related to ESMValGroup/ESMValCore#1854.

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

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.

• 🛠 This pull request has a descriptive title
• 🛠 Tests run successfully
• 🛠 The list of authors is up to date
• 🛠 All checks below this pull request were successful

---

To help with the number of pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[bouweandela]

Tests are failing due to #2965

[valeriupredoi]

@bouweandela would you mind turning the GA Test (just the test flow should do) on pls? And don't merge main just yet, I'd be curious to see the behaviour with shapely=2.0 and changing the version setter like in here. That is 100% our issue in Tool since esmvalcore on its own is very happy with shapely=2.0

[bouweandela]

Maybe it's easiest of you run the tests yourself because you know what you want from this. Would that be OK with you? You could just create a new branch off this branch if you would like to use the changes in this one.

[valeriupredoi]

aye, will do, man. Got some ideas before that anyway, steady as she goes for now

[valeriupredoi]

@bouweandela now that I figured out the shapely issue, and it's got nothing to do with scm or versioning, I think we can release this into the wild; if you make it RFR then I can review it and get it out. One thing though - can we maybe change the pin of esmvalcore from 2.7* to >=2.7, so there are no issues with the dev branch of it?

[bouweandela]

One thing though - can we maybe change the pin of esmvalcore from 2.7* to >=2.7, so there are no issues with the dev branch of it?

Would it make sense to create a separate issue to explain what the issue is? It seems unrelated to this pull request.

[valeriupredoi]

yeah I opened #2971 - but am rather dubious about it since I noticed it only on my laptop (yeh, running an OK Ubuntu not 19th century 😆 )

[valeriupredoi]

easiest PR I've reviewed in months 😆

[bouweandela]

@ESMValGroup/technical-lead-development-team Could someone please do a final check and merge?

[valeriupredoi]

I am a changed person in 2023 so I qualify to do the last checks and merge 🤣 (seriously now, I'm grabbing this in so we don't have to wait any more, if there are any issues, better find them earlier)