build(deps): bump github.com/kserve/kserve from 0.13.1 to 0.14.0 in /csi #493
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
This seems to me would make a requirement, at least for CSI, to bump to Go 1.22. Is this worthy, or should we consider sticking to kserve api 0.13 for now, wdyt @Al-Pragliola @lampajr ? |
dependabot
bot
force-pushed
the
dependabot/go_modules/csi/github.com/kserve/kserve-0.14.0
branch
from
ed43804
to
ce13868
Compare
Bumps [github.com/kserve/kserve](https://github.com/kserve/kserve) from 0.13.1 to 0.14.0. - [Release notes](https://github.com/kserve/kserve/releases) - [Commits](kserve/kserve@v0.13.1...v0.14.0) --- updated-dependencies: - dependency-name: github.com/kserve/kserve dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/go_modules/csi/github.com/kserve/kserve-0.14.0
branch
from
ce13868
to
24cfb98
Compare
There was a problem hiding this comment.
This seems to me would make a requirement, at least for CSI, to bump to Go 1.22.
+1 if we upgrade to kserve 0.14 we MUST update go to 1.22
Is this worthy, or should we consider sticking to kserve api 0.13 for now, wdyt @Al-Pragliola @lampajr ?
Technically the CSI is using kserve just for the model download, i.e., this package https://github.com/kserve/kserve/tree/37be2411b462687026686abac8d7bdb7c79c9cd2/pkg/agent/storage and there is just one diff between 0.13.1 and 0.14.0 (just one import change in the util.go) - therefore I don't think we have to upgrade kserve at the moment as there is no valid reason to do that (especially if we need to upgrade go).
thanks for the confirmation 👍 /hold |
Bumps github.com/kserve/kserve from 0.13.1 to 0.14.0.
Release notes
Sourced from github.com/kserve/kserve's releases.
... (truncated)
Commits
7e43642KServe 0.14 Release (#3988)82234c0Pin ubuntu 22.04 for minikube setup action (#3994)dbceef3Torchserve security update (#3774)fc72a2bFix: Headers passing for v1/v2 endpoints (#3669)7796c44Modelcar race condition mitigation with an init container (#3932)d2695a5Do not set security context on the storage initializer from user container (#...6ff2a2fAdd a flag for automount serviceaccount token (#3979)dec8c14Fix streaming response not working properly with logger (#3847)70e12ffFix kserve local testing env (#3981)d7d79e1Fix Kubernetes Doc Links (#3670)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 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)