Skip to content

Bump github.com/container-storage-interface/spec from 1.9.0 to 1.11.0 #368

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 12, 2024

Bumps github.com/container-storage-interface/spec from 1.9.0 to 1.11.0.

Release notes

Sourced from github.com/container-storage-interface/spec's releases.

v1.11.0

What's Changed

Breaking changes/Deprecations

  • None

Additions

Clarifications/Corrections/Fixes

  • None

Dependencies

  • None

Full Changelog: container-storage-interface/spec@v1.10.0...v1.11.0

v1.11.0-rc1

No release notes provided.

v1.10.0

What's Changed

Breaking changes/Deprecations

  • The google.golang.org/protobuf and protoc-gen-go libraries were bumped in this release to v1.33.0 (indirectly bumping github.com/golang/protobuf to v1.5.3) resulting in breaking changes to generated protobuf go message structures. SPs updating their CSI drivers to this version of the CSI spec must modify their code to handle the changes. See #570.

Additions

Clarifications/Corrections/Fixes

  • None

Dependencies

New Contributors

Full Changelog: container-storage-interface/spec@v1.9.0...v1.10.0

v1.10.0-rc1

No release notes provided.

Commits
  • f6b6d53 Move VolumeGroupSnapshot to GA (#573)
  • 2f34062 Merge pull request #567 from saad-ali/bumpv111
  • 47d428b Bump master version to 1.11 for next release
  • 21be3f8 Merge pull request #566 from saad-ali/protoBufTo133
  • 1bc2caf Bump google.golang.org/protobuf from 1.32.0 to 1.33.0
  • adb2b16 Merge pull request #564 from container-storage-interface/dependabot/go_module...
  • 811799a Bump golang.org/x/net from 0.10.0 to 0.23.0
  • 9674d35 Merge pull request #559 from container-storage-interface/dependabot/go_module...
  • 2696773 Added the SnapshotMetadata service. (#551)
  • 1f2bf8a Bump google.golang.org/grpc from 1.57.0 to 1.57.1
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [github.com/container-storage-interface/spec](https://github.com/container-storage-interface/spec) from 1.9.0 to 1.11.0.
- [Release notes](https://github.com/container-storage-interface/spec/releases)
- [Commits](container-storage-interface/spec@v1.9.0...v1.11.0)

---
updated-dependencies:
- dependency-name: github.com/container-storage-interface/spec
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 12, 2024
@kubevirt-bot kubevirt-bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Dec 12, 2024
@kubevirt-bot
Copy link

Hi @dependabot[bot]. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@awels
Copy link
Member

awels commented Feb 26, 2025

/lgtm
/approve
/release-note-none

@kubevirt-bot kubevirt-bot added the release-note-none Denotes a PR that doesn't merit a release note. label Feb 26, 2025
@kubevirt-bot kubevirt-bot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Feb 26, 2025
@kubevirt-bot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 26, 2025
@kubevirt-bot
Copy link

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-hostpath-provisioner-sanity 602039e link true /test pull-hostpath-provisioner-sanity
pull-hpp-unit-test 602039e link false /test pull-hpp-unit-test
pull-hostpath-provisioner-e2e-k8s 602039e link true /test pull-hostpath-provisioner-e2e-k8s
pull-hostpath-provisioner-k8s-e2e-storage 602039e link true /test pull-hostpath-provisioner-k8s-e2e-storage
pull-hostpath-provisioner-e2e-k8s-ceph 602039e link true /test pull-hostpath-provisioner-e2e-k8s-ceph

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 8, 2025
@kubevirt-bot
Copy link

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. dependencies Pull requests that update a dependency file lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note-none Denotes a PR that doesn't merit a release note. size/XXL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants