Skip to content
This repository was archived by the owner on Oct 23, 2026. It is now read-only.

build(deps): Bump Go to 1.26.10 - #3

Open
sentry-junior[bot] wants to merge 1 commit into
mainfrom
vuln-3216/go-1.26.10
Open

sentry-junior[bot] wants to merge 1 commit into
mainfrom
vuln-3216/go-1.26.10

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Oct 20, 2026

Copy link
Copy Markdown

Security fix for VULN-3216: the eMudhra CA was compromised and Go fixed its crypto/x509 root handling in Go 1.26.10. Go compiles the standard library into binaries, so the build toolchain has to move.

Go 1.17 -> 1.26.10:

  • Dockerfile (builder stage): golang:1.17-alpine3.14 -> golang:1.26-alpine3.24 (floating minor, currently resolves to 1.26.10)

The builder OS changes too: there are no Go 1.26 images on alpine3.14, so the builder moves to alpine3.24 (the same image as golang:1.26-alpine). The runtime stage stays on alpine:3.14. The emulator is built by a cgo-free alpine golang image, so the binary should be static. The pinned google-cloud-go commit (23c02d92) is unchanged.

The fix only reaches the published ghcr.io/getsentry/cbtemulator image once it's rebuilt and pushed.

Verified locally with Go 1.26.10 (GOTOOLCHAIN=local, CGO_ENABLED=0) on the pinned google-cloud-go tarball: go install -v ./cmd/emulator in bigtable/ passes, go vet ./cmd/emulator passes, and the binary reports go1.26.10, starts, and listens on its port. I didn't build the Docker image (no Docker available), so I haven't checked busybox wget or the multi-arch build on the new base. CI's docker/build-push-action will cover that.

Note: this repo is a fork that has been inactive since late 2024.

via Geoff Goldsmith.

--

View Junior Session [Sentry]

Co-Authored-By: Geoff Goldsmith <[email protected]>
@linear-code

linear-code Bot commented Oct 20, 2026

Copy link
Copy Markdown

VULN-3216

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant