chore(charts): update chart versions for Cloudprem, Console-V3, Forma…

[reslene]

…nce, and Portal to latest releases

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e6792a3f-d65a-4b26-a9c7-d6ec4d79af24

📥 Commits

Reviewing files that changed from the base of the PR and between 7b1307c and 2153c2d.

⛔ Files ignored due to path filters (9)

• charts/cloudprem/Chart.lock is excluded by !**/*.lock, !**/*.lock
• charts/cloudprem/Chart.yaml is excluded by !**/*.yaml
• charts/console-v3/Chart.lock is excluded by !**/*.lock, !**/*.lock
• charts/console-v3/Chart.yaml is excluded by !**/*.yaml
• charts/formance/Chart.lock is excluded by !**/*.lock, !**/*.lock
• charts/formance/Chart.yaml is excluded by !**/*.yaml
• charts/membership/Chart.lock is excluded by !**/*.lock, !**/*.lock
• charts/portal/Chart.lock is excluded by !**/*.lock, !**/*.lock
• charts/portal/Chart.yaml is excluded by !**/*.yaml

📒 Files selected for processing (5)

• README.md
• charts/cloudprem/README.md
• charts/console-v3/README.md
• charts/formance/README.md
• charts/portal/README.md

🚧 Files skipped from review as they are similar to previous changes (3)

• charts/cloudprem/README.md
• charts/formance/README.md
• charts/portal/README.md

---

Walkthrough

Updated the root Helm chart version table and four chart README badges for the Cloudprem, Console-V3, Formance, and Portal releases.

Changes

Chart release metadata

Layer / File(s)	Summary
Synchronize chart version documentation README.md, charts/{cloudprem,console-v3,formance,portal}/README.md	Updated displayed chart versions and, for Console-V3 and Portal, application versions in the Helm chart table and README badges.

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

Possibly related PRs

• formancehq/helm#395: Updates the same chart README version and AppVersion badges.
• formancehq/helm#384: Applies corresponding version-badge updates across the same chart documentation.
• formancehq/helm#397: Updates the Formance chart version badge in the same README.

Suggested reviewers: dav-14, gfyrag

Poem

A rabbit hops through charts so bright,
Bumping badges left and right.
Cloudprem, Console, Portal too,
Formance wears a number new.
Release carrots—freshly grew!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change by summarizing the chart version updates for the affected charts.
Description check	✅ Passed	The description is related to the changeset and states the charts were updated to latest releases.
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/platform_ui_v2.7

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[NumaryBot]

🛑 Changes requested — automated review

The PR performs a chart version cascade for Cloudprem, Console-V3, and Forma charts, which appears consistent. However, the standalone membership chart's Chart.lock file has been refreshed (updating the locked PostgreSQL subchart dependency) while charts/membership/Chart.yaml remains at version 3.6.2. This creates a conflict with the repository's immutable chart release workflow: the release pipeline uses --skip-existing, so no new membership artifact will be published, yet building from source would yield a different 3.6.2 artifact than the already-published one. This must be resolved by either reverting the Chart.lock change or bumping the membership chart version and regenerating all derived files.

Findings outside the diff

🟠 [major] Membership Chart.lock changed without a corresponding chart version bump — charts/membership/Chart.lock:4 _{(NumaryBot, chatgpt-codex-connector[bot], codex)}

The standalone membership chart's locked PostgreSQL subchart dependency has been refreshed in Chart.lock, but charts/membership/Chart.yaml still remains at version 3.6.2. The release workflow publishes immutable chart versions with --skip-existing, so no new membership chart artifact will be published. However, packaging from this source would produce a different 3.6.2 artifact than the already-published one, causing a mismatch between the repository and the published artifact.

Suggestion: Either revert the Chart.lock change (if it was unintentional) or bump the membership chart version in Chart.yaml and regenerate all derived files so the updated dependency set is published under a new version.

[NumaryBot]

NumaryBot posted 1 new inline finding.

Summary: #398 (comment)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7b1307c027

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Bump membership for its lockfile refresh

This refreshes membership's locked PostgreSQL dependency while charts/membership/Chart.yaml remains at 3.6.2. The repo documents that any Chart.lock owner needs its own chart version bump, and the release flow publishes immutable chart versions with cr upload --skip-existing; without a new membership version, direct membership consumers will never receive this dependency update as a released chart, while source builds can produce a different 3.6.2 artifact. Please bump membership and regenerate the derived files.

Useful? React with 👍 / 👎.

[NumaryBot]

🛑 Changes requested — automated review

The PR performs a chart version cascade for Cloudprem, Console-V3, and Forma charts, which appears consistent. However, the standalone membership chart's Chart.lock file has been refreshed (updating the locked PostgreSQL subchart dependency) while charts/membership/Chart.yaml remains at version 3.6.2. This creates a conflict with the repository's immutable chart release workflow: the release pipeline uses --skip-existing, so no new membership artifact will be published, yet building from source would yield a different 3.6.2 artifact than the already-published one. This must be resolved by either reverting the Chart.lock change or bumping the membership chart version and regenerating all derived files.

Findings outside the diff

🟠 [major] Membership Chart.lock changed without a corresponding chart version bump — charts/membership/Chart.lock:4 _{(NumaryBot, chatgpt-codex-connector[bot], codex)}

The standalone membership chart's locked PostgreSQL subchart dependency has been refreshed in Chart.lock, but charts/membership/Chart.yaml still remains at version 3.6.2. The release workflow publishes immutable chart versions with --skip-existing, so no new membership chart artifact will be published. However, packaging from this source would produce a different 3.6.2 artifact than the already-published one, causing a mismatch between the repository and the published artifact.

Suggestion: Either revert the Chart.lock change (if it was unintentional) or bump the membership chart version in Chart.yaml and regenerate all derived files so the updated dependency set is published under a new version.

Summary: #398 (comment)