fix(ci): bump go.work to 1.25 to match veza-backend-api/go.mod
Some checks failed
Security Scan / Secret Scanning (gitleaks) (push) Successful in 4m21s
Veza CI / Rust (Stream Server) (push) Successful in 6m22s
Veza CI / Backend (Go) (push) Failing after 13m45s
Veza CI / Frontend (Web) (push) Successful in 22m26s
Veza CI / Notify on failure (push) Successful in 5s

Backend Go CI was still failing on 9e817aa6b with:

  go: module . listed in go.work file requires go >= 1.25.0,
  but go.work lists go 1.24.0; to update it: go work use

The go.mod of veza-backend-api was bumped to 1.25.0 in 24af2f72b
("ci: bump Go to 1.25 and fix goimports drift"), but go.work at the
repo root was never updated to match. The previous CI runs tolerated
the mismatch through toolchain auto-download at the cost of ~3 min
per job; today's dependency bumps (9e817aa6b) apparently pulled a
directive that flips Go into strict mode and makes the mismatch fatal.

Local go.work had been updated to 1.25.0 automatically by `go get`
during the dep bumps but was never staged, so the previous commit
shipped go.work still at 1.24.0. This commit stages the one-line
version bump that go had already applied locally.
This commit is contained in:
senke 2026-04-15 15:06:50 +02:00
parent 9e817aa6b3
commit 51ed89cda7

View file

@ -1,3 +1,3 @@
go 1.24.0
go 1.25.0
use ./veza-backend-api