fix(cloudprem): old dex img

[Dav-14]

No description provided.

[coderabbitai]

Walkthrough

This pull request involves version updates for two Helm charts: Cloudprem and Membership. The README files for both charts have been modified to increment their chart versions from 2.1.0 to 2.1.1 and 1.1.0 to 1.1.1 respectively. Additionally, the Membership chart's README includes an image tag update for the Dex component from v0.33.10 to v0.36.2.

Changes

File	Change Summary
README.md	Helm chart versions updated for Cloudprem (2.1.0 → 2.1.1) and Membership (1.1.0 → 1.1.1)
charts/cloudprem/README.md	Version incremented from 2.1.0 to 2.1.1
charts/membership/README.md	Version incremented from 1.1.0 to 1.1.1, Dex image tag updated from v0.33.10 to v0.36.2

Possibly related PRs

• feat: Update all releases in stable #91: Version update for Cloudprem chart from v2.0.0-beta.45 to 2.1.0
• feat: Update all releases in stable #91: Version update for Membership chart from v1.0.0-beta.27 to 1.1.0

Suggested labels

bug, docs, release

Suggested reviewers

• flemzord

Poem

🐰 Versions dance, a subtle art,
Charts updated, a fresh new start
From 2.1.0 to 2.1.1 we leap
Dex tags shift, improvements we keep
A rabbit's release, precise and neat! 🚀

---

📜 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 912a648 and 94f859f.

⛔ Files ignored due to path filters (4)

• charts/cloudprem/Chart.lock is excluded by !**/*.lock, !**/*.lock
• charts/cloudprem/Chart.yaml is excluded by !**/*.yaml
• charts/membership/Chart.yaml is excluded by !**/*.yaml
• charts/membership/values.yaml is excluded by !**/*.yaml

📒 Files selected for processing (3)

• README.md (1 hunks)
• charts/cloudprem/README.md (2 hunks)
• charts/membership/README.md (2 hunks)

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

• charts/cloudprem/README.md
• charts/membership/README.md

🧰 Additional context used

🪛 LanguageTool

README.md

[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 10 exclamation marks for a text that’s 3034 characters long)
Context: ...tions, users, roles, and permissions. | | | Portal | 1.1.0 |191a441519a65dae56a5b2cf56fe64eee03fc059 | Formance Portal | | | Regions | 2.7.0 |latest | Formance Private Regions Helm Chart | | | Stargate | 0.6.0 |latest | Formance Stargate gRPC Gateway | [![Artifact HUB](https://img.shields.io/en...

(EN_EXCESSIVE_EXCLAMATION)

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

• GitHub Check: Tests

🔇 Additional comments (2)

README.md (2)

8-8: Verify the rationale for Cloudprem version bump.

The chart version is bumped from 2.1.0 to 2.1.1, but the app version remains at v0.36.2. Please clarify if this patch version increment is related to the Dex image fix mentioned in the PR title.

✅ Verification successful

Version bump is justified

The Cloudprem chart version increment (2.1.0 to 2.1.1) is appropriate as it reflects the Dex image update in its Membership chart dependency. This follows semantic versioning principles where dependency updates warrant a patch version bump.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the Cloudprem chart has any Dex-related changes

# Look for Dex-related changes in the Cloudprem chart
fd -t f . charts/cloudprem -x rg -l 'dex|DEX'

Length of output: 418

---

Script:

#!/bin/bash
# Check Chart.yaml and values.yaml for Dex-related changes
echo "=== Chart.yaml ==="
cat charts/cloudprem/Chart.yaml

echo -e "\n=== values.yaml Dex config ==="
rg -A 5 -B 5 'dex:|DEX' charts/cloudprem/values.yaml

echo -e "\n=== Git diff for relevant files ==="
git diff HEAD^1 charts/cloudprem/Chart.yaml charts/cloudprem/values.yaml

Length of output: 2920

---

13-13: LGTM! Verify Dex image update in values.yaml.

The Membership chart version bump from 1.1.0 to 1.1.1 aligns with the Dex image update mentioned in the PR title.

✅ Verification successful

✅ Dex image update verified

The Dex image tag is correctly set to v0.36.2 in the Membership chart's values.yaml, matching the app version in README.md.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify Dex image update in Membership chart

# Check the values.yaml file for Dex image configuration
rg -A 5 'image:.*dex' charts/membership/values.yaml

Length of output: 53

---

Script:

#!/bin/bash
# Broader search for Dex configuration
echo "=== Searching for Dex in values.yaml ==="
rg -i "dex" charts/membership/values.yaml

echo -e "\n=== Looking for Dex-related files ==="
fd -i dex charts/membership/

Length of output: 2299

---

Script:

#!/bin/bash
# Get more context around Dex image configuration
rg -B 2 -A 4 'repository: ghcr.io/formancehq/dex' charts/membership/values.yaml

Length of output: 293

---

Script:

#!/bin/bash
# Get extended context around Dex image configuration
rg -B 2 -A 8 'repository: ghcr.io/formancehq/dex' charts/membership/values.yaml

Length of output: 358

🧰 Tools

🪛 LanguageTool

[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 10 exclamation marks for a text that’s 3034 characters long)
Context: ...tions, users, roles, and permissions. | | | Portal | 1.1.0 |191a441519a65dae56a5b2cf56fe64eee03fc059 | Formance Portal | | | Regions | 2.7.0 |latest | Formance Private Regions Helm Chart | | | Stargate | 0.6.0 |latest | Formance Stargate gRPC Gateway | [![Artifact HUB](https://img.shields.io/en...

(EN_EXCESSIVE_EXCLAMATION)

---

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.