Skip to content

Commit d265606

Browse files
yokotasoclaude
andcommitted
fix: specify GitHub Packages registry explicitly in npm publish
npm publish was defaulting to registry.npmjs.org instead of npm.pkg.github.com, causing ENEEDAUTH errors. Adding --registry flag ensures the correct registry is used regardless of .npmrc resolution in workspace setups. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 61ac45d commit d265606

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

.github/workflows/publish-gpr.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,6 @@ jobs:
2323
- name: Set version
2424
if: ${{ inputs.version != '' }}
2525
run: npm version "${{ inputs.version }}" --no-git-tag-version -w pkgs/typed-api-spec
26-
- run: npm publish -w pkgs/typed-api-spec --access public
26+
- run: npm publish -w pkgs/typed-api-spec --access public --registry https://npm.pkg.github.com
2727
env:
2828
NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

0 commit comments

Comments
 (0)