You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+35-4Lines changed: 35 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,10 @@ jobs:
44
44
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
45
45
```
46
46
47
-
See [GitHub's Node.js publishing guide](https://docs.github.com/en/actions/tutorials/publish-packages/publish-nodejs-packages) for more details and examples.
47
+
See GitHub's [Node.js publishing][] guide and npm's [trusted publishing][] docs for more details and examples.
If you have [trusted publishing][] configured for your package and use `npm@>=11.5.1`, you can omit the `token` input and use OIDC instead.
104
+
105
+
> [!IMPORTANT]
106
+
> If you're publishing a private package, you will still need to provide a read-only `token` so the action can read existing versions from the registry before publish.
You can also publish to third-party registries. For example, to publish to the [GitHub Package Registry][], set `token` to `secrets.GITHUB_TOKEN` and `registry` to `https://npm.pkg.github.com`:
101
128
102
129
```yaml
@@ -134,7 +161,7 @@ You can set any or all of the following input parameters using `with`:
0 commit comments