ci: set up Go in release platform smoke#144
Merged
Merged
Conversation
tonyredondo
force-pushed
the
feat/fix-release-go-setup
branch
from
May 18, 2026 14:27
5330872 to
f9b8dfb
Compare
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.
Summary
Adds the same Go toolchain setup used by CI to the release platform smoke job.
The pre-tag release gate failed on macOS before running the mock-server harness because
gowas not available on the runner. The harness requires a host Go binary for the bootstrap integration path.Validation
Release workflow validation will be rerun on this branch before tagging
v1.0.0.Release Readiness
LICENSE-3rdparty.csvwhen dependencies or vendored code changed. Not applicable.