FDN-001 Update generic-charts to v2.0.6

[team-foundation-git]

This PR contains the following updates:

Package	Update	Change
git@github.com:flowcommerce/generic-charts.git	patch	v2.0.0 -> v2.0.6

⚠️ This PR updates the shared Helm chart version.

Before merging:

1. Ensure your service is compatible with the new chart version

2. Review diff in PR with changes

3. Merge when ready to deploy this change

After merging, ArgoCD will automatically sync the new chart version.

---

Release Notes

flowcommerce/generic-charts (git@github.com:flowcommerce/generic-charts.git)

v2.0.6

Compare Source

v2.0.5

Compare Source

v2.0.4

Compare Source

v2.0.3

Compare Source

v2.0.2

Compare Source

v2.0.1

Compare Source

---

This PR has been generated by Renovate Bot.

Summary by CodeRabbit

• Chores
  • Updated deployment chart dependency version from v2.0.0 to v2.0.6 across deployment configurations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two Argo CD Application manifests updated to use flow-generic Helm chart version v2.0.6 instead of v2.0.0 across dependency-api and dependency-www deployments.

Changes

Cohort / File(s)	Summary
Helm Chart Version Updates deploy/dependency-api/app.yaml, deploy/dependency-www/app.yaml	Updated targetRevision for flow-generic chart from v2.0.0 to v2.0.6 in both Argo CD Application manifests

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the main change: updating generic-charts to v2.0.6 across deployment manifests.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8611cc4 and f70a03f.

📒 Files selected for processing (2)

• deploy/dependency-api/app.yaml
• deploy/dependency-www/app.yaml

🔇 Additional comments (2)

deploy/dependency-www/app.yaml (1)

45-47: LGTM! Chart version bump is consistent with PR objectives.

The targetRevision update from v2.0.0 to v2.0.6 is a patch-level change. Since automated sync with selfHeal: true is enabled (lines 65-67), this will deploy automatically after merge—ensure service compatibility as noted in the PR description.

deploy/dependency-api/app.yaml (1)

45-47: LGTM! Consistent version bump across both applications.

The update to v2.0.6 matches the change in deploy/dependency-www/app.yaml, ensuring both services use the same chart version.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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 and usage tips.}

[flow-tech]

Argo diff output for dependency-www:

===== datadoghq.com/DatadogMonitor datadog/dependency-www-errorrate ======
148d147
<   - generated:kubernetes

[flow-tech]

Argo diff output for dependency-api:

===== datadoghq.com/DatadogMonitor datadog/dependency-api-errorrate ======
148d147
<   - generated:kubernetes

[team-foundation-git]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[jlogeart]

The Jira ticket is wrong and must be updated.