Repository navigation
build(deps): Bump Go to 1.26.10 - #558
Open
sentry-junior[bot] wants to merge 1 commit into
Open
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: Geoff Goldsmith <geoff.goldsmith@sentry.io>
commit: |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of VULN-3216: the eMudhra CA was compromised, and Go 1.26.10 fixes the related root handling in
crypto/x509..github/workflows/release.yml(mcp_registryjob):actions/setup-go@v5go-version: '1.22'->'1.26.10'The
mcp_registryjob is the only place Go runs. It buildsmcp-publisherfrom the upstreammodelcontextprotocol/registrydefault branch, then uses it over HTTPS to publish. Upstream's go.mod requiresgo 1.26.0, so with Go 1.22 the last release run (2026-09-23) switched automatically and downloadedgo1.26.0. That version predates the fix. Pinning1.26.10builds the publisher with a patched toolchain. The exact pin is needed becausesetup-goprefers a version already cached on the runner, and current runner images were built before 1.26.10 came out.The shipped npm package and macOS portable artifacts are not built with Go and are unaffected.
mcp-publisheris rebuilt on every release run, so nothing else needs to be redeployed.Verified locally: on a clone of the current upstream registry,
make publisherwith Go 1.26.10 andGOTOOLCHAIN=localsucceeds.go version -mreportsgo1.26.10. I did not run the release workflow. I did not add a CHANGELOG entry because this is a CI-only change.via Geoff Goldsmith.
--
View Junior Session [Sentry]