tiennm99/goclaw
1
0 Fork 0
mirror of https://github.com/tiennm99/goclaw.git synced 2026-10-20 02:17:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: speed up zuey beta deploy (#127)

Browse Source 
* ci: speed up zuey beta deploy

* ci: mark issue 88 plan complete
This commit is contained in:
Duy /zuey/ authored and GitHub committed 2026-05-31 21:47:28 +07:00
1 parent 94cbaa9f0f
commit 64c02ea5a6
9 files changed
+460 -15
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/deployment-guide.md
+3 -1
View File
@@ -190,7 +190,9 @@ The remote trigger endpoint fails closed unless `GOCLAW_UPGRADE_TRIGGER_TOKEN` i
### Automatic Beta Deploy From `dev`
Pushing or merging into `dev` runs `.github/workflows/dev-beta-release.yaml`. After Go/Web checks pass, the workflow creates the next semantic beta tag, publishes the prerelease assets, promotes beta Docker aliases, then deploys that exact beta tag to the zuey VPS through the gateway upgrade endpoint.
Pushing or merging into `dev` runs `.github/workflows/dev-beta-release.yaml`. After Go/Web checks pass, the workflow creates the next semantic beta tag, publishes the linux amd64 prerelease asset and checksum, then deploys that exact beta tag to the zuey VPS through the gateway upgrade endpoint.
Linux arm64 release assets, full checksums, multi-arch Docker images, and beta Docker aliases continue after the fast zuey deploy path. Those completion jobs are still required to pass; the workflow remains failed if later artifact completion breaks. Zuey deploy and Docker beta alias promotion both skip stale beta tags so older runs cannot roll back a newer beta.
Required GitHub Actions configuration: