chore: update config-db to 0.0.1381#595
Conversation
WalkthroughThis PR synchronizes two Helm chart dependencies to version 0.0.1381. The ChangesHelm Chart Dependency Update
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with 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.
Inline comments:
In `@agent-chart/Chart.yaml`:
- 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.
In `@chart/Chart.yaml`:
- 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.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: fa6918fa-53fc-479d-9032-f9ac61ac2783
📒 Files selected for processing (2)
agent-chart/Chart.yamlchart/Chart.yaml
| dependencies: | ||
| - name: config-db | ||
| version: "0.0.1380" | ||
| version: "0.0.1381" |
There was a problem hiding this comment.
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.
| condition: apm-hub.enabled | ||
| - name: config-db | ||
| version: "0.0.1380" | ||
| version: "0.0.1381" |
There was a problem hiding this comment.
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.
1 participant
Updated chart dependencies from new chart releases:
Auto-generated by charts repo publish workflow.
Summary by CodeRabbit