ZeroDownTime/KubeZero
3
0
Fork 0
Code Issues 1 Pull Requests 31 Packages Projects Releases Wiki Activity

chore(deps): update ghcr.io/k8snetworkplumbingwg/multus-cni docker tag to v4.2.1 #122

Open
renovate wants to merge 1 commits from renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x into main
pull from: renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x
merge into: ZeroDownTime:main
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2025-06-06 03:01:56 +00:00
Member
Copy Link

This PR contains the following updates:

Package Update Change
ghcr.io/k8snetworkplumbingwg/multus-cni patch v4.2.0 -> v4.2.1

Release Notes

k8snetworkplumbingwg/multus-cni (ghcr.io/k8snetworkplumbingwg/multus-cni)

v4.2.1

Compare Source

  • Thick client: mount multus-conf-dir
  • Subdirectory CNI chain loading e2e tests
  • Functionality for Aux CNI Chain using subdirectory based CNI configuration loading.
  • Use cross-compilation for thick plugin build
  • Add trivy vulnerability scanner in build step
  • Properly structure empty CNI result return
  • Bumps to libcni v1.3.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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/k8snetworkplumbingwg/multus-cni](https://github.com/k8snetworkplumbingwg/multus-cni) | patch | `v4.2.0` -> `v4.2.1` | --- ### Release Notes <details> <summary>k8snetworkplumbingwg/multus-cni (ghcr.io/k8snetworkplumbingwg/multus-cni)</summary> ### [`v4.2.1`](https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v4.2.1) [Compare Source](https://github.com/k8snetworkplumbingwg/multus-cni/compare/v4.2.0...v4.2.1) - Thick client: mount multus-conf-dir - Subdirectory CNI chain loading e2e tests - Functionality for Aux CNI Chain using subdirectory based CNI configuration loading. - Use cross-compilation for thick plugin build - Add trivy vulnerability scanner in build step - Properly structure empty CNI result return - Bumps to libcni v1.3.0 </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC4yMi4xIiwidXBkYXRlZEluVmVyIjoiNDAuMjIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsicmVub3ZhdGUiXX0=-->
renovate added 1 commit 2025-06-06 03:01:56 +00:00
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x:renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x
git checkout renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-4.x
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
renovate
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jenkins renovate stefan
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ZeroDownTime/KubeZero#122
No description provided.
Delete Branch "renovate/ghcr.io-k8snetworkplumbingwg-multus-cni-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?