chore(deps): update dependency flux-local to v4 #100
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/flux-local-4.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.2.0->4.2.2Release Notes
allenporter/flux-local (flux-local)
v4.2.2Compare Source
What's Changed
Developer dependency updates
Full Changelog: https://github.com/allenporter/flux-local/compare/4.2.1...4.2.2
v4.2.1Compare Source
What's Changed
Version
4.2.0contains a bug in the diff action that caused it to never emit a diff, which is fixed in this release.Developer updates
Full Changelog: https://github.com/allenporter/flux-local/compare/4.2.0...4.2.1
v4.2.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/allenporter/flux-local/compare/4.1.1...4.2.0
v4.1.1Compare Source
What's Changed
Full Changelog: https://github.com/allenporter/flux-local/compare/4.1.0...4.1.1
v4.1.0Compare Source
What's Changed
Developer dependency updates
Full Changelog: https://github.com/allenporter/flux-local/compare/4.0.0...4.1.0
v4.0.0Compare Source
What's Changed
Native flux build
The primary change in this release is to move to use
flux buildinternally. This means that thefluxCLI is now required to be present in the environment, similar to howkustomizeis 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
--pathto 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 diagnosticshttps://github.com/allenporter/flux-local/pull/401:Performance
With the move to
flux build, we've been able to reduce some unnecessarykustomizecalls, 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
diagnosticscommand to find yaml files that kustomize does no… by @allenporter in https://github.com/allenporter/flux-local/pull/401flux build kswhen building Kustomizations by @allenporter in https://github.com/allenporter/flux-local/pull/392Developer dependency updates
Full Changelog: https://github.com/allenporter/flux-local/compare/3.2.0...4.0.0
Configuration
📅 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 this update again.
This PR has been generated by Renovate Bot.
3eb623a904to2677ae64e32677ae64e3tobbd9971a01Needs to be added to the container image.
bbd9971a01tocab7c29949cab7c29949to69bb55934269bb559342tobc10b5c164Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.