csi-proxy
csi-proxy copied to clipboard
kubernetes-csi
Bump k8s.io/klog/v2 from 2.100.1 to 2.130.1
Bumps k8s.io/klog/v2 from 2.100.1 to 2.130.1.
Release notes
Sourced from k8s.io/klog/v2's releases.
Prepare klog release for Kubernetes v1.31 (Take 2)
What's Changed
- data race: avoid unprotected access to sb.file by
@pohlyin kubernetes/klog#408Full Changelog: https://github.com/kubernetes/klog/compare/v2.130.0...v2.130.1
Prepare klog release for Kubernetes v1.31 (Take 1)
What's Changed
- chore(*): fix spelling of Intel Corporation by
@jsorefin kubernetes/klog#399- build: fix some linter warnings by
@pohlyin kubernetes/klog#402- examples: fix linter warning by
@pohlyin kubernetes/klog#406- Do not acquire lock for file.Sync() fsync call by
@1978629634in kubernetes/klog#404- ktesting: tone down warning about leaked test goroutine by
@pohlyin kubernetes/klog#401New Contributors
@jsorefmade their first contribution in kubernetes/klog#399@1978629634made their first contribution in kubernetes/klog#404Full Changelog: https://github.com/kubernetes/klog/compare/v2.120.1...v2.130.0
Prepare klog release for Kubernetes v1.30 (Take 2)
What's Changed
- textlogger: allow caller to override stack unwinding by
@pohlyin kubernetes/klog#397Full Changelog: https://github.com/kubernetes/klog/compare/v2.120.0...v2.120.1
Prepare klog release for Kubernetes v1.30 (Take 1)
What's Changed
- OWNERS: remove serathius, add mengjiao-liu, promote pohly by
@pohlyin kubernetes/klog#394- docs: clarify relationship between different features by
@pohlyin kubernetes/klog#395- Add SafePtr wrapper by
@kaisozin kubernetes/klog#393- logr v1.4.1 + SetSlogLogger by
@pohlyin kubernetes/klog#396New Contributors
@kaisozmade their first contribution in kubernetes/klog#393Full Changelog: https://github.com/kubernetes/klog/compare/v2.110.1...v2.120.0
Prepare klog release for Kubernetes v1.29 (Take 1)
What's Changed
- fix: SetLogger via klog.SetLogger will output an unexpected newline by
@aimuzin kubernetes/klog#378- resolve comments warning by
@lowang-bhin kubernetes/klog#379- stderrthreshold: fix flag comment by
@pohlyin kubernetes/klog#376- enable "go vet" checks for parameters by
@pohlyin kubernetes/klog#390- promote experimental code to stable by
@pohlyin kubernetes/klog#392- golangci-lint action by
@pohlyin kubernetes/klog#380- output: handle WithName like zapr does by
@pohlyin kubernetes/klog#391- slog support + logr 1.3.0 update by
@pohlyin kubernetes/klog#384
... (truncated)
Commits
75663bbMerge pull request #408 from pohly/klog-flush-sync-fix2327d4cdata race: avoid unprotected access to sb.file16c7d26Merge pull request #401 from pohly/ktesting-warning-delaycd24012ktesting: tone down warning about leaked test goroutine2ee202aMerge pull request #404 from 1978629634/fsync-freelock79575d8Do not acquire lock for file.Sync() fsync call7af45d6Merge pull request #406 from pohly/linterd008cfeexamples: fix linter warningab53041Merge pull request #402 from pohly/linter-issuesff7c070build: fix some linter warnings- Additional commits viewable in compare view
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)
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign xing-yang for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Hi @dependabot[bot]. Thanks for your PR.
I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
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.
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
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.