Draft
Conversation
Contributor
|
I pushed #18370 for a minor upgrade (to 1.25.7) that can also be applied to 1.37. Please consider accepting and backporting it before upgrading to 1.26. |
telegraf-tiger
bot
added
the
feat
Member
Author
|
Marking this as draft for now due to issues with the |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
golangci-lintto 2.9.0 (required for Go 1.26 compatibility)goversioninfoto 1.5.0 and adds a new flag to work around an issue in the build tool that happened due to changes with 32-bit windows builds in the new Go updateprealloclinter as it resulted in many many more linter warnings and I think it would be best for this to be done in a separate follow-up PRChecklist
Related issues
resolves #18248