chore(payments): Upgrade stack 3.2 with payments 3.3.2

[Quentin-David-24]

No description provided.

[coderabbitai]

Warning

Review limit reached

@Quentin-David-24, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 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

Run ID: 0ca08473-64e8-4c4c-b802-4a548d2f2d59

📥 Commits

Reviewing files that changed from the base of the PR and between 3e8ed2d and 8abf921.

⛔ Files ignored due to path filters (7)

• charts/console-v3/Chart.lock is excluded by !**/*.lock, !**/*.lock
• 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/regions/Chart.yaml is excluded by !**/*.yaml
• charts/regions/values.yaml is excluded by !**/*.yaml

📒 Files selected for processing (3)

• README.md
• charts/formance/README.md
• charts/regions/README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/upgrade-payments-v3.3.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

• X
• Mastodon
• Reddit
• LinkedIn

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

[NumaryBot]

🛑 Changes requested — automated review

The intended payments bump is present, but the patch also changes dependency locks for charts whose versions are not bumped, making those changes unreleasable and inconsistent with the published chart versions.

[NumaryBot]

NumaryBot posted 1 new inline finding.

Summary: #394 (comment)

[NumaryBot]

🟠 [major] Revert unrelated lockfile bumps or version those charts

When this is merged, console-v3 now resolves Bitnami PostgreSQL 18.7.11 from source while its Chart.yaml version remains the already-published 3.7.0; the same applies to the portal and membership lockfile changes. The release workflow packages all charts but uploads with chart-releaser --skip-existing, so these changed artifacts won't be published under a new chart version and the repository source diverges from the released chart. Please either revert the unrelated lock updates or bump the affected chart versions if the PostgreSQL upgrade is intended.