Skip to content

build(deps): raise the Go floor to 1.27.2, closing the GO-2026-6617 residual - #317

Merged
JonasBorgesLM merged 1 commit into
developfrom
fix/go-1.27.2-316
Oct 13, 2026
Merged

JonasBorgesLM merged 1 commit into
developfrom
fix/go-1.27.2-316

Conversation

@JonasBorgesLM

Copy link
Copy Markdown
Owner

Closes #316. The trigger arrived: staticcheck 2026.2.2 (v0.8.2, 2026-10-12) "now supports the updated export data format used by Go 1.27.2".

Changes

  • go.mod, Dockerfile, web/Dockerfile and the README mention move from 1.26.9 to 1.27.2.
  • STATICCHECK_VERSION moves from v0.8.1 to v0.8.2.
  • GOSEC_VERSION moves from v2.28.0 to the master commit d2b649e. No release reads Go 1.27 export data, and that includes v2.29.0. It is the same pin as usher and sapper, and goes back to a tag via usher#146 and sapper#56.
  • #nosec G703 on os.Stat(fsPath) in spaHandler. This is the false positive DECISIONS.md predicted, and the comment carries the justification.
  • A new DECISIONS.md entry closes the residual.

Checklist from #316

  • go.mod, both Dockerfiles at 1.27.2, and STATICCHECK_VERSION/GOSEC_VERSION updated
  • G703 annotated. Without the annotation, make gosec fails on exactly that line (exit 2), and with it, exit 0.
  • Every gate checked by exit code, with GOTOOLCHAIN=go1.27.2: go build, go vet (with and without -tags=integration), make lint (both variants), make gosec, make vulncheck, make tidy-check, go test -race ./.... All exit 0.
  • DECISIONS.md entry

Also checked: the API image builds from golang:1.27.2-alpine.

Not checked locally: integration tests (-tags=integration) and the web image. CI runs both.

🤖 Generated with Claude Code

…esidual

1.26.9 was accepted with a residual: a local build on Go 1.27.0 or 1.27.1
satisfies it and ships the vulnerable net/http. 1.27.2 excludes both
vulnerable lines, but no staticcheck could read Go 1.27 export data.
staticcheck 2026.2.2 (v0.8.2) now can, which was the trigger #316 named.

gosec has no release that reads it (v2.29.0 included), so it is pinned to
master commit d2b649e, as usher and sapper are. The new gosec flags the
G703 in spaHandler that DECISIONS.md predicted; it is a false positive
for the reason recorded there, and is annotated next to the call.

Every gate was checked by exit code under go1.27.2: build, vet (both tag
sets), make lint, make gosec, make vulncheck, make tidy-check, and
go test -race.

Closes #316

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JonasBorgesLM
JonasBorgesLM merged commit 008433c into develop Oct 13, 2026
6 checks passed
@JonasBorgesLM
JonasBorgesLM deleted the fix/go-1.27.2-316 branch October 13, 2026 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant