Log message:
gopls: update to 0.14.0

This release includes initial support for the "inline call to function"
refactoring, as well as a few other smaller features. It also includes several
bug fixes, notably a fix for a performance regression in completion that may be
significant in some environments.

The release also contains support for opt-in telemetry. If you want, you can
enable the periodic uploading of telemetry data, including gopls stack traces
and metrics, but never your source code, to telemetry.go.dev. See below for
details.

New features
------------

- Refactoring: inline call to function
- Refactoring: removing unused parameters
- Improved support for go:embed directives, including hover and
  jump-to-definition

New analyses
------------

This release include three new static analyses, all of which are enabled by
default.

"appends": reports calls to append that pass no values to be appended \ 
to the
slice.

"defers": checks for common mistakes in defer statements.

"slog": checks for invalid structured logging calls.

Opt-in telemetry
----------------

This is the first gopls release to include opt-in transparent telemetry.
Telemetry uploading is off by default, and can be enabled with the following
command:

go run golang.org/x/telemetry/cmd/gotelemetry@latest on

After telemetry is enabled, gopls will periodically upload metrics and stack
traces to telemetry.go.dev. If we get enough adoption, this data can
significantly advance the pace of gopls development and help us meet a higher
standard of reliability. For example:

- Even with semi-automated crash reports in VS Code, we've seen several
  crashers go unreported for weeks or months.
- Even with a suite of benchmarks, some performance regressions don't show up
  in our benchmark environment (such as the completion bug mentioned below!).
- Even with lots of great ideas for how to improve gopls, we have limited
  resources. Telemetry can help us identify which new features are most
  important, and which existing features aren't being used or aren't working
  well.

These are just a few ways that telemetry can improve gopls. The telemetry blog
post series contains many more.

Go telemetry is designed to be transparent and privacy-preserving. If you have
concerns about enabling telemetry, you can learn more at
https://telemetry.go.dev/privacy.

Log message:
Revbump all Go packages because go121 is now the default

Log message:
Revbump all Go packages after go120 security update

Log message:
Revbump all Go packages after go120 update

Log message:
Revbump all Go packages after go120 update

Log message:
gopls: update to 0.13.2

0.13.2
fix for a new crash when renaming methods in certain packages

0.13.1
fix three issues with the v0.13.0 release:

- broken imports due to corrupted export data
- panic in stubmethods with variadic args
- gofumpt integration panics when used with the new go directive syntax in go.mod
  files (e.g. go 1.21rc3)

0.13.0
This release fixes several bugs and mitigates a few performance regressions. It
also somewhat reduces the latency and CPU cost of most operations, and includes
a few small additional features.

Log message:
Revbump all Go packages after go120 update

Log message:
gopls: update to 0.12.4.

0.12.4

This is a follow up to gopls@v0.12.3 fixing a crash in the new
analysis driver, in the presence of certain invalid packages
(golang/go#60952).

0.12.3

This release fixes a couple rare but significant performance
regressions introduced in the v0.12.0 release.

Log message:
gopls: update to 0.12.2

0.12.2

This is an alias for the gopls/v0.12.1 release.

0.12.1

This release fixes a few regressions/crashes in the v0.12.0 release:

*   Unimported completion should use fuzzy matching
*   Fix a crash when method has receiver type comparable
*   Fix for documentHighlight on import paths
*   Clear vulncheck diagnostics when they are toggled off

0.12.0

This release contains a major rewrite of the way gopls computes and stores
package information, with the goal of reducing memory usage and allowing gopls
to scale to larger repositories. This change can also significantly reduce
startup time when workspaces are reopened, as gopls now uses a file-based cache
to persist data across sessions. With these optimizations, gopls is finally
able to fully analyze dependencies using the golang.org/x/tools/go/analysis
framework, resulting in improved accuracy for analysis diagnostics.

Log message:
Revbump all Go packages after go120 security update