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

fix(docs): clarify local Gitea consumer auth behavior

Browse Source
This commit is contained in:
saravanakumardb1 2026-03-23 18:52:26 -07:00
parent fdf80d6470
commit a0469c2a57
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

@ -137,9 +137,9 @@ That is enough to treat this Mac as the single-VM rehearsal environment.
### Proven locally on this Mac
- shared packages build cleanly in `learning_ai_common_plat`
- a local-only Gitea package token was created and used successfully
- a local-only Gitea package token was created and used successfully for local package publishing
- pilot packages were published to local Gitea npm registry successfully
- a clean scratch `pnpm install` from the local Gitea registry worked on the host
- a clean scratch `pnpm install` from the local Gitea registry worked on the host when `GITEA_NPM_TOKEN` was set to a non-empty placeholder value for `.npmrc` env resolution
- `learning_ai_flowmonk` was migrated on the host from tarball refs to semver `@bytelyst/*` refs
- `learning_ai_flowmonk` host-side install, typecheck, and tests passed against the local Gitea registry
@ -534,9 +534,9 @@ What is **not** yet proven enough to call low-change:
This migration plan is locally validated only when all are true:
- [x] local Gitea package-registry auth verified
- [x] local Gitea package publish auth verified
- [x] local package publish path verified for a pilot package set
- [x] local consumer install path verified
- [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`
- [ ] local Gitea Actions path verified
- [ ] pilot repo migrated successfully end-to-end including Docker