Skip to content

Bump honnef.co/go/tools from 0.4.7 to 0.8.1 in /tools - #203

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/go_modules/tools/honnef.co/go/tools-0.6.1
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/go_modules/tools/honnef.co/go/tools-0.6.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Mar 10, 2025

Copy link
Copy Markdown
Contributor

Bumps honnef.co/go/tools from 0.4.7 to 0.8.1.

Commits
  • 1285a6a Version 2026.2.1 (v0.8.1)
  • 41fe1c7 website: add 2026.2.1 release notes
  • 5bb0735 SA4023: only flag possibly typed nils
  • 8d63ae3 go/types/typeutil: rename IsPointerLike to MaybePointerLike
  • f01b3d2 go/types/typesutil: return true from IsPointerLike for unconstrained type sets
  • f0c0ad6 Version 2026.2 (v0.8.0)
  • 0a6410f website: update shell.nix
  • 81d37dd website: finalize 2026.2 release notes
  • f4f8a57 analysis/facts/nilness: handle 'recover' builtin
  • c6603d6 go/ir: fix use of GO111MODULE in tests
  • Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Mar 10, 2025
@coderabbitai

coderabbitai Bot commented Mar 10, 2025

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@justinhwang

Copy link
Copy Markdown
Contributor

@dependabot rebase

Bumps [honnef.co/go/tools](https://github.com/dominikh/go-tools) from 0.4.7 to 0.8.1.
- [Release notes](https://github.com/dominikh/go-tools/releases)
- [Commits](dominikh/go-tools@v0.4.7...v0.8.1)

---
updated-dependencies:
- dependency-name: honnef.co/go/tools
  dependency-version: 0.6.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump honnef.co/go/tools from 0.4.7 to 0.6.1 in /tools Bump honnef.co/go/tools from 0.4.7 to 0.8.1 in /tools Sep 17, 2026
@dependabot
dependabot Bot force-pushed the dependabot/go_modules/tools/honnef.co/go/tools-0.6.1 branch from 0d772d7 to 2e7461d Compare September 17, 2026 19:59
justinhwang added a commit that referenced this pull request Sep 19, 2026
The CI matrix (1.17/1.18/1.19) had aged out of upstream support, and the
pinned lint tooling no longer builds on any current toolchain:

    golang.org/x/tools@v0.12.1/internal/tokeninternal.go:78:9:
      invalid array length -delta * delta (constant -256 of type int64)

Move the matrix to 1.25/1.26/1.27, with lint running on 1.27. Raise the
module's minimum Go version only as far as the source actually requires:
Pointer[T] wraps sync/atomic.Pointer[T], which landed in 1.19, so 1.20 is
the floor. Neither dependency constrains this further -- testify v1.12.1
declares go 1.17 and go.yaml.in/yaml/v3 declares go 1.16.

Bump honnef.co/go/tools to v0.8.1 so staticcheck and golint compile
again. staticcheck v0.8.1 declares `go 1.26.0`, so the tools module sits
well ahead of the library; it is build-only and does not affect
consumers. This supersedes #203.

With a 1.20 floor, the pointer build variants are dead code: the
`go1.18 && !go1.19` constraint is unsatisfiable, so delete that file, and
drop the now-vacuous go1.18/go1.19 tags from the remaining files. The
surviving Pointer[T] is the sync/atomic.Pointer[T] implementation that
every supported toolchain already selected.

Note that CI does not build on 1.20-1.24, so the declared floor is a
compatibility promise rather than a tested configuration.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
justinhwang added a commit that referenced this pull request Sep 21, 2026
The CI matrix (1.17/1.18/1.19) had aged out of upstream support, and the
pinned lint tooling no longer builds on any current toolchain:

    golang.org/x/tools@v0.12.1/internal/tokeninternal.go:78:9:
      invalid array length -delta * delta (constant -256 of type int64)

Move the matrix to 1.25/1.26/1.27, with lint running on 1.27. Raise the
module's minimum Go version only as far as the source actually requires:
Pointer[T] wraps sync/atomic.Pointer[T], which landed in 1.19, so 1.20 is
the floor. Neither dependency constrains this further -- testify v1.12.1
declares go 1.17 and go.yaml.in/yaml/v3 declares go 1.16.

Bump honnef.co/go/tools to v0.8.1 so staticcheck and golint compile
again. staticcheck v0.8.1 declares `go 1.26.0`, so the tools module sits
well ahead of the library; it is build-only and does not affect
consumers. This supersedes #203.

With a 1.20 floor, the pointer build variants are dead code: the
`go1.18 && !go1.19` constraint is unsatisfiable, so delete that file. The
surviving Pointer[T] is the sync/atomic.Pointer[T] implementation that
every supported toolchain already selected. With no build tags left, the
go118/go119 split is meaningless, so merge the two survivors into a single
pointer.go.

Note that CI does not build on 1.20-1.24, so the declared floor is a
compatibility promise rather than a tested configuration.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
justinhwang added a commit that referenced this pull request Sep 21, 2026
The CI matrix (1.17/1.18/1.19) had aged out of upstream support, and the
pinned lint tooling no longer builds on any current toolchain:

    golang.org/x/tools@v0.12.1/internal/tokeninternal.go:78:9:
      invalid array length -delta * delta (constant -256 of type int64)

Move the matrix to 1.25/1.26/1.27, with lint running on 1.27. Raise the
module's minimum Go version only as far as the source actually requires:
Pointer[T] wraps sync/atomic.Pointer[T], which landed in 1.19, so 1.20 is
the floor. Neither dependency constrains this further -- testify v1.12.1
declares go 1.17 and go.yaml.in/yaml/v3 declares go 1.16.

Bump honnef.co/go/tools to v0.8.1 so staticcheck and golint compile
again. staticcheck v0.8.1 declares `go 1.26.0`, so the tools module sits
well ahead of the library; it is build-only and does not affect
consumers. This supersedes #203.

With a 1.20 floor, the pointer build variants are dead code: the
`go1.18 && !go1.19` constraint is unsatisfiable, so delete that file, and
drop the now-vacuous go1.18/go1.19 tags from the remaining files. The
surviving Pointer[T] is the sync/atomic.Pointer[T] implementation that
every supported toolchain already selected.

Note that CI does not build on 1.20-1.24, so the declared floor is a
compatibility promise rather than a tested configuration.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update Go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant