chore: remove Cozystack-specific packaging (packages/) from the operator repo#23
Conversation
The packages/ directory held the Cozystack package wrapper (cozy-kilo-clustermesh-operator) and its OCI bundle. That packaging is Cozystack-specific and does not belong in the generic operator repo. Drop packages/ and the release-workflow steps that stamped, packaged and pushed the wrapper chart and the Cozystack package bundle (and the docker login that only the bundle's flux push needed). The release still publishes the operator image and the generic Helm chart (charts/kilo-clustermesh-operator). Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
|
Warning Review limit reached
More reviews will be available in 44 minutes and 24 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request deletes the cozy-kilo-clustermesh-operator Helm chart, removing its Chart.yaml, values.yaml, and dependency lock files. There are no review comments, so I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
1 participant
Removes the Cozystack package wrapper
packages/system/kilo-clustermesh-operator/(cozy-kilo-clustermesh-operator) and the release-workflow steps that stamped, packaged and pushed the wrapper chart + the Cozystack package OCI bundle (plus the docker login only the bundle's flux push needed).This operator is a generic kilo-io-style project; Cozystack-specific packaging belongs in the Cozystack monorepo, not here. The release still publishes the operator image and the generic Helm chart (
charts/kilo-clustermesh-operator).