Skip to content

chore: update config-db to 0.0.1381 #595

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.1381 #595

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.1380"
version: "0.0.1381"
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot May 27, 2026

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

Sync dependency lockfile with this version bump.

Line 11 updates config-db to 0.0.1381, but agent-chart/Chart.lock (Lines 1-4) still pins config-db to 0.0.1161. Please regenerate and commit the lockfile to avoid stale/non-reproducible dependency resolution in packaging pipelines.

🤖 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, Update the dependency lockfile to match
the bumped Chart version: regenerate agent-chart/Chart.lock so the config-db
entry is updated from 0.0.1161 to 0.0.1381 (or otherwise reflects the current
Chart.yaml dependencies). Run the chart dependency lock command (e.g., helm
dependency update/helm dependency build or the repo's lock generation step) and
commit the updated Chart.lock alongside Chart.yaml so packaging pipelines use
the correct pinned config-db version.

repository: https://flanksource.github.io/charts
- name: canary-checker
version: "1.1.3-beta.142"
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.1380"
version: "0.0.1381"
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot May 27, 2026

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

Refresh chart/Chart.lock after dependency version change.

Line 16 bumps config-db to 0.0.1381, but the current chart/Chart.lock snapshot is stale (e.g., it still shows apm-hub at 0.0.47 in Lines 1-4). Please run dependency update and commit the updated lockfile so release artifacts resolve 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, Chart version was bumped in Chart.yaml
(version: "0.0.1381") but the chart/Chart.lock snapshot is stale; run the Helm
dependency update to refresh the lockfile (e.g., run helm dependency update or
the repo's dependency update script) so Chart.lock reflects the new dependency
versions (ensure entries like apm-hub and config-db match the bumped versions),
then commit the updated chart/Chart.lock alongside the Chart.yaml change.

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