All checks were successful
Build & Deploy Staging / build-and-deploy (release) Successful in 28s
git fetch origin won't replace a tag that already exists locally pointing at a different commit. When v3.3.5 was force-moved on origin after a first failed CI run, the staging runner kept the stale tag cached and re-checked-out the old commit — the compose-env-wiring fix was never actually applied and the container booted without LEADERBOARD_INCLUDE_TEST_DEFAULT. --tags --force makes the behaviour safe for moved tags. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.7 KiB
1.7 KiB