search

roocs / clisops

Climate Simulation Operations
https://clisops.readthedocs.io/en/latest/
Other
21 stars 9 forks source link

Prepare v0.12.0 #305

Closed cehbrecht closed 9 months ago

cehbrecht commented 9 months ago

Pull Request Checklist:

What kind of change does this PR introduce?:

prepares version 0.12.0 with regridding.

Does this PR introduce a breaking change?:

no

Other information:

coveralls commented 9 months ago

Pull Request Test Coverage Report for Build 6981328252

Totals Coverage Status
Change from base Build 6972988063: 0.0%
Covered Lines: 1703
Relevant Lines: 2364
💛 - Coveralls
Zeitsperre commented 9 months ago

@cehbrecht

Would it be possible to unpin xarray before we tag a new version? For the regridding errors, we could emit some warnings about how 360-day calendars aren't supported at this time. I'd like to update CLISOPS downstream, but xarray 23.3.0 is ancient to the stack.

What do you think?

Zeitsperre commented 9 months ago

I'm opening a PR with some quality of life improvements to make things a bit more streamlined here. Should be ready in the next 30 mins.

cehbrecht commented 9 months ago

@cehbrecht

Would it be possible to unpin xarray before we tag a new version? For the regridding errors, we could emit some warnings about how 360-day calendars aren't supported at this time. I'd like to update CLISOPS downstream, but xarray 23.3.0 is ancient to the stack.

What do you think?

I think @sol1105 needs to answer this question ... I could also make the pin in daops or rook.

Zeitsperre commented 9 months ago

@cehbrecht

This is good to go. If you want to bump the version when merged to master, we'll be good. The exact process now (given the tooling changes):

$ pip install bump-my-version
$ bump-my-version bump minor
$ git push
$ git push --tags

After that, we should see a workflow get triggered and the "publish release" announcement get staged. After publishing, another workflow should trigger that either I, you, or @agstephens will need to authorize. This will then push a package to PyPI automatically.

Zeitsperre commented 9 months ago

@cehbrecht Would it be possible to unpin xarray before we tag a new version? For the regridding errors, we could emit some warnings about how 360-day calendars aren't supported at this time. I'd like to update CLISOPS downstream, but xarray 23.3.0 is ancient to the stack. What do you think?

I think @sol1105 needs to answer this question ... I could also make the pin in daops or rook.

I added a warning for users using the new xarray (assuming they updated their version beyond the supported one). It appears that the fix is up to the maintainers of xarray/cf-xarray. Not much we can do about it.