feat: bump climate-ref components to v0.16.1#17
Conversation
|
Warning Review limit reached
Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
📝 WalkthroughWalkthroughUpdates the minimum supported Python version to 3.12 (removing 3.11 from CI matrix and pyproject constraint) and bumps pinned climate-ref component versions from 0.14.3 to 0.16.1 across pyproject.toml, versions.toml, Docker Compose images, Helm chart/values/README, and adds corresponding changelog entries. ChangesPython Version and Climate-REF Version Bump
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bump the pinned climate-ref core, celery, esmvaltool, pmp, and ilamb components and the worker container image (helm + docker-compose) from v0.14.3 to v0.16.1, and raise the Python floor to 3.12 to match. climate-ref v0.15.0 dropped Python 3.11 and made the diagnostic input-dataset hash deterministic across pandas versions, so existing databases re-run each execution once on first upgrade. v0.16.1 also ships default_ignore_datasets.yaml inside the package (Climate-REF/climate-ref#800), so the test suite no longer needs to work around the upstream test fixture.
4c4317a to
4d53655
Compare
Update the pinned Climate REF stack from v0.14.3 to v0.16.1 across every place the AFT repo tracks it, and raise the Python floor to 3.12 to match upstream.
Changes
climate-ref,-core,-celery,-esmvaltool,-pmp,-ilambto0.16.1inpyproject.toml,versions.toml,helm/Chart.yaml(appVersion),helm/values.yaml,helm/README.md, anddocker/docker-compose.yaml. Relockeduv.lock.requires-python→>=3.12and drop3.11from the CI matrix. climate-ref v0.15.0 dropped Python 3.11.Breaking changes (for deployers)
Notes
default_ignore_datasets.yamlinside theclimate_refpackage (Climate-REF/climate-ref#800), which fixes theconfigtest fixture for wheel-installed consumers. The AFT test suite therefore needs no workaround — it runs against the real upstream fixture.tests/conftest.pyis unchanged frommain.Verification
test_provider_discovery(which errored against 0.16.0) now passes with the packaged fixture.ruff check/formatclean.helm templaterenders the worker image asghcr.io/climate-ref/climate-ref:v0.16.1; frontend image unchanged.uv lock --checkclean.Summary by CodeRabbit
Breaking Changes
Updates