Skip to content

chore(mise): update tool aqua:fluxcd/flux2 (2.10.0 ➔ 2.10.1) - #4941

Merged
dunce-bot[bot] merged 1 commit into
mainfrom
renovate/aqua-fluxcd-flux2-2.x
Nov 21, 2026
Merged

dunce-bot[bot] merged 1 commit into
mainfrom
renovate/aqua-fluxcd-flux2-2.x

Conversation

@dunce-bot

@dunce-bot dunce-bot Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
aqua:fluxcd/flux2 tools patch 2.10.0 → 2.10.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

fluxcd/flux2 (aqua:fluxcd/flux2)

v2.10.1

Compare Source

Highlights

Flux v2.10.1 is a patch release that fixes credential caching across the controllers, so changes to the credential.auth.fluxcd.io/username and gcp.auth.fluxcd.io/workload-identity-provider ServiceAccount annotations take effect on the next reconcile instead of continuing to use the previously cached authenticator until it expires or the controller restarts. It also resolves the default decryption ServiceAccount lazily for Kustomizations that only use Age or PGP keys, restores authentication to registries whose token service runs on a private address and after same-host HTTP to HTTPS redirects by updating ORAS to v2.7.0, and fixes Git checkouts that deleted the target of a relative symlink or got permanently stuck when the push branch removed a file that relative symlinks point to. 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 the credentials cache key so changes to the credential username or the GCP workload identity provider take effect on the next reconcile (helm-controller, kustomize-controller, source-controller, notification-controller, image-reflector-controller, image-automation-controller)
  • Fix resolving the default ServiceAccount for providers that don't use one (source-controller, image-reflector-controller, image-automation-controller)
  • Resolve the default decryption ServiceAccount lazily, only when a cloud KMS or Vault backend is used (kustomize-controller)
  • Restore authentication to registries whose token service runs on a private address and after same-host HTTP to HTTPS redirects by updating ORAS to v2.7.0 (source-controller)
  • Fix Git checkouts deleting the target of a relative symlink when the checked-out revision removes the symlink (source-controller)
  • Fix Git checkouts getting stuck when the push branch removes a file that relative symlinks point to (image-automation-controller)
  • Delete the reconcile duration metric series for objects that no longer exist (kustomize-controller)

Improvements:

  • Remove leftover object-level workload identity log message (helm-controller, kustomize-controller, source-controller, notification-controller, image-reflector-controller, image-automation-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.10.0...v2.10.1


Configuration

📅 Schedule: (in timezone America/New_York)

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

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate CLI.

@dunce-bot
dunce-bot Bot requested a review from dapperdivers as a code owner November 21, 2026 18:30
@dunce-bot dunce-bot Bot added the type/patch label Nov 21, 2026
@dunce-bot
dunce-bot Bot enabled auto-merge (squash) November 21, 2026 18:30
@dunce-bot

dunce-bot Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: mise.lock
�[33mmise�[0m �[33mWARN�[0m  /tmp/renovate/repos/github/dapperdivers/dapper-cluster/mise.lock uses lockfile format version 0; run `mise lock --upgrade` to enable the latest lockfile features
�[2mmise�[0m lock            aqua:fluxcd/flux2@2.10.1 linux-arm64
�[2mmise�[0m lock            aqua:fluxcd/flux2@2.10.1 linux-arm64-musl
�[2mmise�[0m lock            aqua:fluxcd/flux2@2.10.1 linux-x64-musl
�[2mmise�[0m lock            aqua:fluxcd/flux2@2.10.1 macos-x64
�[2mmise�[0m lock            aqua:fluxcd/flux2@2.10.1 linux-x64
�[2mmise�[0m lock            aqua:fluxcd/flux2@2.10.1 windows-x64
�[2mmise�[0m lock            aqua:fluxcd/flux2@2.10.1 macos-arm64
�[31mmise�[0m �[31mERROR�[0m lockfile generation would downgrade recorded provenance; previous files were preserved: recorded slsa but the new entry has no provenance. If the registry recipe no longer provides what mise needs to verify it, fix the recipe or lock the tool through another backend, or, if the recipe names the SLSA provenance asset but no signer, set slsa_signer_identity and slsa_signer_issuer in the tool options so the SLSA provenance can be verified and recorded again (aqua:fluxcd/flux2@2.10.1 on linux-arm64, aqua:fluxcd/flux2)
�[31mmise�[0m �[31mERROR�[0m Version: 2026.11.12 linux-x64 (2026-11-21)
�[31mmise�[0m �[31mERROR�[0m �[2mRun with --verbose or MISE_VERBOSE=1 for more information�[0m

@dunce-bot
dunce-bot Bot merged commit 96137ba into main Nov 21, 2026
7 of 8 checks passed
@dunce-bot
dunce-bot Bot deleted the renovate/aqua-fluxcd-flux2-2.x branch November 21, 2026 19:52
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