CI started failing on every branch: govulncheck reports GO-2026-6809 (crypto/x509, distrust compromised intermediate certificates), reachable from backup.VerifyDataDirBackup, found in go1.26.9 and fixed in go1.26.10.
go.mod: go 1.26.10 (the GitHub runners read it via go-version-file).
.gitea/workflows/ci.yml: the fallback golang:1.26-bookworm image re-pinned to the digest that ships 1.26.10.
Checked in that image: go vet, go test ./... all pass, govulncheck: no vulnerabilities found.
CI started failing on every branch: govulncheck reports [GO-2026-6809](https://pkg.go.dev/vuln/GO-2026-6809) (crypto/x509, distrust compromised intermediate certificates), reachable from `backup.VerifyDataDirBackup`, found in go1.26.9 and fixed in go1.26.10.
- `go.mod`: `go 1.26.10` (the GitHub runners read it via `go-version-file`).
- `.gitea/workflows/ci.yml`: the fallback `golang:1.26-bookworm` image re-pinned to the digest that ships 1.26.10.
Checked in that image: `go vet`, `go test ./...` all pass, govulncheck: no vulnerabilities found.
govulncheck reports GO-2026-6809 (crypto/x509 distrusting compromised
intermediates) reachable from backup verification on Go 1.26.9; 1.26.10 fixes
it. go.mod drives the GitHub runners; the Gitea fallback image is re-pinned to
the 1.26-bookworm digest that ships 1.26.10.
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.
CI started failing on every branch: govulncheck reports GO-2026-6809 (crypto/x509, distrust compromised intermediate certificates), reachable from
backup.VerifyDataDirBackup, found in go1.26.9 and fixed in go1.26.10.go.mod:go 1.26.10(the GitHub runners read it viago-version-file)..gitea/workflows/ci.yml: the fallbackgolang:1.26-bookwormimage re-pinned to the digest that ships 1.26.10.Checked in that image:
go vet,go test ./...all pass, govulncheck: no vulnerabilities found.