From 9866dd5f23f8f31095e9581678f977e6e2a8aaa6 Mon Sep 17 00:00:00 2001 From: hsiegeln <37154749+hsiegeln@users.noreply.github.com> Date: Wed, 25 Mar 2026 09:37:51 +0100 Subject: [PATCH] fix: move design system dev install after COPY to bust Docker cache The npm install @cameleer/design-system@dev was in the same cached layer as npm ci, so Docker never re-ran it when the registry had a new version. Co-Authored-By: Claude Opus 4.6 (1M context) --- ui/Dockerfile | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/ui/Dockerfile b/ui/Dockerfile index 80d77046..e0a9826a 100644 --- a/ui/Dockerfile +++ b/ui/Dockerfile @@ -4,12 +4,15 @@ WORKDIR /app ARG REGISTRY_TOKEN COPY package.json package-lock.json .npmrc ./ RUN echo "//gitea.siegeln.net/api/packages/cameleer/npm/:_authToken=${REGISTRY_TOKEN}" >> .npmrc && \ - npm ci && \ - npm install @cameleer/design-system@dev && \ - rm -f .npmrc + npm ci COPY . . +# Upgrade design system to latest dev snapshot (after COPY to bust Docker cache) +RUN echo "//gitea.siegeln.net/api/packages/cameleer/npm/:_authToken=${REGISTRY_TOKEN}" >> .npmrc && \ + npm install @cameleer/design-system@dev && \ + rm -f .npmrc + ARG VITE_ENV_NAME=PRODUCTION ENV VITE_ENV_NAME=$VITE_ENV_NAME RUN npm run build