From 3b5fcc51cc0b6eac4833e8ef014ee454fe632466 Mon Sep 17 00:00:00 2001 From: hermes_dev Date: Fri, 30 Oct 2026 09:56:19 +0000 Subject: [PATCH] fix(ui): pin npm build stage to TLS 1.2 on the CI host uplink The CI host uplink (192.168.1.108) drops TLS 1.3 ClientHello carrying the hybrid X25519MLKEM768 key share, so registry.npmjs.org is unreachable from the seeded node:22-alpine build stage while the same host answers over TLS 1.2. RUN npm ci hung until the build was cancelled. Cap only the UI build stage at TLS 1.2 via NODE_OPTIONS=--tls-max-v1.2. Certificates, SRI and the lockfile are untouched; no mirror, fallback or cache-substituted packages. Remove the line once TLS 1.3 works from the CI host again. --- apps/ui/Dockerfile | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/apps/ui/Dockerfile b/apps/ui/Dockerfile index c457c52..f0b33fd 100644 --- a/apps/ui/Dockerfile +++ b/apps/ui/Dockerfile @@ -1,5 +1,10 @@ FROM node:22-alpine AS build +# The CI host uplink drops TLS 1.3 ClientHello carrying the hybrid +# X25519MLKEM768 key share; pin the npm stage to TLS 1.2 until that network +# defect is fixed. Certificates, SRI and the lockfile are unaffected. +ENV NODE_OPTIONS=--tls-max-v1.2 + WORKDIR /app COPY apps/ui/package.json apps/ui/package-lock.json ./ -- 2.54.0