Pin the frontend image to v1.3.0
CI / test (push) Successful in 14s
CI / integration (push) Successful in 19s
CI / publish (push) Skipped
CI / docker (push) Successful in 22s

The server image used musicfrontend:latest, so it got whatever frontend was
newest when it was built. Pin the version instead, and bump it when a new
frontend is released.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
SansanandClaude Opus 5.5 committed 2026-10-15 22:17:38 +02:00
1 parent 8da5468efb
commit 9b5a3c58c6
1 file changed
+2 -2
+2 -2
View File
@@ -1,5 +1,5 @@
# The frontend is built and published separately; override to pin a version.
ARG FRONTEND_IMAGE=gitea.sanplex.xyz/sansan/musicfrontend:latest
# The frontend is built and published separately. Bump this when a new frontend is released.
ARG FRONTEND_IMAGE=gitea.sanplex.xyz/sansan/musicfrontend:v1.3.0
# Stage 1: Build the backend on the build machine and cross-compile for the target platform,
# so multi-platform builds need no emulation.