v1.7.0 #318

Merged
LukeGus merged 138 commits from dev-1.7.0 into main 2025-10-01 20:40:10 +00:00
Showing only changes of commit 7865a28d3d - Show all commits

View File

@@ -11,7 +11,6 @@ ENV npm_config_target_arch=x64
ENV npm_config_target_libc=glibc
RUN npm ci --force --ignore-scripts && \
npm install @rollup/rollup-linux-x64-gnu @esbuild/linux-x64 @lightningcss/linux-x64-gnu --force && \
npm cache clean --force
# Stage 2: Build frontend
@@ -20,8 +19,7 @@ WORKDIR /app
gemini-code-assist[bot] commented 2025-10-01 20:38:40 +00:00 (Migrated from github.com)
Review

high

This command removes package-lock.json and uses npm install --force, which undermines the principle of reproducible builds. Using npm ci is strongly recommended for Docker builds as it installs dependencies exactly as specified in package-lock.json, ensuring that the build is consistent and deterministic across all environments. If there are dependency conflicts, they should be resolved in package.json rather than being bypassed with --force.

RUN npm ci --ignore-scripts && \
    npm cache clean --force
![high](https://www.gstatic.com/codereviewagent/high-priority.svg) This command removes `package-lock.json` and uses `npm install --force`, which undermines the principle of reproducible builds. Using `npm ci` is strongly recommended for Docker builds as it installs dependencies exactly as specified in `package-lock.json`, ensuring that the build is consistent and deterministic across all environments. If there are dependency conflicts, they should be resolved in `package.json` rather than being bypassed with `--force`. ``` RUN npm ci --ignore-scripts && \ npm cache clean --force ```
COPY . .
RUN npm install @rollup/rollup-linux-x64-gnu @esbuild/linux-x64 @lightningcss/linux-x64-gnu --force && \
npm cache clean --force && \
RUN npm cache clean --force && \
npm run build
# Stage 3: Build backend TypeScript