[github-actions]

🤖 I have created a release beep boop

0.54.0 (2026-10-23)

⚠ BREAKING CHANGES

• applier: rename FluxTrigger/ArgoCDTrigger to FluxClaim/ArgoCDClaim (#438)
• applier: hold an Argo CD Application's automated sync off, as a suspend (#437)
• one GitReceiver for many repositories (#432)
• replace ClusterProvider with a namespaced KubeProvider (#430)
• hold a repository branch with a GitBranch (#429)
• every GitTarget writing one repository branch must name the same GitProvider; a GitTarget writing it through another GitProvider than the oldest GitTarget there is refused with TargetConflict. Share a GitProvider across namespaces with spec.gitProviderRef.namespace and the GitProvider's spec.accessFrom. See UPGRADING.md.
• FluxTrigger spec.quietPeriod and status.source.prefetch are removed. An apply no longer waits for a quiet branch: the branch worker publishes what is pending, then applies. Server-side apply and kubectl's strict field validation reject a manifest that still sets spec.quietPeriod; a client with field validation off drops the field without an error. Remove spec.quietPeriod from FluxTrigger manifests before upgrading.

Features

• applier: hold an Argo CD Application's automated sync off, as a suspend (#437) (dec7056)
• hold a repository branch with a GitBranch (#429) (17c0c96)
• one GitReceiver for many repositories (#432) (6ae6272)
• recognize the applier's own writes, and flush before applying (#425) (2d98259)
• replace ClusterProvider with a namespaced KubeProvider (#430) (5d7d5f8)
• share a GitProvider across namespaces, and key the branch worker by repository (#428) (c49803f)

Bug Fixes

• attribution: credit a removal by what caused it, never by the watch's selector (#431) (a52caca)
• controller: publish a refreshed status.remote when the floor lifts, and time the bi-directional loop (#424) (3f00e09)

Code Refactoring

• applier: rename FluxTrigger/ArgoCDTrigger to FluxClaim/ArgoCDClaim (#438) (efc0203)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: d0dbf07c-59e9-4caa-8df7-4b4c82b315e4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}