mrhid6andClaude Opus 5 946a748038 chore: declare go 1.26 rather than 1.26.4 across the workspace ...

The 1.26.4 floor meant a base toolchain of 1.26.2 could not load the
workspace at all: the terminal worked only because GOTOOLCHAIN=auto
silently swapped in a downloaded 1.26.4, and gopls -- which does not get
that switch -- failed every packages.Load with

  go: go.work requires go >= 1.26.4 (running go 1.26.2)

Nothing needed the patch-level floor. agent/go.mod already declared plain
go 1.26, so this makes the workspace uniform rather than introducing a new
convention, and CI is unaffected because golang:1.26 is already newer.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-07-25 19:33:58 +01:00

..

cmd

revert(server): drop the licence grandfather migration

2026-07-24 15:49:46 +01:00

internal

revert(server): drop the licence grandfather migration

2026-07-24 15:49:46 +01:00

Dockerfile

build: build Go images from the repo root for the shared module

2026-07-24 13:45:45 +01:00

go.mod

chore: declare go 1.26 rather than 1.26.4 across the workspace

2026-07-25 19:33:58 +01:00

go.sum

fix(server): add the lk go.sum entry the workspace was masking

2026-07-24 15:35:01 +01:00