Skip to content

feat: bump climate-ref components to v0.16.1#17

Open
lewisjared wants to merge 1 commit into
mainfrom
feat/climate-ref-0.16.1
Open

feat: bump climate-ref components to v0.16.1#17
lewisjared wants to merge 1 commit into
mainfrom
feat/climate-ref-0.16.1

Conversation

@lewisjared

@lewisjared lewisjared commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

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

  • Pin climate-ref, -core, -celery, -esmvaltool, -pmp, -ilamb to 0.16.1 in pyproject.toml, versions.toml, helm/Chart.yaml (appVersion), helm/values.yaml, helm/README.md, and docker/docker-compose.yaml. Relocked uv.lock.
  • requires-python>=3.12 and drop 3.11 from the CI matrix. climate-ref v0.15.0 dropped Python 3.11.

Breaking changes (for deployers)

  • Python 3.12 is now the floor. Upgrade the environment before deploying.
  • Existing databases re-run each execution once on first use after upgrading. climate-ref v0.15.0 made the diagnostic input-dataset hash deterministic across pandas versions and platforms, so the stored hashes change.

Notes

  • v0.16.1 ships default_ignore_datasets.yaml inside the climate_ref package (Climate-REF/climate-ref#800), which fixes the config test fixture for wheel-installed consumers. The AFT test suite therefore needs no workaround — it runs against the real upstream fixture. tests/conftest.py is unchanged from main.

Verification

  • Full fast suite passes on Python 3.12 and 3.13 (11 passed); test_provider_discovery (which errored against 0.16.0) now passes with the packaged fixture.
  • All 10 version-consistency checks pass; ruff check/format clean.
  • helm template renders the worker image as ghcr.io/climate-ref/climate-ref:v0.16.1; frontend image unchanged.
  • uv lock --check clean.

Summary by CodeRabbit

  • Breaking Changes

    • Python 3.11 is no longer supported; Python 3.12+ is now required.
    • Existing databases may re-run once after upgrade due to updated hash values.
  • Updates

    • Bumped the platform and worker images to version 0.16.1 across deployment and packaging settings.
    • CI now tests against Python 3.12 and 3.13 only.

@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@lewisjared, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1a3138c1-5ef7-4617-858d-eec48a377b4a

📥 Commits

Reviewing files that changed from the base of the PR and between 4c4317a and 4d53655.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (9)
  • .github/workflows/ci.yml
  • changelog/17.breaking.md
  • changelog/17.improvement.md
  • docker/docker-compose.yaml
  • helm/Chart.yaml
  • helm/README.md
  • helm/values.yaml
  • pyproject.toml
  • versions.toml
📝 Walkthrough

Walkthrough

Updates 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.

Changes

Python Version and Climate-REF Version Bump

Layer / File(s) Summary
CI and dependency Python version constraint
.github/workflows/ci.yml, pyproject.toml, changelog/17.breaking.md
CI's install-pinned matrix drops Python 3.11, pyproject.toml raises requires-python to >=3.12, and a breaking changelog entry documents the new minimum version and related hashing behaviour change.
Climate-ref version pin bump
pyproject.toml, versions.toml, changelog/17.improvement.md
Pinned climate-ref core, celery, and diagnostic provider (esmvaltool, pmp, ilamb) versions plus app-version are bumped from 0.14.3 to 0.16.1, documented in an improvement changelog entry.
Container image and Helm chart tag updates
docker/docker-compose.yaml, helm/Chart.yaml, helm/values.yaml, helm/README.md
Docker Compose ref-init and base climate-ref service images, Helm chart appVersion, values.yaml image tag, and README provider defaults table are all updated from v0.14.3 to v0.16.1.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: upgrading Climate REF components to v0.16.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/climate-ref-0.16.1

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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.
@lewisjared lewisjared force-pushed the feat/climate-ref-0.16.1 branch from 4c4317a to 4d53655 Compare July 9, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant