ci(release): bind gitea token for archive checkout

This commit is contained in:
Xiaoxia AI
2026-06-22 18:05:26 +08:00
parent 785b73239e
commit f73b87314d
3 changed files with 13 additions and 6 deletions
+7 -6
View File
@@ -53,12 +53,13 @@ Do not store SSH private keys in the repository.
On `v*` tag push:
1. `build-production-runtime-images` runs on `runtime-builder`.
2. It executes `scripts/build_release_images.sh <tag>`.
3. It builds `apps/web/dist` in a Node Docker container, not on production.
4. It packages `release-<tag>.tar.gz` with the prebuilt Web dist.
5. It uploads both `runtime-images-<tag>.tar` and `release-<tag>.tar.gz` to production.
6. `deploy-production` runs after the build job succeeds.
7. `deploy-production` extracts the prebuilt release artifact, loads `/var/lib/xiaoxia-saas-production/runtime-images-<tag>.tar`, and restarts API/Worker/Web.
2. Checkout downloads the repository archive using the explicit `${{ github.token }}` environment binding; runner shell environments must not assume `GITHUB_TOKEN` is implicitly set.
3. It executes `scripts/build_release_images.sh <tag>`.
4. It builds `apps/web/dist` in a Node Docker container, not on production.
5. It packages `release-<tag>.tar.gz` with the prebuilt Web dist.
6. It uploads both `runtime-images-<tag>.tar` and `release-<tag>.tar.gz` to production.
7. `deploy-production` runs after the build job succeeds.
8. `deploy-production` extracts the prebuilt release artifact, loads `/var/lib/xiaoxia-saas-production/runtime-images-<tag>.tar`, and restarts API/Worker/Web.
If either the release tar or runtime image tar is missing, production deploy must fail.