P1: Tighten CI go-version pinning #1702

Closed
opened 2026-10-27 13:41:27 +00:00 by sam · 0 comments
Owner

CI's go-version is set to '1.26' (floating) while go.mod has exact 1.26.5. This loose coupling means CI could use 1.26.0-1.26.5 or newer minor versions, potentially missing bugs or compatibility issues.

Need to:

  • Pin CI go-version to exact match go.mod (currently 1.26.5, will be 1.26.6+ after P0 bump)
  • Consider using same variable/source of truth for both
  • Update CI configuration files

Blocked by: Go version bump (archie-core-1sjk) for consistency

Close reason

Switched CI to actions/setup-go go-version-file: go.mod so CI's Go version is always sourced from go.mod directly, eliminating drift


Imported from beads archie-core-zq4l · GitHub #660 · type task · priority P1 · created 2026-08-28 · closed 2026-08-31

CI's go-version is set to '1.26' (floating) while go.mod has exact 1.26.5. This loose coupling means CI could use 1.26.0-1.26.5 or newer minor versions, potentially missing bugs or compatibility issues. Need to: - Pin CI go-version to exact match go.mod (currently 1.26.5, will be 1.26.6+ after P0 bump) - Consider using same variable/source of truth for both - Update CI configuration files Blocked by: Go version bump (archie-core-1sjk) for consistency ### Close reason Switched CI to actions/setup-go go-version-file: go.mod so CI's Go version is always sourced from go.mod directly, eliminating drift --- _Imported from beads `archie-core-zq4l` · GitHub #660 · type task · priority P1 · created 2026-08-28 · closed 2026-08-31_
sam added the hightask labels 2026-10-27 13:41:27 +00:00
sam self-assigned this 2026-10-27 13:41:27 +00:00
sam closed this issue 2026-10-27 13:41:27 +00:00
sam added a new dependency 2026-10-27 13:42:28 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1702