Pairs with mesh-controller#88. builder and route-proxy both build from the mesh-controller repository's context, so its go.mod is theirs, and nats.go v1.54.0 puts that at go >= 1.26. Pinned at 1.25.14 they cannot compile it — the build machine failed on exactly this while catching the mesh up after today's merges.
Each moves to the 1.26.8 digest of the flavour it already used: alpine for builder, debian for route-proxy. Nothing changes but the compiler version.
Pairs with mesh-controller#88. `builder` and `route-proxy` both build from the mesh-controller repository's context, so its `go.mod` is theirs, and `nats.go v1.54.0` puts that at `go >= 1.26`. Pinned at 1.25.14 they cannot compile it — the build machine failed on exactly this while catching the mesh up after today's merges.
Each moves to the 1.26.8 digest of the flavour it already used: alpine for `builder`, debian for `route-proxy`. Nothing changes but the compiler version.
builder and route-proxy both build from the mesh-controller repository's context,
so its go.mod is theirs, and `nats.go v1.54.0` puts that at `go >= 1.26`. Pinned at
1.25.14 they cannot compile it: the build machine's own build failed with "go.mod
requires go >= 1.26.0 (running go 1.25.14)".
Each moves to the 1.26.8 digest of the flavour it already used — alpine for
builder, debian for route-proxy — so nothing changes but the compiler version.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Pairs with mesh-controller#88.
builderandroute-proxyboth build from the mesh-controller repository's context, so itsgo.modis theirs, andnats.go v1.54.0puts that atgo >= 1.26. Pinned at 1.25.14 they cannot compile it — the build machine failed on exactly this while catching the mesh up after today's merges.Each moves to the 1.26.8 digest of the flavour it already used: alpine for
builder, debian forroute-proxy. Nothing changes but the compiler version.