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
* feat: support tokenless trusted publishers
* docs: add trusted publisher usage
* fix: prevent error in dry-run publication due to collision with an already published version
* style: typo
* fix: update npm only if needed
* style: use "preferred/legacy" instead of "deprecated"
On [npmjs.com](https://www.npmjs.com/), configure the root publish workflow of your GitHub repository as a trusted publisher for your package.
101
+

102
+
103
+
NB: You can have only one trusted publisher per package, if you need multiple publication triggers (workflow_dispatch, release, etc.), you need to merge them into a single workflow referenced as trusted publisher.
104
+
105
+
### With npm token (legacy)
106
+
107
+
1.**Call the Reusable Workflow**
65
108
66
-
2.**Call the Reusable Workflow**
67
109
In another workflow file (e.g., triggered by a release), invoke this reusable workflow like so:
68
110
69
111
```yaml
@@ -90,7 +132,8 @@ for the package scope, Node.js version, registry URL, and other options. The wor
90
132
npm-token: ${{ secrets.NPM_TOKEN }}
91
133
```
92
134
93
-
3. **Configure Secrets**
135
+
2. **Configure Secrets**
136
+
94
137
Ensure that the `NPM_TOKEN` secret is added to your repository’s settings. This token is required to authenticate
0 commit comments