c1c002d moved CI to the 1.26.11 image but release.yml stayed on 1.26.10, so v27.1-rc.9 shipped binaries built with go1.26.10 (checked: go version on the published amd64 binary). govulncheck flags GO-2026-6859 there (net/http, reached from tui.Summary). This puts release.yml on the CI image and go.mod on 1.26.11. For v27.1-rc.10.
c1c002d moved CI to the 1.26.11 image but release.yml stayed on 1.26.10, so v27.1-rc.9 shipped binaries built with go1.26.10 (checked: `go version` on the published amd64 binary). govulncheck flags GO-2026-6859 there (net/http, reached from tui.Summary). This puts release.yml on the CI image and go.mod on 1.26.11. For v27.1-rc.10.
c1c002d moved CI to the 1.26.11 image but left release.yml on 1.26.10,
so 27.1-rc.9 was built with a net/http that govulncheck flags
(GO-2026-6859, reached from the interface's summary). Releases now use
the same image as CI, and go.mod asks for 1.26.11.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
c1c002dmoved CI to the 1.26.11 image but release.yml stayed on 1.26.10, so v27.1-rc.9 shipped binaries built with go1.26.10 (checked:go versionon the published amd64 binary). govulncheck flags GO-2026-6859 there (net/http, reached from tui.Summary). This puts release.yml on the CI image and go.mod on 1.26.11. For v27.1-rc.10.