Skip to content

fix: rebuild verification service with Go 1.26.10 - #6

Merged
freehere107 merged 1 commit into
mainfrom
codex/go-1-26-10-security
Oct 22, 2026
Merged

freehere107 merged 1 commit into
mainfrom
codex/go-1-26-10-security

Conversation

@freehere107

Copy link
Copy Markdown
Contributor

Rebuild the verifier with Go 1.26.10 to include the crypto/x509 certificate verification fix in GO-2026-6809. Pin the patch in go.mod, use the official setup-go action to select it in CI, and align Dockerfile.local and development guidance. This service has no third-party Go module dependencies, so no x/net requirement is added.

The production Dockerfile packages the verification binary produced by CI's make build; changing its Alpine runtime alone would not update Go. Document this build boundary and the amd64 solc requirement, and add a regression confirming that outbound HTTPS rejects an untrusted certificate. PR builds now skip registry login, image publication, and failure notifications while retaining test and image-build validation.

Validation:

  • Go 1.26.10 on macOS/arm64: go mod tidy, go build ./..., go vet ./....
  • go test -race -count=1 -v -skip '^(Test_compile|Test_MultifileCompile|Test_verificationHandler)$' ./... passes on macOS/arm64. These three tests execute downloaded amd64 solc binaries; this machine has no Rosetta support.
  • The complete go test -mod=mod -v ./... passes in Linux/amd64 with Go 1.26.10, Alpine, and gcompat, including actual solc compilation, the verification handler, and metadata/immutable/library/constructor compatibility regressions.
  • make build passes in the same Linux/amd64 environment. go version -m verification confirms Go 1.26.10, linux/amd64, and CGO_ENABLED=0.
  • git diff --check passes.

The change prepares the production binary rebuild; it does not deploy the service.

@freehere107
freehere107 merged commit d870988 into main Oct 22, 2026
1 check passed
@freehere107
freehere107 deleted the codex/go-1-26-10-security branch October 22, 2026 07:35
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