@mailpace/mcp 2.0.0 → 2.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -127,7 +127,16 @@ com.mailpace/mailpace-mcp
|
|
|
127
127
|
|
|
128
128
|
### One-time setup
|
|
129
129
|
|
|
130
|
-
1.
|
|
130
|
+
1. Configure npm Trusted Publishing for `@mailpace/mcp`:
|
|
131
|
+
- Open `https://www.npmjs.com/package/@mailpace/mcp/access`
|
|
132
|
+
- Under **Trusted Publisher**, choose **GitHub Actions**
|
|
133
|
+
- Organization or user: `mailpace`
|
|
134
|
+
- Repository: `mailpace-mcp`
|
|
135
|
+
- Workflow filename: `release.yml`
|
|
136
|
+
- Allowed action: **npm publish**
|
|
137
|
+
|
|
138
|
+
The release workflow authenticates to npm with GitHub OIDC, so no `NPM_TOKEN` secret is used.
|
|
139
|
+
|
|
131
140
|
2. Generate an Ed25519 key pair for DNS authentication:
|
|
132
141
|
|
|
133
142
|
```bash
|
|
@@ -154,7 +163,9 @@ git tag v2.0.0
|
|
|
154
163
|
git push origin v2.0.0
|
|
155
164
|
```
|
|
156
165
|
|
|
157
|
-
|
|
166
|
+
Because `2.0.0` was published before trusted publishing was enabled, use a new version such as `2.0.1` for the first workflow release. This lets npm validate the trusted publisher within its setup window. Subsequent tags publish normally with OIDC.
|
|
167
|
+
|
|
168
|
+
The `Release` workflow runs typechecking and tests, verifies the tag matches `package.json`, publishes to npm using GitHub OIDC, waits for the package to appear, and publishes the version metadata to the Official MCP Registry.
|
|
158
169
|
|
|
159
170
|
## Security
|
|
160
171
|
|