Skip to content

chore(deps): update fluxcd/flux2 action to v2.9.6 - #42

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/fluxcd-flux2-2.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/fluxcd-flux2-2.x

Conversation

@renovate

@renovate renovate Bot commented Sep 30, 2025 •

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
fluxcd/flux2 action minor v2.6.4 → v2.9.6

Release Notes

fluxcd/flux2 (fluxcd/flux2)

v2.9.6

Compare Source

Highlights

Flux v2.9.6 is a patch release that stops helm-controller from reapplying chart CRDs on every upgrade when server-side apply is enabled, and recovers HelmReleases left with a drifted Ready=Unknown condition after a failed status patch. source-controller normalizes Azure Blob listing ETags so unchanged containers are no longer re-downloaded on every reconcile, and evicts stale Helm repository index entries from the cache so repositories with frequently changing indexes no longer fail with "Cache is full". kustomize-controller extends SOPS decryption error redaction to spec.postBuild.substituteFrom values, so substituted secrets echoed back in API validation errors are masked out of status conditions and events, and adds the opt-in DisableCommitStatusEvent feature gate. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Stop reapplying chart CRDs on upgrades when using server-side apply with the default Create policy (helm-controller)
  • Recover HelmReleases stranded with a drifted Ready=Unknown condition after a failed status patch (helm-controller)
  • Ignore NotFound when deleting the HelmChart (helm-controller)
  • Normalize Azure Blob listing ETags so unchanged containers are not re-downloaded on every reconcile (source-controller)
  • Evict stale Helm repository index entries from the cache to avoid "Cache is full" errors (source-controller)
  • Extend SOPS decryption error redaction to spec.postBuild.substituteFrom values (kustomize-controller)

Improvements:

  • Add the opt-in DisableCommitStatusEvent feature gate (kustomize-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.9.5...v2.9.6

v2.9.5

Compare Source

Highlights

Flux v2.9.5 is a patch release that moves helm-controller and source-controller back to upstream Helm, now at v4.2.4, dropping the temporary Flux fork. It hardens the handling of kubeconfig Secrets in helm-controller and kustomize-controller, which now reject kubeconfigs referencing files on the local filesystem and require credentials and certificates to be embedded inline. It also stops kustomize-controller from leaving behind the temporary directories of a previous process that exited without running its cleanup, and fixes a crash in post-build substitution where a substring expression with a negative length, e.g. ${VAR:2:-1}, panicked instead of counting back from the end of the string like Bash does. Across all controllers and the CLI, the fluxcd/pkg dependencies have been updated, bringing Kubernetes to 1.36.4. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Validate kubeconfigs from .spec.kubeConfig Secrets, rejecting local file references in certificate-authority, tokenFile, client-certificate and client-key; credentials and certificates must be embedded inline (helm-controller, kustomize-controller)
  • Purge temporary directories at startup (kustomize-controller)
  • Fix panic on negative-length substring expressions in post-build substitution (kustomize-controller, flux CLI)

Improvements:

  • Move back to upstream Helm v4.2.4, dropping the Flux fork (helm-controller, source-controller)
  • Update fluxcd/pkg dependencies, which bring Kubernetes to 1.36.4 (all controllers, flux CLI)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.9.4...v2.9.5

v2.9.4

Compare Source

Highlights

Flux v2.9.4 is a patch release that ships various fixes to the Flux controllers, covering source-watcher tarball extraction and glob expansion limits, the refspecs accepted by ImageUpdateAutomation, the HTTP request limits of the notification-controller servers, and Helm repository index loading, OCI chart digest pinning, Bucket error handling and GCS static authentication in source-controller. On the CLI side, flux migrate -f now supports migrating repositories to Flux 2.9. Users are encouraged to upgrade for the best experience.

Note that this release contains CRD schema changes for ArtifactGenerator and ImageUpdateAutomation; both CRDs must be updated along with the controllers.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Confine tarball extraction and bound glob expansion (source-watcher)
  • Disallow force-update and deletion via refspecs (image-automation-controller)
  • Unify HTTP server request limits (notification-controller)
  • Align Helm repository index loading with upstream Helm v4 (source-controller)
  • Improve error handling in Bucket reconciliation (source-controller)
  • Pin OCI chart verification by digest (source-controller)
  • Limit GCS static authentication to service account keys (source-controller)
  • Restrict the allow-webhooks network policy to the receiver port (flux CLI)

Improvements:

  • Add support for migrating repositories to 2.9 in flux migrate -f (flux CLI)
  • Update fluxcd/pkg dependencies, which align the ECR host detection with upstream (source-controller, image-reflector-controller, flux CLI)
  • Update Bitbucket Cloud receiver guidance (notification-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.9.3...v2.9.4

v2.9.3

Compare Source

Highlights

Flux v2.9.3 is a patch release. It fixes empty lines vanishing from rendered Helm chart manifests, HelmReleases being marked as tested when their Helm test hooks never ran, and spec.images entries that set only some image fields discarding the remaining fields already declared for the same image in the kustomization.yaml. The latter affects both kustomize-controller and the flux build|diff kustomization commands. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix empty lines vanishing from rendered chart manifests (helm-controller)
  • Fix HasBeenTested for all corner cases, where a release could be marked as tested although its Helm test hooks never ran (helm-controller)
  • Fix a spec.images entry setting only some of the image fields discarding the remaining fields already declared for the same image in the kustomization.yaml at spec.path, e.g. overriding only newName produced an untagged image reference (kustomize-controller, flux CLI)

Improvements:

  • Update fluxcd/pkg dependencies
  • Include source-watcher in the OCI flux-manifests artifact

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.9.2...v2.9.3

v2.9.2

Compare Source

Highlights

Flux v2.9.2 is a patch release. The main fix addresses a regression introduced in
v2.9.1 where a Kustomization with openapi.path pointing to a URL failed to
reconcile with failed to read OpenAPI schema. This release also corrects several
CRD field descriptions that contained inaccurate or leaked content. Users are
encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix a regression where a Kustomization with openapi.path pointing to a URL failed to reconcile with failed to read OpenAPI schema (kustomize-controller)
  • Fix the HelmChart CRD description for .status.url, which pointed users at BucketStatus.Artifact instead of HelmChartStatus.Artifact (source-controller)
  • Fix the ImageRepository CRD description for .status.observedExclusionList, which referred to spec.lastScanResult instead of status.lastScanResult (image-reflector-controller)
  • Fix the ImageUpdateAutomation CRD description for .status.observedSourceRevision, which had a stray Go struct declaration leaking into it (image-automation-controller)

Improvements:

  • Update fluxcd/pkg dependencies
Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.9.1...v2.9.2

v2.9.1

Compare Source

v2.9.0

Compare Source

Highlights

Flux v2.9.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a compressive overview of new features and API changes included in this release, please refer to the Announcing Flux 2.9 GA blog post.

Overview of the new features:

  • Flux CLI Plugin System with the Mirror and Schema plugins (flux plugin)
  • Server-Side Apply field ignore rules for fine-grained drift control (Kustomization)
  • SOPS decryption with the Age post-quantum cipher (Kustomization)
  • Kubernetes Workload Identity authentication for OpenBao and Vault (Kustomization)
  • Helm post-render strategies, including chart hooks support (HelmRelease)
  • Literal mode for Helm values references mirroring helm --set-literal (HelmRelease)
  • Allow empty kind in CEL health check expressions (Kustomization, HelmRelease)
  • Git commit signing and verification with SSH keys (GitRepository, ImageUpdateAutomation)
  • AWS CodeCommit authentication using Workload Identity (GitRepository)
  • Custom Sigstore trusted root for keyless verification in air-gapped environments (OCIRepository)
  • Path pattern directory discovery for monorepos (ArtifactGenerator)
  • Secret-less, OIDC-secured webhook Receivers (Receiver)

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version Minimum required
v1.34 >= 1.34.1
v1.35 >= 1.35.0
v1.36 >= 1.36.0

[!NOTE]
Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift compatibility

Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub using Flux Operator. The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts, and S3-compatible storage.

Upgrade procedure

⚠️ The Flux APIs image.toolkit.fluxcd.io/v1beta2 and notification.toolkit.fluxcd.io/v1beta2
have reached end-of-life and have been removed from the CRDs.

Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from older versions of Flux to v2.9.

Components changelog
CLI changelog
New Contributors

Full Changelog: fluxcd/flux2@v2.8.0...v2.9.0

v2.8.8

Compare Source

Highlights

Flux v2.8.8 is a patch release that includes CVE fixes via go-git v5.19.1 (source-controller, image-automation-controller), reliability fixes in helm-controller and source-controller, the move of Helm back to upstream v4.2.0, support for GCP sovereign cloud artifact registries, and dependency updates. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Add a configurable HTTP timeout for artifact fetching, preventing fetches that could block indefinitely and stall reconciliations (helm-controller)
  • Fix unbounded memory growth caused by a Kubernetes client transport retry wrapper accumulating on every reconcile (helm-controller)
  • Stop force-applying non-CRD objects placed under a chart's crds/ directory (helm-controller)
  • Fix the Helm test action failing to find releases with names longer than 53 characters (helm-controller)
  • Improve path handling in the source reconcilers (source-controller)
  • Support Helm semver build-metadata encoding in OCIRepository tags (source-controller)

Improvements:

  • Update go-git to v5.19.1 which fixes CVE-2026-45571 and CVE-2026-45570 (source-controller, image-automation-controller)
  • Move Helm back to upstream v4.2.0 (source-controller, helm-controller)
  • Add support for GCP sovereign cloud artifact registries (source-controller, image-reflector-controller)
  • Upgrade Kubernetes to 1.36.1 (source-controller, helm-controller)
  • Update fluxcd/pkg dependencies
Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.8.7...v2.8.8

v2.8.7

Compare Source

Highlights

Flux v2.8.7 is a patch release that includes a bug fix in kustomize-controller, a CVE fix in source-controller and image-automation-controller via go-git v5.19.0, and dependency updates. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix management of objects annotated with kustomize.toolkit.fluxcd.io/ssa: IfNotPresent where non-namespaced resources were being deleted and recreated on each reconciliation (kustomize-controller)

Improvements:

  • Update go-git to v5.19.0 which fixes CVE-2026-45022 (source-controller, image-automation-controller)
  • Update fluxcd/pkg dependencies (source-controller, kustomize-controller, image-automation-controller)
Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.8.6...v2.8.7

v2.8.6

Compare Source

Highlights

Flux v2.8.6 is a patch release that includes bug fixes and improvements across helm-controller, image-automation-controller, kustomize-controller, notification-controller, and source-controller. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix a post-renderer conflict between overlapping hooks and templates (helm-controller)
  • Ignore force replace when server-side apply is enabled (helm-controller)
  • Fix a regression where generic providers would not forward commit status events (notification-controller)
  • Require the audience field on the GCR Receiver secret for tighter verification — will become mandatory in Flux v2.9 (notification-controller)

Improvements:

  • Introduce the MigrateAPIVersion feature gate for migrating the API version of resources in managed field entries (kustomize-controller)
  • Update go-git to v5.18.0 bringing performance improvements for Git operations (source-controller, image-automation-controller)
Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.8.5...v2.8.6

v2.8.5

Compare Source

Highlights

Flux v2.8.5 is a patch release that includes bug fixes and improvements across kustomize-controller, source-controller, and notification-controller. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix a race condition where a cancelled reconciliation could leave stale data in the cache, causing Kustomizations to get stuck (kustomize-controller)
  • Fix Azure Blob prefix option not being passed to the storage client (source-controller)

Improvements:

  • Improve error message for encrypted SSH keys without password (source-controller)
  • Add optional email and audience fields to the GCR Receiver for tighter verification (notification-controller)
  • Add provider manifest example for Azure Event Hub managed identity authentication (notification-controller)
Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.8.4...v2.8.5

v2.8.4

Compare Source

Highlights

Flux v2.8.4 is a patch release that includes fixes for the Flux CLI. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix flux build ks and flux diff ks on Windows
  • Fix --source flag validation in create kustomization command
CLI changelog

Full Changelog: fluxcd/flux2@v2.8.3...v2.8.4

v2.8.3

Compare Source

Highlights

Flux v2.8.3 is a patch release that fixes a regression in helm-controller. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix templating errors for charts that include --- in the content, e.g. YAML separators, embedded scripts, CAs inside ConfigMaps (helm-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.2...v2.8.3

v2.8.2

Compare Source

Highlights

Flux v2.8.2 is a patch release that comes with various fixes. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix enqueuing new reconciliation requests for events on source Flux objects when they are already reconciling the revision present in the watch event (kustomize-controller, helm-controller)
  • Fix the Go templates bug of YAML separator --- getting concatenated to apiVersion: by updating to Helm 4.1.3 (helm-controller)
  • Fix canceled HelmReleases getting stuck when they don't have a retry strategy configured by introducing a new feature gate DefaultToRetryOnFailure that improves the experience when the CancelHealthCheckOnNewRevision is enabled (helm-controller)
  • Fix the auth scope for Azure Container Registry to use the ACR-specific scope (source-controller, image-reflector-controller)
  • Fix potential Denial of Service (DoS) during TLS handshakes (CVE-2026-27138) by building all controllers with Go 1.26.1

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.1...v2.8.2

v2.8.1

Compare Source

Highlights

Flux v2.8.1 is a patch release that comes with various fixes. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Fix Git commit status events being dropped for Kustomizations (notification-controller)
  • Fix health check for StatefulSets when the Pods are Pending/Unschedulable during rollout (helm-controller, kustomize-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.0...v2.8.1

v2.8.0

Compare Source

Highlights

Flux v2.8.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a compressive overview of new features and API changes included in this release, please refer to the Announcing Flux 2.8 GA blog post.

Overview of the new features:

  • Helm v4 support, including server-side apply and kstatus-based health checking (HelmRelease)
  • Readiness evaluation of Helm-managed objects with CEL expressions (HelmRelease)
  • Improved observability of Helm releases with inventory tracking in .status.inventory (HelmRelease)
  • Reduced the mean time to recovery of Flux-managed applications via CancelHealthCheckOnNewRevision feature gate (Kustomization, HelmRelease)
  • Support for commenting on Pull Requests directly from Flux notifications (Provider)
  • Custom SSA apply stages for ordering resource application in kustomize-controller (Kustomization)
  • Automatic GitHub App installation ID lookup from the repository owner (GitRepository, ImageUpdateAutomation, Provider)
  • Support for Cosign v3 for verifying OCI artifacts and container images (OCIRepository)
  • ArtifactGenerator support for extracting and modifying Helm charts (ArtifactGenerator)
  • Bypass cache when fetching source objects via DirectSourceFetch feature gate (Kustomization, HelmRelease, ArtifactGenerator)

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version Minimum required
v1.33 >= 1.32.0
v1.34 >= 1.34.1
v1.35 >= 1.35.0

[!NOTE]
Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift compatibility

Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub using Flux Operator. The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts, and S3-compatible storage.

Upgrade procedure

⚠️ The Flux APIs v1beta2 and v2beta2 (deprecated in 2024) have reached end-of-life and have been removed from the CRDs.

Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from older versions of Flux to v2.8.

Components changelog

CLI changelog

❗ Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from gabe565 as a code owner September 30, 2025 11:29
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 4082b26 to 2f6f1f5 Compare October 6, 2025 15:50
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.7.0 chore(deps): update fluxcd/flux2 action to v2.7.1 Oct 6, 2025
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 2f6f1f5 to 7149773 Compare October 6, 2025 19:29
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.7.1 chore(deps): update fluxcd/flux2 action to v2.7.2 Oct 8, 2025
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 7149773 to d59bbb2 Compare October 8, 2025 22:27
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from d59bbb2 to c64380d Compare October 28, 2025 16:47
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.7.2 chore(deps): update fluxcd/flux2 action to v2.7.3 Oct 28, 2025
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from c64380d to e5f3c52 Compare November 24, 2025 18:56
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.7.3 chore(deps): update fluxcd/flux2 action to v2.7.4 Nov 24, 2025
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.7.4 chore(deps): update fluxcd/flux2 action to v2.7.5 Nov 27, 2025
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from e5f3c52 to e97de2f Compare November 27, 2025 13:01
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from e97de2f to b498a62 Compare December 15, 2025 15:16
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.7.5 chore(deps): update fluxcd/flux2 action to v2.8.0 Feb 24, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from b498a62 to 884e9bb Compare February 24, 2026 16:49
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.0 chore(deps): update fluxcd/flux2 action to v2.8.1 Feb 27, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 884e9bb to e8f20c1 Compare February 27, 2026 15:31
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.1 chore(deps): update fluxcd/flux2 action to v2.8.2 Mar 14, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from e8f20c1 to 480aa2a Compare March 14, 2026 12:08
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.2 chore(deps): update fluxcd/flux2 action to v2.8.3 Mar 16, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 480aa2a to da2cde3 Compare March 16, 2026 15:44
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from da2cde3 to 2014f3f Compare April 7, 2026 15:33
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.3 chore(deps): update fluxcd/flux2 action to v2.8.4 Apr 7, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 2014f3f to 8bf8983 Compare April 7, 2026 19:02
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.4 chore(deps): update fluxcd/flux2 action to v2.8.5 Apr 7, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 8bf8983 to 67e2e06 Compare April 21, 2026 18:02
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.5 chore(deps): update fluxcd/flux2 action to v2.8.6 Apr 21, 2026
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.6 chore(deps): update fluxcd/flux2 action to v2.8.7 May 12, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 67e2e06 to 60a8181 Compare May 12, 2026 13:52
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 60a8181 to 80d1543 Compare May 20, 2026 12:02
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.7 chore(deps): update fluxcd/flux2 action to v2.8.8 May 20, 2026
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.8 chore(deps): update fluxcd/flux2 action to v2.9.0 Jun 30, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 80d1543 to 150d9b9 Compare June 30, 2026 17:43
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 150d9b9 to 6583172 Compare July 7, 2026 18:10
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.9.0 chore(deps): update fluxcd/flux2 action to v2.9.1 Jul 7, 2026
@cursor

cursor Bot commented Jul 7, 2026

Copy link
Copy Markdown

Bugbot is not enabled for this team, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 6583172 to bca3491 Compare July 13, 2026 17:57
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.9.1 chore(deps): update fluxcd/flux2 action to v2.9.2 Jul 13, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from bca3491 to 3e5b10b Compare July 23, 2026 16:32
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.9.2 chore(deps): update fluxcd/flux2 action to v2.9.3 Jul 23, 2026
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.9.3 chore(deps): update fluxcd/flux2 action to v2.9.4 Aug 7, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 3e5b10b to 3415445 Compare August 7, 2026 15:57
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 3415445 to c09f426 Compare August 31, 2026 20:33
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.9.4 chore(deps): update fluxcd/flux2 action to v2.9.5 Aug 31, 2026
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.9.5 chore(deps): update fluxcd/flux2 action to v2.9.6 Oct 1, 2026
@renovate
renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from c09f426 to 7dfbbe1 Compare October 1, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants