feat(github-release): update flux group ( v2.4.0 → v2.6.2 ) (minor) #600
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.4.0->v2.6.2v2.4.0->v2.6.2Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.6.2Compare Source
v2.6.1Compare Source
Highlights
Flux v2.6.1 is a patch release that comes with various fixes. Users are encouraged to upgrade for the best experience.
Fixes:
Components changelog
What's Changed
Full Changelog: fluxcd/flux2@v2.6.0...v2.6.1
v2.6.0Compare Source
Highlights
Flux v2.6.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.6 GA blog post.
Overview of the new features:
flux artifactcommandsWaitForTerminationdeletion policy (Kustomization)DisableChartDigestTrackingfeature gate (HelmRelease)❤️ Big thanks to all the Flux contributors that helped us with this release!
Kubernetes compatibility
This release is compatible with the following Kubernetes versions:
v1.31>= 1.31.0v1.32>= 1.32.0v1.33>= 1.33.0OpenShift 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
Upgrade Flux from
v2.5.0tov2.6.0by following the upgrade guide.To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:
apiVersion: source.toolkit.fluxcd.io/v1in the YAML files that containOCIRepositorydefinitions.api.fluxcd.io/upgrade: "v2.6.0"to theOCIRepositoryresources. (this is not required if Flux Operator is used for upgrade)Bumping the APIs version in manifests can be done gradually.
It is advised to not delay this procedure as the deprecated versions will be removed after 6 months.
Components changelog
New Documentation
What's Changed
flux tracefor HRs fromOCIRepositorys by @makkes in https://github.com/fluxcd/flux2/pull/5349New Contributors
Full Changelog: fluxcd/flux2@v2.5.0...v2.6.0
v2.5.1Compare Source
Highlights
Flux v2.5.1 is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.
Fixes:
Components changelog
CLI Changelog
v2.5.0Compare Source
Highlights
Flux v2.5.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.5 GA blog post.
Overview of the new features:
GitRepositoryandImageUpdateAutomationAPI)KustomizationAPI)KustomizationAPI)KustomizationAPI)AlertAPI)AlertAPI)ReceiverAPI)❤️ Big thanks to all the Flux contributors that helped us with this release!
Kubernetes compatibility
This release is compatible with the following Kubernetes versions:
v1.30>= 1.30.0v1.31>= 1.31.0v1.32>= 1.32.0OpenShift 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
Upgrade Flux from
v2.4.0tov2.5.0by following the upgrade guide.There are no new API versions in this release, so no changes are required in the YAML manifests containing Flux resources.
Components changelog
CLI Changelog
flux diffskipping with kustomize-controllerflux debug kustomizationcommandflux debug helmreleasecommandfluxcd/pkgdependenciesConfiguration
📅 Schedule: 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.