Skip to content

Commit 4142b3f

Browse files
committed
setup npm registry url
The `NPM_TOKEN` name was also incorrect (surprise?). Found another resource here that mentions the `registry-url` option and `NODE_AUTH_TOKEN`. Let's see if that works... https://docs.github.com/en/actions/guides/publishing-nodejs-packages
1 parent fac02f3 commit 4142b3f

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

.github/workflows/release-insiders.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ jobs:
1919
uses: actions/setup-node@v2
2020
with:
2121
node-version: ${{ matrix.node-version }}
22+
registry-url: 'https://registry.npmjs.org'
2223

2324
- name: Use cached node_modules
2425
id: cache
@@ -54,4 +55,4 @@ jobs:
5455
run: npm publish --tag insiders
5556
env:
5657
CI: true
57-
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
58+
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/release.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ jobs:
1919
uses: actions/setup-node@v2
2020
with:
2121
node-version: ${{ matrix.node-version }}
22+
registry-url: 'https://registry.npmjs.org'
2223

2324
- name: Use cached node_modules
2425
id: cache
@@ -47,4 +48,4 @@ jobs:
4748
run: npm publish
4849
env:
4950
CI: true
50-
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
51+
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

0 commit comments

Comments
 (0)