chore: update config-db to 0.0.1391#636
Merged
Merged
Conversation
WalkthroughTwo Helm chart dependency versions are bumped from ChangesHelm Dependency Version Bumps
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: Sync the chart lockfile with the updated config-db dependency
version. In `Chart.yaml` the `config-db` dependency is pinned to `0.0.1391`, but
`Chart.lock` still references `0.0.1161`; update the lockfile entry so Helm
lockfile-based installs resolve the same version as `Chart.yaml`. Focus on the
`config-db` dependency entries in `Chart.lock` and keep the version/repository
metadata aligned with the current chart pin.
In `@chart/Chart.yaml`:
- Line 16: The Helm dependency lock is out of sync with the version bump in
Chart.yaml, so regenerate chart/Chart.lock after updating config-db to 0.0.1391.
Make sure the lockfile entry for config-db is refreshed to the same resolved
version as the Chart.yaml dependency, and 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: 3b856136-197c-4c9f-903a-069dd4ef7208
📒 Files selected for processing (2)
agent-chart/Chart.yamlchart/Chart.yaml
| dependencies: | ||
| - name: config-db | ||
| version: "0.0.1390" | ||
| version: "0.0.1391" |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
python - <<'PY'
import re
from pathlib import Path
checks = [
("agent-chart/Chart.yaml", "agent-chart/Chart.lock", "config-db"),
("chart/Chart.yaml", "chart/Chart.lock", "config-db"),
("chart/Chart.yaml", "chart/Chart.lock", "apm-hub"),
]
def parse_versions(path):
text = Path(path).read_text()
deps = {}
current = None
for line in text.splitlines():
m_name = re.match(r'^\s*-\s*name:\s*"?([^"]+)"?\s*$', line)
if m_name:
current = m_name.group(1)
continue
m_ver = re.match(r'^\s*version:\s*"?([^"]+)"?\s*$', line)
if m_ver and current:
deps[current] = m_ver.group(1)
current = None
return deps
for chart, lock, dep in checks:
cv = parse_versions(chart).get(dep)
lv = parse_versions(lock).get(dep)
print(f"{dep}: {chart}={cv} | {lock}={lv}")
PYRepository: flanksource/mission-control-chart
Length of output: 375
Sync agent-chart/Chart.lock with the config-db bump. Chart.yaml now pins config-db to 0.0.1391, but Chart.lock still has 0.0.1161, so lockfile-based installs will keep the old version.
🤖 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, Sync the chart lockfile with the updated
config-db dependency version. In `Chart.yaml` the `config-db` dependency is
pinned to `0.0.1391`, but `Chart.lock` still references `0.0.1161`; update the
lockfile entry so Helm lockfile-based installs resolve the same version as
`Chart.yaml`. Focus on the `config-db` dependency entries in `Chart.lock` and
keep the version/repository metadata aligned with the current chart pin.
| condition: apm-hub.enabled | ||
| - name: config-db | ||
| version: "0.0.1390" | ||
| version: "0.0.1391" |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major
🧩 Analysis chain
🏁 Script executed:
set -euo pipefail
printf 'Chart.yaml:\n'
sed -n '1,120p' chart/Chart.yaml
printf '\nChart.lock:\n'
sed -n '1,200p' chart/Chart.lockRepository: flanksource/mission-control-chart
Length of output: 2334
🏁 Script executed:
set -euo pipefail
printf 'Chart.yaml:\n'
sed -n '1,120p' chart/Chart.yaml
printf '\nChart.lock:\n'
sed -n '1,200p' chart/Chart.lockRepository: flanksource/mission-control-chart
Length of output: 2334
🏁 Script executed:
set -euo pipefail
printf 'Chart.yaml:\n'
sed -n '1,120p' chart/Chart.yaml
printf '\nChart.lock:\n'
sed -n '1,200p' chart/Chart.lockRepository: flanksource/mission-control-chart
Length of output: 2334
🏁 Script executed:
set -euo pipefail
printf 'Chart.yaml:\n'
sed -n '1,120p' chart/Chart.yaml
printf '\nChart.lock:\n'
sed -n '1,200p' chart/Chart.lockRepository: flanksource/mission-control-chart
Length of output: 2334
Regenerate chart/Chart.lock for config-db 0.0.1391
chart/Chart.yaml bumps config-db to 0.0.1391, but chart/Chart.lock still resolves config-db to 0.0.1339. Refresh and commit the lockfile so the chart pulls the intended release.
🤖 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, The Helm dependency lock is out of sync with
the version bump in Chart.yaml, so regenerate chart/Chart.lock after updating
config-db to 0.0.1391. Make sure the lockfile entry for config-db is refreshed
to the same resolved version as the Chart.yaml dependency, and commit the
updated chart/Chart.lock alongside the Chart.yaml change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated chart dependencies from new chart releases:
Auto-generated by charts repo publish workflow.
Summary by CodeRabbit
0.0.1390to0.0.1391in two charts.