mirror of
https://github.com/vectorize-io/hindsight.git
synced 2026-09-14 19:31:49 +08:00
42d4de25cc
The Docker cp-builder stage moved to node:24-slim, but the two CI jobs that build the control plane directly on the runner still provisioned Node 20, which reached end-of-life on 2026-04-30. That is both an EOL toolchain and a version skew: CI would validate and publish a build produced on a different major than the one the shipped image builds with. - test.yml build-control-plane: runs the CP unit tests, i18n parity check, next build, standalone verification and server smoke test - release.yml release-control-plane: builds and publishes @vectorize-io/hindsight-control-plane to npm Neither package declares an `engines` floor, and next@16.2.11 requires >=20.9.0, so Node 24 clears both. Other Node 20 jobs are deliberately left alone: the TypeScript client jobs (build/test-typescript-client, -oracle, -deno) and test-hindsight-all exercise the published SDK, where pinning an older major is lower-bound coverage rather than an oversight, and changing it should be a separate decision.