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

fix(docs): capture local Docker auth blocker

Browse Source
This commit is contained in:
saravanakumardb1 2026-03-23 18:57:34 -07:00
parent 90e3f8d056
commit fdf640e5bd
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md
View File

@ -170,7 +170,7 @@ The remaining blocker is not host-side package publishing or host-side package c
The blocker is specifically:
- Docker / BuildKit installs against the local Homebrew Gitea instance on this Mac
- registry metadata and tarball fetch behavior across the Mac host ↔ Docker build boundary
- the Docker-side auth path, where `host.docker.internal` reaches the registry but placeholder-token package fetches still fail with `401 Unauthorized`
At the time of writing:
@ -190,6 +190,7 @@ The local rehearsal on this Mac has proven enough to validate the **host-side**
- Docker / BuildKit package installs from the local Homebrew Gitea instance are still not green
- the Homebrew Gitea `ROOT_URL` / package tarball URL behavior is still fragile across host and Docker boundaries
- Docker-side package installs currently need a real Gitea package token even though host-side installs only need non-empty `GITEA_NPM_TOKEN` env resolution for `.npmrc`
- local Gitea Actions has not yet been validated end-to-end for the package build → publish → consumer flow
- the FlowMonk pilot is currently validated only for backend/web host-side consumption; Docker is still blocked and mobile remains outside the registry-backed pilot slice
- not all `@bytelyst/*` packages have been revalidated under the local Gitea registry with a fresh consumer install after the `pnpm pack` publish flow changes