build: use patched Go toolchain and UI dependency#2927
Merged
Conversation
Ensure setup-go and GoReleaser use the patched Go toolchain for release binaries. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 0b2aa497-b47d-464a-b132-af0dcaf2b621
Resolve the high-severity host-confusion advisories reported by npm audit. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 0b2aa497-b47d-464a-b132-af0dcaf2b621
loganrosen
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares v1.6.1 security fixes by aligning release builds with patched Go 1.25.12 and updating the vulnerable UI dependency.
Changes:
- Sets the Go minimum/toolchain input to 1.25.12.
- Updates
fast-urifrom 3.1.2 to 3.1.4.
Show a summary per file
| File | Description |
|---|---|
go.mod |
Pins release workflows to patched Go 1.25.12. |
ui/package-lock.json |
Updates the transitive fast-uri dependency. |
Review details
Files not reviewed (1)
- ui/package-lock.json: Generated file
- Files reviewed: 1/2 changed files
- Comments generated: 0
- Review effort level: Medium
RossTarrant
approved these changes
Jul 22, 2026
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
Ensures release binaries are built with Go 1.25.12 and removes the remaining high-severity UI dependency finding.
Why
Main's Docker builder was updated by #2867, but GoReleaser reads the exact Go version from
go.mod, which remained at 1.25.0. That could leave future release archives built with an older, vulnerable Go standard library even though the container image was patched. The broader Go 1.26 upgrade in #2705 can proceed separately from this focused correction.No linked issue. Related: #2705.
What changed
go.modminimum from Go 1.25.0 to 1.25.12 so setup-go and GoReleaser use the patched toolchain.fast-urifrom 3.1.2 to 3.1.4 to resolve its high-severity host-confusion advisories.MCP impact
This only changes build inputs; MCP tools and behavior are unchanged.
Prompts tested (tool changes only)
Security / limits
This is a build and dependency security update. It does not change runtime authentication, data exposure, filtering, or limits.
Tool renaming
deprecated_tool_aliases.goNote: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.
Lint & tests
./script/lint./script/testAlso verified
govulncheck, license generation, UI typecheck/audit/build, GoReleaser snapshot artifacts, and amd64/arm64 container builds.Docs