-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[1.4] ci: backport #4934 #4917 #4937 #4941
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
[1.4] ci: backport #4934 #4917 #4937 #4941
Conversation
|
Wait, golangci-lint 2.5 should error on naked returns like this: and it's not. My guess, this is because of caching. @lifubang you need to include the other commit from #4917. |
`lima-vm/lima-actions/ssh` is now merged into `lima-vm/lima-actions/setup`. https://github.com/lima-vm/lima-actions/releases/tag/v1.1.0 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp> (cherry picked from commit c0e6f42) Signed-off-by: lifubang <lifubang@acmcoder.com>
Since gofumpt v0.9.0 there's a new formatting rule to "clothe" any naked returns. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit b2f8a74) Signed-off-by: lifubang <lifubang@acmcoder.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 2aea861) Signed-off-by: lifubang <lifubang@acmcoder.com>
All the new code appears in main (not in the release branches), and we only want extra linter rules to apply to new code. Disable lint-extra job if the PR is not to the main branch. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 1c4dba6) Signed-off-by: lifubang <lifubang@acmcoder.com>
a5b9b97 to
ae19971
Compare
|
The CI failure seems like a bug in criu-dev: I saw a similar failure in runc-private (also on release-1.4, strangely enough). |
Caching is such a deep and mysterious art—so advanced that I couldn’t grasp it. Anyway, I just nuked the cache, and magically, the CI turned green! 🥲 |
To backport some PRs in CI area:
#4934
#4917
#4937