bytelyst/learning_ai_common_plat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(docs): update local Gitea migration status

Browse Source
This commit is contained in:
saravanakumardb1 2026-03-23 19:17:07 -07:00
parent 6f748b11d4
commit 03b92eb2df
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md
View File

@ -539,7 +539,7 @@ This migration plan is locally validated only when all are true:
- [x] local Gitea package publish auth verified
- [x] local package publish path verified for a pilot package set
- [x] local consumer install path verified on the host with non-empty `GITEA_NPM_TOKEN` env resolution
- [ ] local Docker build path verified without `docker-prep.sh`
- [x] local FlowMonk backend/web Docker build path verified without `docker-prep.sh` using the documented local workaround
- [ ] local Gitea Actions path verified
- [ ] pilot repo migrated successfully end-to-end including Docker
- [ ] rollback path documented and tested conceptually
@ -551,7 +551,7 @@ This migration plan is locally validated only when all are true:
1. create or verify a local-only Gitea package token
2. publish a minimal pilot `@bytelyst/*` package set to local Gitea only
3. validate install from local Gitea in one pilot consumer
4. validate Docker build from local Gitea in that pilot repo
5. validate the same path via local Gitea Actions
3. validate the same FlowMonk backend/web Docker workaround path via local Gitea Actions
4. decide whether the current `localhost` tarball workaround is acceptable for the single-VM pattern or if Gitea URL shape must be corrected first
5. document and validate the rollback path for the FlowMonk pilot
6. only then expand to broader ecosystem migration