-
Notifications
You must be signed in to change notification settings - Fork 28
chore: bump deps #276
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
Merged
+34
−34
Merged
chore: bump deps #276
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
golangci-lint v2.8.0 release notes breaking changes💡 Result:
golangci-lintv2.8.0 (released January 7, 2026) does not list any explicit “breaking changes” in its official release notes/changelog—no CLI/config removals or incompatible defaults are called out for this version. (golangci-lint.run)The changes most likely to impact CI results (i.e., “practically breaking” due to new/changed findings) are linter updates: (golangci-lint.run)
godoc-lint: new rulerequire-stdlib-doclink(golangci-lint.run)gosec: new ruleG116(golangci-lint.run)modernize: new analyzersstringscut,unsafefuncs(golangci-lint.run)unqueryvet: adds multiple new options (e.g.,check-subqueries,sql-builders, etc.) (golangci-lint.run)prealloc: “message changes” (can affect baselines/golden files) (golangci-lint.run)Citations:
🌐 Web query:
golangci-lint v2.8.0 Go 1.25 support compatibility💡 Result:
golangci-lint v2.8.0is compatible with Go 1.25, as long as thegolangci-lintbinary you run was built with Go 1.25 (or newer).golangci-lintgenerally supports analyzing Go code for versions ≤ the Go version used to compilegolangci-lint. [2][3]golangci-lintmaintainers note that official binaries are built with Go 1.25 (so the official release artifacts should work with Go 1.25 projects). [3][4]v2.8.0itself was released 2026-01-07. [1]golangci-lintwith an older Go toolchain, the resulting binary may not properly support Go 1.25; in that case use the official binaries or build it yourself with Go 1.25. [3]Sources:
golangci-lintv2.8.0 changelog [1], support policy FAQ [2], Go 1.25 support discussion (golangci-lint) [3], Go 1.25 release announcement [4].🌐 Web query:
golangci-lint-action v9 golangci-lint version 2.8.0 compatibility💡 Result:
Yes—
golangci/golangci-lint-action@v9is compatible withgolangci-lint v2.8.0.golangci-lint v2.8.0was released 2026-01-07. [3]If you’re pinning it, use:
Sources: [1] [2] [3]
Review v2.8.0 for new linter checks that could fail in CI.
While v2.8.0 introduces no config-breaking changes and fully supports Go 1.25, it adds new linter rules (godoc-lint's
require-stdlib-doclink, gosec'sG116, modernize'sstringscut/unsafefuncs, and unqueryvet options) and changes prealloc's output messages. Run a test pass with this version to ensure these new checks don't cause unexpected lint failures.🤖 Prompt for AI Agents