Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -161,6 +161,8 @@ RUN git -c advice.detachedHead=0 clone --branch "$NVM_VERSION" --depth 1 https:/
&& nvm install 18 && nvm use 18 && npm install -g npm@10.9 pnpm@10.12 && corepack enable && corepack install -g yarn \
&& nvm install 20 && nvm use 20 && npm install -g npm@11.4 pnpm@10.12 && corepack enable && corepack install -g yarn \
&& nvm install 22 && nvm use 22 && npm install -g npm@11.4 pnpm@10.12 && corepack enable && corepack install -g yarn \
&& nvm install 24 && nvm use 24 && npm install -g npm@11.4 pnpm@10.12 && corepack enable && corepack install -g yarn \
&& nvm install 26 && nvm use 26 && npm install -g npm@11.4 pnpm@10.12 && corepack enable && corepack install -g yarn \

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P0 Badge Avoid installing unreleased Node 26

The new nvm install 26 line causes the Docker build to fail. nvm can only install versions that have been published upstream, and Node.js 26 has not been released yet (nvm responds with Version 'v26.0.0' (with LTS) not yet released). Because this is inside a single RUN block, the entire image build halts. Please revert or guard this step until Node 26 actually ships.

Useful? React with 👍 / 👎.

&& nvm alias default "$NODE_VERSION" \
&& nvm cache clear \
&& npm cache clean --force || true \
Expand Down