etcd-io
build(deps): Bump golangci/golangci-lint-action from 6.5.1 to 7.0.0
Bumps golangci/golangci-lint-action from 6.5.1 to 7.0.0.
Release notes
Sourced from golangci/golangci-lint-action's releases.
v7.0.0
⚠️ The GitHub Action v7 supports golangci-lint v2 only. ⚠️
What's Changed
Changes
- feat: golangci-lint v2 support by
@ldezin golangci/golangci-lint-action#1198Documentation
- docs: update annotation permissions by
@ldezin golangci/golangci-lint-action#1203- docs: fix checks permissions for annotations by
@kema-devin golangci/golangci-lint-action#1204Dependencies
- build(deps-dev): bump the dev-dependencies group with 3 updates by
@dependabotin golangci/golangci-lint-action#1207New Contributors
@kema-devmade their first contribution in golangci/golangci-lint-action#1204Full Changelog: https://github.com/golangci/golangci-lint-action/compare/v6.5.2...v7.0.0
v6.5.2
What's Changed
Changes
- fix: update max version by
@ldezin golangci/golangci-lint-action#1201Dependencies
- build(deps-dev): bump the dev-dependencies group with 2 updates by
@dependabotin golangci/golangci-lint-action#1199Full Changelog: https://github.com/golangci/golangci-lint-action/compare/v6.5.1...v6.5.2
Commits
14814047.0.0dec74fafeat: golangci-lint v2 support (#1198)1f07148build(deps-dev): bump the dev-dependencies group with 3 updates (#1207)9938e10docs: fix checks permissions for annotations (#1204)b91d580docs: update annotation permissions (#1203)55c2c146.5.2911ec56fix: update max version (#1201)eb5c0ccbuild(deps-dev): bump the dev-dependencies group with 2 updates (#1199)- See full diff 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 ptabor for approval. For more information see the 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 etcd-io 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.
