feat(github-action)!: Update allenporter/flux-local action to 4.2.1 #41
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:
3.2.0
->4.2.1
Release Notes
allenporter/flux-local (allenporter/flux-local)
v4.2.1
Compare Source
What's Changed
Version
4.2.0
contains a bug in the diff action that caused it to never emit a diff, which is fixed in this release.Developer updates
Full Changelog: allenporter/flux-local@4.2.0...4.2.1
v4.2.0
Compare Source
What's Changed
New Contributors
Full Changelog: allenporter/flux-local@4.1.1...4.2.0
v4.1.1
Compare Source
What's Changed
Full Changelog: allenporter/flux-local@4.1.0...4.1.1
v4.1.0
Compare Source
What's Changed
Developer dependency updates
Full Changelog: allenporter/flux-local@4.0.0...4.1.0
v4.0.0
Compare Source
What's Changed
Native flux build
The primary change in this release is to move to use
flux build
internally. This means that theflux
CLI is now required to be present in the environment, similar to howkustomize
is already required. See documentation for the Github Action for details on how to setup the CLI environment. https://github.com/allenporter/flux-local/pull/392To simplify internals, multiple clusters in the same path are no longer supported. You can still use a multi-cluster repo if you specify
--path
to one of the clusters. This should be a no-op for most users of the github action since likely you already were setting a path argument.Diagnostics
You can now discover malormed or unexpected yaml files with
flux-local diagnostics
https://github.com/allenporter/flux-local/pull/401:Performance
With the move to
flux build
, we've been able to reduce some unnecessarykustomize
calls, improving internal caching, and parallelize some of the cluster commands. Speed has been improved by 2x even for smaller clusters with only a handful of kustomizations. https://github.com/allenporter/flux-local/pull/435Change Log
diagnostics
command to find yaml files that kustomize does no… by @allenporter in https://github.com/allenporter/flux-local/pull/401flux build ks
when building Kustomizations by @allenporter in https://github.com/allenporter/flux-local/pull/392Developer dependency updates
Full Changelog: allenporter/flux-local@3.2.0...4.0.0
Configuration
📅 Schedule: Branch creation - "on saturday" (UTC), 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.
This PR has been generated by Mend Renovate. View repository job log here.