build: restore staticcheck in the gate when it supports Go 1.27.2 #741

New issue

Open

opened 2026-10-09 16:52:45 +00:00 by hexajon · 0 comments

hexajon commented

2026-10-09 16:52:45 +00:00

Owner

Context

I bumped the gate to Go 1.27.2. It is a security patch: govulncheck flagged 9 standard-library CVEs, fixed only in 1.27.2.

Go 1.27.2 broke staticcheck. The current release (v0.8.1) and the master build both fail to decode 1.27.2 export data. Every run reports "export data version 5 is greater than maximum supported version 4". No staticcheck release supports 1.27.2 yet.

What the gate does now

scripts/gate.sh still runs staticcheck. When staticcheck fails ONLY with that export-data error, the gate prints a skip line and does not fail. Any real staticcheck finding still fails the gate. This is a loud, tracked skip, not a silent pass.

The skip is self-clearing. When a staticcheck release decodes 1.27.2, the error stops, and staticcheck runs as a normal gate step again, with no change to gate.sh.

What to do to close this

Confirm a staticcheck release decodes Go 1.27.2 (no export-data error on staticcheck ./...).
Bump the staticcheck pin in scripts/setup-dev.sh and .forgejo/workflows/ci.yml to that release.
Confirm the gate shows staticcheck as a normal pass, not a skip.

## Context I bumped the gate to Go 1.27.2. It is a security patch: govulncheck flagged 9 standard-library CVEs, fixed only in 1.27.2. Go 1.27.2 broke staticcheck. The current release (v0.8.1) and the master build both fail to decode 1.27.2 export data. Every run reports "export data version 5 is greater than maximum supported version 4". No staticcheck release supports 1.27.2 yet. ## What the gate does now `scripts/gate.sh` still runs staticcheck. When staticcheck fails ONLY with that export-data error, the gate prints a skip line and does not fail. Any real staticcheck finding still fails the gate. This is a loud, tracked skip, not a silent pass. The skip is self-clearing. When a staticcheck release decodes 1.27.2, the error stops, and staticcheck runs as a normal gate step again, with no change to `gate.sh`. ## What to do to close this 1. Confirm a staticcheck release decodes Go 1.27.2 (no export-data error on `staticcheck ./...`). 2. Bump the staticcheck pin in `scripts/setup-dev.sh` and `.forgejo/workflows/ci.yml` to that release. 3. Confirm the gate shows staticcheck as a normal pass, not a skip.

hexajon referenced this issue

2026-10-09 17:11:50 +00:00

chore: adopt Go 1.27.2 and keep the gate green #742

hexajon referenced this issue

2026-10-14 20:10:56 +00:00

epic: the gate scopes to the change, runs heavy tests as their own stage, and reads as a list of guarantees #767

hexajon referenced this issue

2026-10-14 20:14:10 +00:00

gate: run the formatter and Go linters behind golangci-lint #768