ci: allow trusted publishing with default registry (QQQ #912) #47

Merged
KofTwentyTwo merged 1 commits from feature/GH-912-default-registry into develop 2026-09-29 20:27:20 +00:00
KofTwentyTwo commented 2026-09-29 20:26:11 +00:00 (Migrated from github.com)

Remove the tracked .npmrc containing only registry and @qrunio:registry, both set to npm's default public registry. The trusted publisher intentionally rejects project config, so this redundant file stopped job 382 before OIDC acquisition. Package publishConfig.registry remains explicitly set to the same public registry; dependencies and lockfile are unchanged.

Validate with a clean npm ci, TypeScript build, effective registry checks and normal CI. After merge, verify the real public package with a fresh consumer. No credential or registry behavior change is intended.

Tracks https://github.com/QRun-IO/qqq/issues/912; Boolean correction https://github.com/QRun-IO/qqq/issues/915 is already delivered in verified public orb 0.6.8.

Remove the tracked `.npmrc` containing only `registry` and `@qrunio:registry`, both set to npm's default public registry. The trusted publisher intentionally rejects project config, so this redundant file stopped job 382 before OIDC acquisition. Package `publishConfig.registry` remains explicitly set to the same public registry; dependencies and lockfile are unchanged. Validate with a clean `npm ci`, TypeScript build, effective registry checks and normal CI. After merge, verify the real public package with a fresh consumer. No credential or registry behavior change is intended. Tracks https://github.com/QRun-IO/qqq/issues/912; Boolean correction https://github.com/QRun-IO/qqq/issues/915 is already delivered in verified public orb 0.6.8.
Sign in to join this conversation.