chore(deps): update dependency chainguard-dev/apko to v1.2.39 #9
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/chainguard-dev-apko-1.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:
1.2.37→1.2.39Release Notes
chainguard-dev/apko (chainguard-dev/apko)
v1.2.39Compare Source
Changelog
351252dbuild: make WithAnnotations and WithFormat order-independent (#2413)302ff3cerofs: add a privileged CI job that mounts a layer (#2414)25f7e68fix(oci): tolerate an unreadable config when building the index (#2416)v1.2.38: apko 1.2.38Compare Source
What's Changed
make lint, reading its version from CI by @smoser in #2411[edit] ⚠️ Contains Regression (#2417 library only): GenerateIndex/GenerateDockerIndex fail with failed to get config file when passed a v1.Image that can't serve its config (introduced by #2249). The apko CLI is unaffected. Pin v1.2.37 or see #2416
Full Changelog: https://github.com/chainguard-dev/apko/compare/v1.2.37...v1.2.38
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 CLI.
Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
chore(deps): update dependency chainguard-dev/apko to v1.2.38to chore(deps): update dependency chainguard-dev/apko to v1.2.39240cbdd8254697ef00ae