Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump k8s.io/api from 0.28.2 to 0.29.2 #26

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 19, 2024

Bumps k8s.io/api from 0.28.2 to 0.29.2.

Commits
  • d473130 Update dependencies to v0.29.2 tag
  • f5eca04 Merge pull request #122959RomanBednar/automated-cherry-pick-of-#122728
  • fd1786f flag PersistentVolumeLastPhaseTransitionTime field as beta
  • a48c0a4 Merge pull request #122429 from MadhavJivrajani/tools-bump-129
  • 656e18f .*: bump golang.org/x/tools to v0.16.1
  • 0d77c34 Merge remote-tracking branch 'origin/master' into release-1.29
  • bb0a75c add beta comment for pod replacement policy
  • 0099855 update go.mod
  • d4b94f4 Merge pull request #121765 from mimowo/ready-pods-stable-api
  • 8391a3f Merge pull request #121764 from mimowo/backoff-limit-per-index-beta-api
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 19, 2024
@dependabot dependabot bot force-pushed the dependabot/go_modules/k8s.io/api-0.29.2 branch from a340797 to d6b741e Compare February 26, 2024 13:09
Bumps [k8s.io/api](https://github.com/kubernetes/api) from 0.28.2 to 0.29.2.
- [Commits](kubernetes/api@v0.28.2...v0.29.2)

---
updated-dependencies:
- dependency-name: k8s.io/api
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/k8s.io/api-0.29.2 branch from d6b741e to b99e227 Compare February 26, 2024 13:10
@rafalgalaw
Copy link
Collaborator

rafalgalaw commented Feb 26, 2024

@bavarianbidi How should we deal with these kind of dependency updates? Should we alway have our k8s packages up-to-date with the latest and greatest upstream version or do we update when we migrate to a new k8s version? Or should we offer multiple k8s compatible versions?

@bavarianbidi
Copy link
Member

@bavarianbidi How should we deal with these kind of dependency updates? Should we alway have our k8s packages up-to-date with the latest and greatest upstream version or do we update when we migrate to a new k8s version? Or should we offer multiple k8s compatible versions?

i've manually closed few of these PRs but didn't invested that much time on how to ignore major version bumps - as the packages doesn't follow a semantic version string.

As long as it's not requested i would keep it simple and just use the version we are using internally from our managed kubernetes service

@bavarianbidi
Copy link
Member

close for now and add the same configuration as we have in mercedes-benz/garm-operator#94 if it works as expected

Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 5, 2024

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/go_modules/k8s.io/api-0.29.2 branch March 5, 2024 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants