Bump k8s.io/cloud-provider from 0.26.3 to 0.27.0 #189
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
Bumps [k8s.io/cloud-provider](https://github.com/kubernetes/cloud-provider) from 0.26.3 to 0.27.0. - [Release notes](https://github.com/kubernetes/cloud-provider/releases) - [Commits](kubernetes/cloud-provider@v0.26.3...v0.27.0) --- updated-dependencies: - dependency-name: k8s.io/cloud-provider dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
LittleFox94
force-pushed
the
dependabot/go_modules/k8s.io/cloud-provider-0.27.0
branch
from
592ef0a to
f739cde
Compare
|
Code Climate has analyzed commit 9ab61f0 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 55.8% (0.0% change). View more on Code Climate. |
Fix deprecation issues
eiabea
force-pushed
the
dependabot/go_modules/k8s.io/cloud-provider-0.27.0
branch
2 times, most recently
from
9b1efe6 to
839cc18
Compare
|
Please add an entry in CHANGELOG.md for upgraded k8s dependencies and Go version It's a bit sad we can't make dependabot add the changelog entry itself ... maybe we should add something to our CI to sync the draft release (which is automatically created by release-drafter) with the CHANGELOG.md 🤔 |
LittleFox94
added
patch
and removed
minor
|
I also removed the "minor" label and added "patch" instead - we have a bad double-use for those labels :/ |
eiabea
force-pushed
the
dependabot/go_modules/k8s.io/cloud-provider-0.27.0
branch
from
839cc18 to
a29f889
Compare
|
I am quite new to dependabot, but maybe we craft a ticket for this changelog proposal for the next sprint? |
dependabot is completely out of our control, being a github service just enable with very few config options - we would have to craft something fresh for that. But we also have a quite diverse build system landscape ... here we have release-drafter, over at go-anxcloud or our terraform provider we don't. Before we craft something, we should probably try to find which way we wanna have it and use that on all projects, or at least decide on one way, craft a solution for the changelog problem and then, if that works out, use that way on every project. TL;DR: nothing to quickly define to do next sprint |
eiabea
force-pushed
the
dependabot/go_modules/k8s.io/cloud-provider-0.27.0
branch
from
a29f889 to
33b14ef
Compare
Update changelog
eiabea
force-pushed
the
dependabot/go_modules/k8s.io/cloud-provider-0.27.0
branch
from
33b14ef to
9ab61f0
Compare
dependabot
bot
deleted the
dependabot/go_modules/k8s.io/cloud-provider-0.27.0
branch
Bumps k8s.io/cloud-provider from 0.26.3 to 0.27.0.
Commits
9379a11Update dependencies to v0.27.0 tag82a6856Merge remote-tracking branch 'origin/master' into release-1.274e01cb4Export WebhookHandler struct because some CCMs use Run directlyf5f43a4Merge remote-tracking branch 'origin/master' into release-1.279f3bbd5.*: update vendor dir and cleanupfe18149Add CloudDualStackNodeIPs feature gate(s)47e45edUpdate GetNodeAddressesFromNodeIP and ParseNodeIPAnnotation for cloud dual-stackb599f38Update GetNodeAddressesFromNodeIP to take the unparsed annotationf48fbdfSplit up PreferNodeIP into legacy and non-legacy versions0555c1aMove kubelet--node-ipparsing to component-helpersDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)