ci: disable registry cache for backend build to fix poisoned buildcache
The backend buildcache was contaminated with frontend image layers, causing the backend image to be built with the wrong content. Using no-cache forces a fresh build until the cache can be reliably separated. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -135,8 +135,7 @@ jobs:
|
|||||||
push: ${{ gitea.event_name != 'pull_request' }}
|
push: ${{ gitea.event_name != 'pull_request' }}
|
||||||
tags: ${{ steps.meta-backend.outputs.tags }}
|
tags: ${{ steps.meta-backend.outputs.tags }}
|
||||||
labels: ${{ steps.meta-backend.outputs.labels }}
|
labels: ${{ steps.meta-backend.outputs.labels }}
|
||||||
cache-from: type=registry,ref=${{ env.REGISTRY }}/${{ env.BACKEND_IMAGE_NAME }}:buildcache
|
no-cache: true
|
||||||
cache-to: type=registry,ref=${{ env.REGISTRY }}/${{ env.BACKEND_IMAGE_NAME }}:buildcache,mode=max
|
|
||||||
build-args: |
|
build-args: |
|
||||||
NODE_ENV=production
|
NODE_ENV=production
|
||||||
CI=true
|
CI=true
|
||||||
|
|||||||
Reference in New Issue
Block a user