---
- branch: MAIN
  date: Sun Apr 21 15:31:33 UTC 2024
  files:
  - new: '1.89'
    old: '1.88'
    path: pkgsrc/devel/gopls/Makefile
    pathrev: pkgsrc/devel/gopls/Makefile@1.89
    type: modified
  - new: '1.44'
    old: '1.43'
    path: pkgsrc/devel/gopls/distinfo
    pathrev: pkgsrc/devel/gopls/distinfo@1.44
    type: modified
  - new: '1.39'
    old: '1.38'
    path: pkgsrc/devel/gopls/go-modules.mk
    pathrev: pkgsrc/devel/gopls/go-modules.mk@1.39
    type: modified
  id: 20240421T153133Z.1e3b014820ef51f12d4bea918be495c59478bc33
  log: |
    gopls: update to 0.15.3.

    This release fixes the following regressions in gopls@v0.15.0+:

        golang/go#66490: occasional crashes when the imports cache is refreshed.
        golang/go#66425: spurious import errors in multi-root workspaces that have go.work replace directives.
        golang/go#66636: a crash in analysis when the go.mod contains a patch version and gopls was built with Go 1.20 or earlier.
        golang/go#66677: silent breakage when the go.mod file contains Go 1.22.x, and gopls was built with Go 1.21.x.
        golang/go#66731: a rare crash when diagnostics are erroneously positioned outside the file due to malformed syntax.
        golang/go#66647: a performance regression due to unnecessary reloading following "workspace/didChangeConfiguration" notifications. Under some not-yet-understood conditions, an apparent VS Code bug causes didChangeConfiguration notifications on every keystroke. With the zero-config logic of gopls@v0.15.0+, any didChangeConfiguration notification causes gopls to re-evaluate (and reload) the set of builds it tracks. With the v0.15.3 release, gopls verifies that configuration actually changed. Special thanks to @gordallott for working with us to track down this bug.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/gopls'
  unixtime: '1713713493'
  user: wiz