Skip to content

chore: update config-db to 0.0.1383 #599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
flankbot merged 1 commit into from
May 27, 2026
Merged

chore: update config-db to 0.0.1383 #599

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion agent-chart/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ maintainers:
- name: Flanksource
dependencies:
- name: config-db
version: "0.0.1382"
version: "0.0.1383"

@coderabbitai coderabbitai Bot May 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Update agent-chart/Chart.lock to match this dependency bump.

agent-chart/Chart.yaml now sets config-db to 0.0.1383, but agent-chart/Chart.lock (lines 1-4 in the provided context) still pins config-db to 0.0.1161. This can cause dependency build/package steps to use the old locked version instead of this bump.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@agent-chart/Chart.yaml` at line 11, Chart.yaml was bumped to set the
config-db dependency to 0.0.1383 but agent-chart/Chart.lock still pins config-db
at 0.0.1161; update Chart.lock to match by either editing the config-db entry to
version 0.0.1383 and updating its checksum, or simply run a dependency
lock/regeneration (e.g., run helm dependency update in the agent-chart
directory) so the Chart.lock reflects config-db: 0.0.1383 and its correct
checksum.

repository: https://flanksource.github.io/charts
- name: canary-checker
version: "1.1.3-beta.144"
Expand Down
2 changes: 1 addition & 1 deletion chart/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ dependencies:
repository: https://flanksource.github.io/charts
condition: apm-hub.enabled
- name: config-db
version: "0.0.1382"
version: "0.0.1383"

@coderabbitai coderabbitai Bot May 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Regenerate chart/Chart.lock to keep dependency state consistent.

This config-db bump to 0.0.1383 should be accompanied by an updated chart/Chart.lock. The provided chart/Chart.lock snippet is stale, so dependency resolution may not reflect the intended versions.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@chart/Chart.yaml` at line 16, Update the Helm chart dependency lock so it
matches the new version change in Chart.yaml: regenerate chart/Chart.lock after
bumping the chart version to "0.0.1383" (the version field in Chart.yaml) by
running the appropriate Helm command (e.g., helm dependency update or helm
dependency build) in the chart directory, commit the updated Chart.lock so
dependency state is consistent with the new config-db bump.

repository: https://flanksource.github.io/charts
- name: canary-checker
version: "1.1.3-beta.144"
Expand Down
Loading