root/geo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(ci): update Gitea Registry CI/CD workflows and enhance image verification
Deployment Config CI / Deployment Config (push) Has been cancelled
Details

Browse Source
This commit is contained in:
liangxu
2026-05-01 23:55:34 +08:00
parent e0b6c1a9fa
commit 0b5bddc1da
2 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
progress.md
+9
View File
@@ -697,3 +697,12 @@
- Confirmed the four platform templates are stored in `article_templates` and currently seeded by `server/cmd/dev-seed/main.go`.
- Confirmed production deployment jobs only run database migrations, so a fresh environment can miss the four template records unless dev seed is run manually.
- Decision: add a production-safe platform-template initializer and wire it into the migrate job/image instead of running the broad dev seed path.
## 2026-05-01T07:15:00Z - Gitea Registry CI/CD cleanup
- Kept `deploy-config-ci.yml` validation-only after the user clarified it should not own images.
- Scoped `frontend-ci.yml` to `admin-web` and `ops-web` plus shared packages/Dockerfiles; removed browser-extension typecheck from this workflow.
- Added Gitea Registry publishing to frontend/backend CI with commit8 tags and skip-if-tag-exists behavior through `deploy/scripts/gitea-registry-images.sh`.
- Added commit8 image verification to compose/k3s/offline deployment paths so CD fails if CI has not produced the required image.
- Changed offline package defaults to use commit8 instead of tag names and to pull business images from the Gitea Registry.
- Verification passed: workflow YAML parse, deploy script `bash -n`, and `sh -n` over all workflow run blocks.