-
Notifications
You must be signed in to change notification settings - Fork 386
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
Release external-snapshotter 8.2.1 #1278
Merged
k8s-ci-robot
merged 7 commits into
kubernetes-csi:release-8.2
from
AndrewSirenko:cherry-picks-8.2.1
Feb 27, 2025
Merged
Release external-snapshotter 8.2.1 #1278
k8s-ci-robot
merged 7 commits into
kubernetes-csi:release-8.2
from
AndrewSirenko:cherry-picks-8.2.1
Feb 27, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
90efb2ca5 Merge pull request kubernetes-csi#272 from andyzhangx/patch-3 9b616fec4 Bump golang to 1.23.6 to fix CVE-2024-45336, CVE-2025-22866 049659326 Merge pull request kubernetes-csi#268 from huww98/cloudbuild 119aee1ff Merge pull request kubernetes-csi#266 from jsafrane/bump-sanity-5.3.1 0ae5e52d9 Update cloudbuild image with go 1.21+ 406a79acf Merge pull request kubernetes-csi#267 from huww98/gomodcache 9cec273d8 Set GOMODCACHE to avoid re-download toolchain 98f23071d Merge pull request kubernetes-csi#260 from TerryHowe/update-csi-driver-version e9d8712d0 Merge pull request kubernetes-csi#259 from stmcginnis/deprecated-kind-kube-root faf79ff66 Remove --kube-root deprecated kind argument 734c2b950 Merge pull request kubernetes-csi#265 from Rakshith-R/consider-main-branch 43bde065f Bump csi-sanity to 5.3.1 f95c855be Merge pull request kubernetes-csi#262 from huww98/golang-toolchain 3c8d966fe Treat main branch as equivalent to master branch 6b05f0fcc use new GOTOOLCHAIN env to manage go version 18b6ac6d2 chore: update CSI driver version to 1.15 git-subtree-dir: release-tools git-subtree-split: 90efb2ca59900f19eba05e65da28beda79c5bb28
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AndrewSirenko, xing-yang 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 |
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.
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
release-note-none
Denotes a PR that doesn't merit a release note.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Cherry-picks #1275, #1251, and pulls latest release-tools into release-8.2 branch
Passed k8s tests when deployed alongside EBS CSI Driver
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release tools update:
Does this PR introduce a user-facing change?: