fix(ci): Force fresh base image in Docker builds

Add --pull and --no-cache flags to docker buildx build to ensure:
- Base image (node:22.20-alpine) is always pulled fresh
- No cached layers from previous builds are used

This fixes issue #1079 where published images contained outdated
Node.js v20.18.x instead of the expected v22.20.x from Dockerfile.dev,
causing Prisma 7 compatibility failures.

Fixes #1079
This commit is contained in:
Adam Kovacs 2025-12-14 21:21:04 -08:00
parent 8e30271fbc
commit 6c4cf4164c
1 changed files with 2 additions and 0 deletions

View File

@ -53,6 +53,8 @@ jobs:
-f Dockerfile.dev \ -f Dockerfile.dev \
-t ghcr.io/gitroomhq/postiz-app:${{ env.CONTAINERVER }}-${{ matrix.arch }} \ -t ghcr.io/gitroomhq/postiz-app:${{ env.CONTAINERVER }}-${{ matrix.arch }} \
--build-arg NEXT_PUBLIC_VERSION=${{ env.NEXT_PUBLIC_VERSION }} \ --build-arg NEXT_PUBLIC_VERSION=${{ env.NEXT_PUBLIC_VERSION }} \
--pull \
--no-cache \
--provenance=false --sbom=false \ --provenance=false --sbom=false \
--output "type=registry,name=ghcr.io/gitroomhq/postiz-app:${{ env.CONTAINERVER }}-${{ matrix.arch }}" . --output "type=registry,name=ghcr.io/gitroomhq/postiz-app:${{ env.CONTAINERVER }}-${{ matrix.arch }}" .