chore: bump Regions chart to version 2.6.0

[flemzord]

Updated the Regions Helm Chart to version 2.6.0 and upgraded the Operator dependency to version 2.5.1. These changes reflect improvements and potential fixes in the chart and its dependencies. Ensure compatibility before deploying.

[coderabbitai]

Walkthrough

This pull request involves version updates for the "Regions" Helm chart. The changes include incrementing the chart version from v2.5.4 to v2.6.0 in both the root README.md and the chart-specific README.md. Additionally, the operator dependency version has been upgraded from v2.3.1 to v2.5.1, indicating potential improvements or compatibility updates for the Helm chart.

Changes

File	Change Summary
README.md	Chart version updated from v2.5.4 to v2.6.0
charts/regions/README.md	- Version badge updated to v2.6.0 - Operator dependency version upgraded to v2.5.1

Poem

🐰 A Helm chart's version takes flight,
From v2.5.4 to v2.6.0 so bright!
Operator bumped with gentle care,
Upgrades dancing through the air 🚀
Regions chart, now fresh and new,
Hopping forward with a view! 🌈

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c48753b and 45ec849.

⛔ 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 (2)

• README.md (1 hunks)
• charts/regions/README.md (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• README.md

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Tests

🔇 Additional comments (2)

charts/regions/README.md (2)

3-3: LGTM: Version bump follows semantic versioning.

The version update from v2.5.4 to v2.6.0 is properly reflected in the badge and follows semantic versioning conventions.

---

25-25: Verify compatibility with operator v2.5.1.

The operator dependency has been updated from v2.3.1 to v2.5.1, which is a significant version jump. Please ensure:

1. All new features and breaking changes in operator v2.5.1 are compatible with this chart
2. The changelog for operator versions between v2.3.1 and v2.5.1 has been reviewed

✅ Verification successful

✓ Operator v2.5.1 compatibility verified

The version upgrade from v2.3.1 to v2.5.1 is safe. Review of the changelog shows:

• No breaking changes across v2.4.0, v2.5.0, and v2.5.1
• Only additive features (payments v3, configurable page sizes)
• Infrastructure improvements (container security, CRD enhancements)

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify operator version compatibility and changelog

# Check if the operator version exists in the registry
gh api \
  -H "Accept: application/vnd.oci.image.index.v1+json" \
  /v2/formancehq/helm/operator/manifests/v2.5.1

# Fetch operator releases to check changelog
gh release list --repo formancehq/operator

Length of output: 1550

---

Script:

#!/bin/bash
# Fetch release notes for relevant versions
echo "=== Release v2.5.1 ==="
gh release view v2.5.1 --repo formancehq/operator

echo -e "\n=== Release v2.5.0 ==="
gh release view v2.5.0 --repo formancehq/operator

echo -e "\n=== Release v2.4.0 ==="
gh release view v2.4.0 --repo formancehq/operator

# Check for any related configuration changes in the chart
echo -e "\n=== Chart Changes ==="
rg -A 5 "operator" charts/regions/values.yaml

Length of output: 5674

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.