From 03b92eb2df61fb11b43fb805ccd1123e9a40d1be Mon Sep 17 00:00:00 2001 From: saravanakumardb1 Date: Mon, 23 Mar 2026 19:17:07 -0700 Subject: [PATCH] fix(docs): update local Gitea migration status --- docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md b/docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md index f27d18df..c4cf3342 100644 --- a/docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md +++ b/docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md @@ -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