chore: separate test release packaging rules

This commit is contained in:
wushumin
2026-06-03 22:50:35 +08:00
parent 5fe201e8fe
commit 9dfd5976ed
9 changed files with 16 additions and 7 deletions

View File

@@ -9,7 +9,7 @@ Project root: `/Users/wushumin/www/biyou/anxinyan`.
Use the outer repository as the single source of truth for all project work. Do not create separate Git branch systems inside `server-api`, `admin-web`, `user-app`, or `work-app`.
Do not manage release artifacts in Git. Files under `releases/`, including zip packages, APKs, and checksum files, are local delivery artifacts and must not be committed or pushed.
Do not manage release artifacts in Git. Files under `releases/` and `releases_dev/`, including zip packages, APKs, and checksum files, are local delivery artifacts and must not be committed or pushed. Put production packages in `releases/` and test packages in `releases_dev/`.
## Branch Model
@@ -59,7 +59,7 @@ Before changing code symbols, follow the repository `AGENTS.md` GitNexus rule: r
For release packaging or deployment preparation, also follow the release checklist and packaging skill. At minimum, run the relevant backend smoke/audit scripts and frontend checks for the surfaces touched.
Release packages should stay under the ignored local `releases/` directory and be handed off separately from Git branches.
Production packages should stay under the ignored local `releases/` directory and use `https://api.anxinjianyan.com`. Test packages should stay under the ignored local `releases_dev/` directory and use `https://test.api.anxinjianyan.com`. Hand off both kinds of artifacts separately from Git branches.
## Documentation Source