tools/tools: Update module github.com/golangci/golangci-lint to v1.64.5
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
github.com/golangci/golangci-lint | require | patch |
v1.64.4 -> v1.64.5
|
Warning Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
MR created with the help of gitlab-org/frontend/renovate-gitlab-bot
Release Notes
golangci/golangci-lint (github.com/golangci/golangci-lint)
v1.64.5
- Bug fixes
- Add missing flag
new-from-merge-base-flag
- Add missing flag
- Linters bug fixes
-
asciicheck
: from 0.3.0 to 0.4.0 -
forcetypeassert
: from 0.1.0 to 0.2.0 -
gosec
: from 2.22.0 to 2.22.1
-
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Merge request reports
Activity
Renovate Comment
What are the next steps?
If you have been assigned as a reviewer to this Merge Request, please review this Merge Request with the same scrutiny as any community contribution:
-
Ensure that the dependencies updated meet our standards:
- Security: Dependencies do not contain malicious code
- Performance: Dependencies do not bloat the application code or prolong CI times unnecessarily
- Stability: Pipelines are passing
-
Review the changes introduced by the version upgrade. Consider using https://my.diffend.io to compare the two versions in case the updated dependency is either a Ruby Gem or a Node.js package, for example to compare
pg_query
2.1.0
and2.1.4
. -
Check if
bundle install
works locally, in the context of GDK. -
If tests are passing and you've reviewed the updated dependencies, execute pipelines in the context of the main project
This MR is created from a fork, therefore not all jobs (e.g. Danger) might have been executed. Instead of hitting MWPS right away, you might want to wait until the pipeline you've just triggered finished.
Note: This might not be available in projects, in that case merging right away is an option
-
Assign the current milestone to the MR
-
Merge away!
Troubleshooting
We have assembled some FAQs to help reviewers of these kind of merge requests.
Improve this message – The JSON comment below is for automation purposes.
/cc @PatrickRice
{"labels":["maintenance::dependency","type::maintenance","automation:bot-authored","group::environments","devops::deploy","section::cd","Category:Infrastructure as Code"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["patrickrice","timofurrer"]}
-
added 1 commit
- 4e95ce38 - tools/tools: Update module github.com/golangci/golangci-lint to v1.64.5
mentioned in issue #1341
requested review from @PatrickRice and @timofurrer
assigned to @gitlab-dependency-update-bot
changed milestone to %17.9
- Resolved by Patrick Rice
@timofurrer
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break
master
, a new pipeline will be started shortly.Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.
added pipeline:mr-approved label
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.
Reviewer Maintainer @tigerwnz
(UTC+13)
@timofurrer
(UTC+1)
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by ****Merge request already approved.
Adding automation:bot-no-updates in order to prevent renovate from updating the MR.
If you want the MR to be updated again, please remove the label and check the "rebase checkbox" in the description.
added automation:bot-no-updates label
changed milestone to %17.10
added missed:17.9 label
started a merge train
changed milestone to %17.9
removed missed:17.9 label
mentioned in commit d81be6a1