Skip to content

chore(regions): upgrade operator to v3.13.2 - #409

Merged
flemzord merged 1 commit into
mainfrom
chore/upgrade-operator-v3.13.2
Aug 12, 2026
Merged

chore(regions): upgrade operator to v3.13.2#409
flemzord merged 1 commit into
mainfrom
chore/upgrade-operator-v3.13.2

Conversation

@flemzord

@flemzord flemzord commented Aug 12, 2026

Copy link
Copy Markdown
Member

Summary

  • upgrade the Regions Operator dependency from 3.13.1 to 3.13.2
  • bump the Regions chart from 3.15.1 to 3.15.2
  • regenerate the dependency lock and chart README

Validation

  • helm show chart oci://ghcr.io/formancehq/helm/operator --version 3.13.2
  • docker buildx imagetools inspect ghcr.io/formancehq/operator:v3.13.2
  • just helm-template-only charts/regions
  • git diff --check

Release verification

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b3bd6d4c-2faf-4984-b937-54855cd6e584

📥 Commits

Reviewing files that changed from the base of the PR and between 87c6fe3 and 5915709.

⛔ Files ignored due to path filters (2)
  • charts/regions/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/regions/Chart.yaml is excluded by !**/*.yaml
📒 Files selected for processing (1)
  • charts/regions/README.md

Walkthrough

The regions chart README version badge was updated from 3.15.1 to 3.15.2.

Changes

Regions chart version

Layer / File(s) Summary
Update chart version badge
charts/regions/README.md
The README badge now reports chart version 3.15.2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: sylr

Poem

A bunny checked the chart with care,
And found a newer number there.
Three-fifteen-two now shines bright,
In README badge display light.
Hop, hop—the version’s right!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
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.
Title check ✅ Passed The title clearly identifies the Regions Operator upgrade to version 3.13.2, which is the primary change described by the objectives.
Description check ✅ Passed The description directly explains the operator and chart upgrades, regeneration steps, validation, and release verification.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/upgrade-operator-v3.13.2

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.

@flemzord
flemzord marked this pull request as ready for review August 12, 2026 14:17
@flemzord
flemzord requested a review from a team as a code owner August 12, 2026 14:17
@NumaryBot

Copy link
Copy Markdown
Contributor

✅ Approve — automated review

The chart, lockfile, and generated README versions are updated consistently, with no apparent regressions.

No findings.

@flemzord
flemzord merged commit 74a4dee into main Aug 12, 2026
5 of 6 checks passed
@flemzord
flemzord deleted the chore/upgrade-operator-v3.13.2 branch August 12, 2026 14:19
Dav-14 added a commit that referenced this pull request Aug 12, 2026
PR #409 bumped regions to 3.15.2 (operator v3.13.2) without cascading
to the formance umbrella chart. Its Chart.lock still pinned regions
3.15.1, leaving main dirty for pre-commit and consumers of the umbrella
without the operator upgrade.

Charts bumped:
- formance 1.18.1 -> 1.18.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants