chore: update canary-checker to 1.1.3-beta.148#620
Conversation
WalkthroughThe Changescanary-checker Dependency Bump
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: 1
🤖 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 `@chart/Chart.yaml`:
- Line 19: The canary-checker dependency version has been updated to
1.1.3-beta.148 in both Chart.yaml files, but the corresponding Chart.lock files
in the chart and agent-chart directories have not been regenerated, causing them
to still pin to older versions. Regenerate the lockfiles by running the helm
dependency update command in both the chart directory and the agent-chart
directory to ensure the Chart.lock files reflect the updated dependency versions
specified in their respective Chart.yaml files.
🪄 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: 6f19e05f-bf67-443c-9cfa-89ac4c1d93c6
📒 Files selected for processing (2)
agent-chart/Chart.yamlchart/Chart.yaml
| repository: https://flanksource.github.io/charts | ||
| - name: canary-checker | ||
| version: "1.1.3-beta.147" | ||
| version: "1.1.3-beta.148" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify Chart.lock files exist and check their canary-checker pinned versions
fd -e Chart.lock -x bash -c 'echo "=== {} ===" && grep -A 2 "name: canary-checker" {} 2>/dev/null || echo " (no canary-checker found)"'Repository: flanksource/mission-control-chart
Length of output: 59
🏁 Script executed:
# Check if chart/Chart.lock exists and show its content
ls -la chart/Chart.lock 2>&1
# Also verify chart/Chart.yaml line 19
echo "=== Chart.yaml line 19 ==="
sed -n '19p' chart/Chart.yaml 2>&1
# Find all Chart.lock files in the repository
echo "=== All Chart.lock files ==="
find . -name "Chart.lock" -type f 2>&1Repository: flanksource/mission-control-chart
Length of output: 272
🏁 Script executed:
# Show content of chart/Chart.lock
echo "=== chart/Chart.lock ==="
cat chart/Chart.lock
# Show content of agent-chart/Chart.lock
echo -e "\n=== agent-chart/Chart.lock ==="
cat agent-chart/Chart.lockRepository: flanksource/mission-control-chart
Length of output: 1367
🏁 Script executed:
# Check agent-chart/Chart.yaml to see what version it specifies
echo "=== agent-chart/Chart.yaml dependency version ==="
rg "canary-checker" agent-chart/Chart.yaml -A 3 -B 1Repository: flanksource/mission-control-chart
Length of output: 325
Both chart/Chart.yaml and agent-chart/Chart.yaml specify canary-checker version 1.1.3-beta.148, but the corresponding lockfiles are out of sync:
chart/Chart.lockpins it to1.1.3-beta.107agent-chart/Chart.lockpins it to1.1.3-beta.63
Helm uses Chart.lock to resolve exact dependency versions during installation/upgrade. Without regenerating these lockfiles, actual deployments will continue to use the older pinned versions, making the version bumps ineffective in production.
Action required: Regenerate both lockfiles by running helm dependency update in the chart/ and agent-chart/ directories.
🤖 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 19, The canary-checker dependency version has been
updated to 1.1.3-beta.148 in both Chart.yaml files, but the corresponding
Chart.lock files in the chart and agent-chart directories have not been
regenerated, causing them to still pin to older versions. Regenerate the
lockfiles by running the helm dependency update command in both the chart
directory and the agent-chart directory to ensure the Chart.lock files reflect
the updated dependency versions specified in their respective Chart.yaml files.
1 participant
Updated chart dependencies from new chart releases:
Auto-generated by charts repo publish workflow.
Summary by CodeRabbit