search

kkHAIKE / contextcheck

Analyzer: check whether a function uses a non-inherited context
Apache License 2.0
43 stars 3 forks source link

Bump golang.org/x/tools from 0.8.0 to 0.11.1 #19

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 1 year ago

Bumps golang.org/x/tools from 0.8.0 to 0.11.1.

Release notes

Sourced from golang.org/x/tools's releases.

gopls/v0.11.0

This is a small release containing new integrations of vulnerability analysis.

Vulnerability analysis for go.mod files can be enabled by configuring the "vulncheck" setting to "Imports". For more information on vulnerability management, see the Vulnerability Management for Go blog post.

Support changes

This release removes support for the "experimentalUseInvalidMetadata" setting, as described in the v0.10.0 release. Other settings slated for deprecation in that release remain temporarily supported, but will be removed in v0.12.0.

New Features

Analyzing dependencies for vulnerabilities

This release offers two different options for detecting vulnerabilities in dependencies. Both are backed by the Go vulnerability database (https://vuln.go.dev) and complement each other.

  • Imports-based scanning, enabled by the "vulncheck": "Imports" setting, reports vulnerabilities by scanning the set of packages imported in the workspace. This is fast, but may report more false positives.
  • Integration of the golang.org/x/vuln/cmd/govulncheck command-line tool performs a more precise analysis based on-call graph reachability, with fewer false positives. Because it is slower to compute, it must be manually triggered by using "Run govulncheck to verify" code actions or the "codelenses.run_govulncheck" code lens on go.mod files.

https://user-images.githubusercontent.com/4999471/206977512-a821107d-9ffb-4456-9b27-6a6a4f900ba6.mp4

Additional checks for the loopclosure analyzer

The loopclosure analyzer, which reports problematic references from a nested function to a variable of an enclosing loop, has been improved to catch more cases. In particular, it now reports when subtests run in parallel with the loop, a mistake that often results in all but the final test case being skipped.

image

Configuration changes

  • The "vulncheck" setting controls vulnerability analysis based on the Go vulnerability database. If set to "Imports", gopls will compute diagnostics related to vulnerabilities in dependencies, and will present them in go.mod files.
  • The "codelenses.run_govulncheck" setting controls the presence of code lenses that run the govulncheck command, which takes longer but produces more accurate vulnerability reporting based on call-graph reachability.

Bug fixes

This version of gopls includes fixes to several bugs, notably:

A full list of all issues fixed can be found in the gopls/v0.11.0 milestone. To report a new problem, please file a new issue at https://go.dev/issues/new.

Thank you to our contributors

@​Arsen6331, @​SN9NV, @​adonovan, @​bcmills, @​dle8, @​findleyr, @​hyangah, @​pjweinbgo, @​suzmue

gopls/v0.10.1

This release contains a fix for golang/go#56505: a new crash during method completion on variables of type *error.

... (truncated)

Commits
  • c16d0be cmd/gonew: add new tool for starting a module by copying one
  • 304e203 internal/edit: copy cmd/internal/edit
  • 82861e0 gopls/internal/lsp/source: reinstate equalOrigin for references check
  • 1561060 gopls/internal/lsp/source: fix incorrect 'origin' logic for named types
  • fe58b07 gopls/internal/lsp/source: fix renaming of type parameters
  • 3a3c169 gopls/internal/lsp/source: refresh embeddirective analyzer docs
  • 03562de refactor/satisfy/find: composite lits may have type parameter type
  • bacac14 gopls/internal/lsp/source: Add SuggestedFix for embeddirective Analyzer
  • 38606b3 gopls/internal/lsp/cache: keep analysis progress reports on one line
  • e8cdaf4 gopls/internal/lsp/cache: fast-path for type-checking active packages
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 7 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.