@relay-org/relay-mcp 0.1.0 → 0.1.75
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 +23 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -76,3 +76,26 @@ For a local agent on the same machine, use a Unix socket instead (no token neede
|
|
|
76
76
|
| `create_signed_link` | Time-bounded share URL for signed-link lanes |
|
|
77
77
|
| `list_companions` | Companion services for an app lane |
|
|
78
78
|
| `restart_companion` | Restart a companion service |
|
|
79
|
+
|
|
80
|
+
## Publishing (maintainers)
|
|
81
|
+
|
|
82
|
+
`@relay-org/relay-mcp` is published from GitHub Actions using npm trusted publishing (OIDC).
|
|
83
|
+
|
|
84
|
+
If publish fails with `npm ERR! code E404` on:
|
|
85
|
+
|
|
86
|
+
`PUT https://registry.npmjs.org/@relay-org%2frelay-mcp`
|
|
87
|
+
|
|
88
|
+
verify package-level trusted publisher settings on npmjs.com for `@relay-org/relay-mcp`:
|
|
89
|
+
|
|
90
|
+
- Organization/user: `Relay-CI`
|
|
91
|
+
- Repository: `Relay`
|
|
92
|
+
- Workflow filename: `auto-release.yml` (must match exactly)
|
|
93
|
+
- Environment: `npm-publish` (must match exactly if configured in workflow)
|
|
94
|
+
|
|
95
|
+
Important:
|
|
96
|
+
|
|
97
|
+
- Trusted publishing is configured per package, not per scope.
|
|
98
|
+
- npm currently allows one trusted publisher connection per package.
|
|
99
|
+
- If another workflow publishes this package, either:
|
|
100
|
+
- switch the trusted publisher to that workflow, or
|
|
101
|
+
- use a granular npm token in that alternate workflow.
|