Skip to content

chore: update canary-checker to 1.1.3-beta.158 - #630

Merged
flankbot merged 1 commit into
mainfrom
chore/update-chart-deps-20260622143406
Jun 22, 2026
Merged

chore: update canary-checker to 1.1.3-beta.158#630
flankbot merged 1 commit into
mainfrom
chore/update-chart-deps-20260622143406

Conversation

@flankbot

@flankbot flankbot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Updated chart dependencies from new chart releases:

  • canary-checker in chart/Chart.yaml: 1.1.3-beta.157 → 1.1.3-beta.158
  • canary-checker in agent-chart/Chart.yaml: 1.1.3-beta.157 → 1.1.3-beta.158

Auto-generated by charts repo publish workflow.

Summary by CodeRabbit

  • Chores
    • Updated canary-checker component dependency to the latest beta release, incorporating the latest improvements and fixes across Helm chart configurations.

@flankbot
flankbot enabled auto-merge (squash) June 22, 2026 14:34
@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

The canary-checker Helm dependency version is bumped from 1.1.3-beta.157 to 1.1.3-beta.158 in both agent-chart/Chart.yaml and chart/Chart.yaml. No other metadata or dependencies are changed.

Changes

canary-checker dependency bump

Layer / File(s) Summary
canary-checker version bump
agent-chart/Chart.yaml, chart/Chart.yaml
canary-checker dependency updated from 1.1.3-beta.157 to 1.1.3-beta.158 in both chart manifests.

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the main change: updating the canary-checker dependency to version 1.1.3-beta.158 across the Helm charts.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/update-chart-deps-20260622143406
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch chore/update-chart-deps-20260622143406

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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 `@agent-chart/Chart.yaml`:
- Line 14: The Chart.lock file has a stale lock for the canary-checker
dependency at version 1.1.3-beta.63, while Chart.yaml declares the updated
version 1.1.3-beta.158. Regenerate the Chart.lock lockfile using the appropriate
Helm command (such as helm dependency update or helm dependency lock) in the
agent-chart directory to sync the pinned canary-checker version with the version
declared in Chart.yaml. This ensures Helm installs the correct declared version
instead of the outdated locked version.
🪄 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: aa874659-3b90-49fb-9da3-25e3cbe17e79

📥 Commits

Reviewing files that changed from the base of the PR and between e5a4da1 and 2077a5d.

📒 Files selected for processing (2)
  • agent-chart/Chart.yaml
  • chart/Chart.yaml

Comment thread agent-chart/Chart.yaml
repository: https://flanksource.github.io/charts
- name: canary-checker
version: "1.1.3-beta.157"
version: "1.1.3-beta.158"

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 | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Searching for Chart.lock files..."
fd -i '^Chart\.lock$' .

echo
echo "Inspecting canary-checker entries in lockfiles..."
fd -i '^Chart\.lock$' . -x sh -c '
  echo "== $1 =="
  rg -n -A2 -B2 "canary-checker|version:" "$1"
' sh {}

Repository: flanksource/mission-control-chart

Length of output: 1553


Update Chart.lock to sync canary-checker dependency version.

The agent-chart/Chart.lock pins canary-checker to 1.1.3-beta.63 (line 7), while Chart.yaml declares 1.1.3-beta.158. Regenerate the lockfile to resolve this mismatch; otherwise Helm will install the outdated locked version instead of the declared dependency.

🤖 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 14, The Chart.lock file has a stale lock for
the canary-checker dependency at version 1.1.3-beta.63, while Chart.yaml
declares the updated version 1.1.3-beta.158. Regenerate the Chart.lock lockfile
using the appropriate Helm command (such as helm dependency update or helm
dependency lock) in the agent-chart directory to sync the pinned canary-checker
version with the version declared in Chart.yaml. This ensures Helm installs the
correct declared version instead of the outdated locked version.

@flankbot
flankbot merged commit c0a94f4 into main Jun 22, 2026
11 checks passed
@flankbot
flankbot deleted the chore/update-chart-deps-20260622143406 branch June 22, 2026 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant