mirror of
https://github.com/lightninglabs/lightning-terminal.git
synced 2026-08-13 12:33:36 +02:00
a04ecb750d
The frontend job was pinned to node 16, which is old enough that some of the packages patched in this branch refuse to install there. tar and esbuild want node 18 or newer, serialize-javascript wants 20. Node was also only pinned in the frontend job. The backend, proto-compile-check and itest jobs all reference matrix.node_version without declaring it in their matrix, so the expression resolved to an empty string and setup-node fell back to whatever the runner happened to ship. Two of those run `yarn install --frozen-lockfile`, so they need a known version too. Both are fixed by a NODE_VERSION env var, matching how GO_VERSION is already handled. It replaces the matrix entry rather than feeding it, because the env context isn't available inside strategy.matrix. |
||
|---|---|---|
| .. | ||
| claude.yml | ||
| docker.yml | ||
| main.yml | ||