| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
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
There was a problem hiding this comment.
Prepares v1.6.1 security fixes by aligning release builds with patched Go 1.25.12 and updating the vulnerable UI dependency.
Changes:
| File | Description |
|---|---|
| go.mod | Pins release workflows to patched Go 1.25.12. |
| ui/package-lock.json | Updates the transitive fast-uri dependency. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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
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
Note: 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
Also verified govulncheck, license generation, UI typecheck/audit/build, GoReleaser snapshot artifacts, and amd64/arm64 container builds.
Docs