saravanakumardb1 85bb860382 fix(gitea): fix publish auth — scoped registry + proxy=false in .npmrc ... Root causes found: 1. publishConfig.registry in each package.json overrides --registry CLI flag, causing npm to hit gitea.bytelyst.com through corp proxy. 2. Global ~/.npmrc proxy settings (NPM_CONFIG_PROXY env vars) route localhost:3300 through the corporate proxy. 3. No .npmrc with auth token was created for npm publish to use. Fix: generate a proper .npmrc in WORK_DIR with: - _authToken for registry auth - @bytelyst:registry scoped override (bypasses publishConfig) - proxy=false + https-proxy=false on corp network - Unified corp/home publish path (both use same .npmrc) Token scope issue still open: current GITEA_NPM_TOKEN has read:package but not write:package — needs regeneration in Gitea UI.		2026-04-13 00:21:13 -07:00
..
harden-publish-config.sh	refactor(scripts): move 5 Gitea scripts into scripts/gitea/ subdirectory	2026-04-13 00:02:55 -07:00
publish-local-packages.sh	refactor(scripts): move 5 Gitea scripts into scripts/gitea/ subdirectory	2026-04-13 00:02:55 -07:00
publish-outdated-packages.sh	fix(gitea): fix publish auth — scoped registry + proxy=false in .npmrc	2026-04-13 00:21:13 -07:00
release-packages.sh	refactor(scripts): move 5 Gitea scripts into scripts/gitea/ subdirectory	2026-04-13 00:02:55 -07:00
run-registry-tests.sh	refactor(scripts): move 5 Gitea scripts into scripts/gitea/ subdirectory	2026-04-13 00:02:55 -07:00