Skip to content

Sync component charts - #2393

Open
adam-cattermole wants to merge 1 commit into
mainfrom
sync-components
Open

adam-cattermole wants to merge 1 commit into
mainfrom
sync-components

Conversation

@adam-cattermole

@adam-cattermole adam-cattermole commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

Unsure if this is supposed to be automated but could see verify failing on another PR, and don't see an open PR to address

Summary by CodeRabbit

  • Chores
    • Updated the deployment chart revisions for the gateway and rate-limiting services. No user-facing functionality changes were included in this update.

Signed-off-by: Adam Cattermole <a.d.cattermole@gmail.com>
@coderabbitai

coderabbitai Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Walkthrough

The component chart sync declarations now use updated pinned refs for limitador-operator and mcp-gateway. Their repositories, chart paths and tracked branches are unchanged.

Changes: Component chart synchronisation

Layer / File(s) Summary
Update pinned chart refs
component-charts/sync.yaml
The pinned refs for limitador-operator and mcp-gateway have changed.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related PRs

Suggested labels: dependencies, component-chart

Suggested reviewers: boomatang

Merge Risk: Minimal · up to f8101

No actionable merge-blocking issue is established for these chart-ref updates. Merge after normal chart synchronization checks pass.

Pre-merge checks: Passed 4
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the primary change: synchronising component charts.
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.
Finishing Touches
Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

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

A rabbit checks each chart ref twice,
Then pins the hashes neat and nice.
Two entries shift; the paths stay put,
The sync file holds each updated foot.
I hop away; the refs are set.

CodeRabbit Verify

  • Run CodeRabbit Verify to test the changes in this pull request.
Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 443bf9d1-4db3-4c22-9424-0c48b20153a3
Commits

Reviewing files that changed from the base of the PR and between 38386c4 and f8101dd.

Files selected for processing: 1
  • component-charts/sync.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@codecov

codecov Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.32%. Comparing base (0f4f012) to head (f8101dd).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2393      +/-   ##
==========================================
- Coverage   77.54%   77.32%   -0.22%     
==========================================
  Files         157      157              
  Lines       17436    17436              
==========================================
- Hits        13520    13482      -38     
- Misses       3216     3244      +28     
- Partials      700      710      +10     
Flag Coverage Δ
bare-k8s-integration 21.28% <ø> (+<0.01%) ⬆️
controllers-integration 53.83% <ø> (-0.15%) ⬇️
controlplane-integration 11.10% <ø> (-0.02%) ⬇️
envoygateway-integration 44.05% <ø> (-0.29%) ⬇️
gatewayapi-integration 16.47% <ø> (-0.02%) ⬇️
istio-integration 47.37% <ø> (+0.06%) ⬆️
unit 40.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
api (u) 89.58% <ø> (ø)
internal (u) 78.78% <100.00%> (-0.26%) ⬇️
pkg (u) 62.46% <ø> (ø)
see 10 files with indirect coverage changes
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@adam-cattermole

Copy link
Copy Markdown
Member Author

Discovered a workflow that generates the PRs (one at at time) so superseded by:

@adam-cattermole

Copy link
Copy Markdown
Member Author

The auto-generated have a dependence on one another for the CI to pass so they're unmergeable.. I'll reopen this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant