Skip to content

fix: build with security-patched Go 1.27.3 - #431

Merged
levifig merged 1 commit into
mainfrom
fix/go-security-toolchain
Nov 2, 2026
Merged

levifig merged 1 commit into
mainfrom
fix/go-security-toolchain

Conversation

@levifig

@levifig levifig commented Nov 2, 2026 •

Copy link
Copy Markdown
Owner

Loaf's pinned Go 1.27.2 toolchain is affected by GO-2026-6809. Build and audit with Go 1.27.3, and keep fresh Orb environments on the same version with verified Linux archive checksums.

Verification

  • The Linux amd64 and arm64 checksums match the official Go download metadata.
  • The pinned-toolchain vulnerability audit passes with Go 1.27.3. The previous Go 1.27.2 audit reported the affected certificate-verification symbol.
  • Independent review confirms only the toolchain pin, matching bootstrap metadata and changelog changed.
  • Full local verification passes with Go 1.27.3 and Node 24.20.0, including uncached Go tests, vet, CGO-free build, all 39 adapter tests and generated-content checks.

Scope

No other dependency versions, runtime selection, release or deployment changes are included. The broader dependency review is tracked in #428; the Linear-reference checker is separate work in #427.

Ship

Signed candidate fbae720541aa46760e0f3f653b64f888932acafa passed local gates, hosted checks and independent review. The Ship approval and criterion evidence are recorded in the PR conversation.

Closes #429.

Agent notes

Keep Orb bootstrap checksums aligned with the patched release toolchain.

Fixes #429.
@levifig
levifig marked this pull request as ready for review November 2, 2026 21:08

levifig commented Nov 2, 2026

Copy link
Copy Markdown
Owner Author

Approved for landing. The signed Go 1.27.3 patch passes full local verification, the pinned vulnerability audit and all hosted checks. No runtime activation, release or deployment is included.

Agent notes
  • Reviewed head: fbae720541aa46760e0f3f653b64f888932acafa; tree: 605db00adf3a59fe2bed6cdf66f039376e683c0a; base: 5905ca59c82a5e9fad673c6a63c0d276f92a4a63. GitHub reports a valid signature and author me@levifig.com.
  • Update the pinned Go toolchain to fix GO-2026-6809 #429: both Orb checksums match live official metadata; full uncached Go tests, compile/vet/CGO-free checks, 39 adapter tests and generated-content checks pass; pinned Go 1.27.3 audit passes; independent correctness/prose review is clean.
  • The previous Go 1.27.2 audit failed GO-2026-6809. The committed binary names Go 1.27.3, this exact revision and an unmodified source tree.
  • All four Verification boxes are ticked with this evidence. The actual committed base/head changelog check passes.
  • Hosted build and both emitted changelog runs pass. Native rules require pull requests, signatures and linear history with squash only; they do not require these check contexts. Ship nevertheless requires passing checks.
  • The maintainer explicitly authorized verification and Ship. Merge must pin this head and use squash with a deliberate outcome message. Re-read head, boxes and checks immediately before merging.

@levifig
levifig merged commit 5d6d7bf into main Nov 2, 2026
4 checks passed

levifig commented Nov 2, 2026

Copy link
Copy Markdown
Owner Author

Landed as 5d6d7bfe; the resulting-main build passed. #429 is closed with all Verification boxes satisfied. No installed runtime, release or deployment was changed.

Agent notes
  • Landed tree 605db00adf3a59fe2bed6cdf66f039376e683c0a matches the reviewed and tested candidate. GitHub verifies the signature and author me@levifig.com.
  • Local reconciliation remains pending because main belongs to the owner checkout, which contains local configuration. That checkout was preserved. Clean feature worktrees and local/remote feature branches are retained.
  • Remote landing and native issue closure are verified independently of that local synchronization boundary.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update the pinned Go toolchain to fix GO-2026-6809

1 participant