Skip to content

fix(deps): update kubernetes monorepo to v0.37.2 - #337

Open
ferrlabs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kubernetes-monorepo
Open

ferrlabs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kubernetes-monorepo

Conversation

@ferrlabs-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
k8s.io/api v0.37.1 → v0.37.2 age adoption passing confidence
k8s.io/apimachinery v0.37.1 → v0.37.2 age adoption passing confidence
k8s.io/client-go v0.37.1 → v0.37.2 age adoption passing confidence

Release Notes

kubernetes/api (k8s.io/api)

v0.37.2

Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)

v0.37.2

Compare Source

kubernetes/client-go (k8s.io/client-go)

v0.37.2

Compare Source


Configuration

📅 Schedule: (UTC)

  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate CLI.

Signed-off-by: ferrlabs-renovate[bot] <282300760+ferrlabs-renovate[bot]@users.noreply.github.com>

@ferrfleet-interne ferrfleet-interne Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Patch bump of k8s.io/api, apimachinery and client-go from v0.37.1 to v0.37.2. All three move together and go.sum has matching entries. I did not read the upstream release notes; a patch release within the same minor should not change the API, and I found no breaking change to check against this repo. controller-runtime v0.25.2 stays on the same 0.37 minor line.

CI (Lint, Test, kind smoke test, security scans) was still queued or running when I reviewed, so I have not seen the results. Approving on the change itself; check that those jobs go green before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants