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
{{ message }}
Repository navigation
Commit cd511f4
Browse filesBrowse the repository at this point in the historyBrowse files
## Motivation and Context
Fixesmodelcontextprotocol#1505.
The GitHub Actions publishing guide downloaded `mcp-publisher` through
the mutable `releases/latest` URL and extracted it without checking the
published Sigstore bundle. The three credential-bearing examples now pin
the release to `v1.8.1`, download the archive and its bundle separately,
verify the release workflow identity and GitHub Actions OIDC issuer with
`cosign verify-blob`, and extract only after verification.
## How Has This Been Tested?
- Parsed all three fenced workflow examples with PyYAML and checked the
pinned version, cosign installer, and verification flags.
- Verified the published `v1.8.1` Linux amd64 archive against its
published Sigstore bundle with cosign v3.0.6 (the version installed by
the pinned cosign-installer action); verification returned `Verified
OK`.
- Ran `git diff --check`.
## Breaking Changes
None. This only hardens the documented installer workflow; existing
registry APIs and authentication commands are unchanged.
## Types of changes
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing users to
update)
- [x] Documentation update
## Checklist
- [x] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [x] My code follows the repository's style guidelines
- [x] New and existing tests pass locally (documentation/workflow
validation listed above)
- [x] I have added appropriate error handling
- [x] I have added or updated documentation as needed
## Additional context
The release version is intentionally explicit so upgrades are
reviewable. The Sigstore certificate identity is constrained to this
repository's release workflow and the selected tag.
---------
Co-authored-by: Radoslav Dimitrov <[email protected]>
Copy file name to clipboardExpand all lines: docs/modelcontextprotocol-io/github-actions.mdx
+69-7Lines changed: 69 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,11 @@ sidebarTitle: GitHub Actions
11
11
12
12
In your server project directory, create a `.github/workflows/publish-mcp.yml` file. Here is an example for npm-based local server, but the MCP Registry publishing steps are the same for all package types:
13
13
14
+
The examples pin `mcp-publisher` to a specific release and verify its Sigstore
15
+
bundle before extracting it. When upgrading, update `MCP_PUBLISHER_VERSION` to
16
+
the intended release tag deliberately; do not switch back to the mutable
17
+
`releases/latest` URL.
18
+
14
19
<CodeGroup>
15
20
16
21
```yaml OIDC authentication (recommended)
@@ -26,6 +31,8 @@ jobs:
26
31
permissions:
27
32
id-token: write # Required for OIDC authentication
# TODO: Replace `example.com` with your domain name
@@ -245,7 +307,7 @@ The workflow will run tests, build the package, publish the package to npm, and
245
307
| Error Message | Action |
246
308
| --- | --- |
247
309
| "Authentication failed" | Ensure `id-token: write` permission is set for OIDC, or check secrets. |
248
-
| "invalid audience" | Your `mcp-publisher` binary is too old for this registry deployment. Re-run the install step shown above so you pick up the latest release. |
310
+
| "invalid audience" | Your `mcp-publisher` binary is too old for this registry deployment. Update `MCP_PUBLISHER_VERSION` to a compatible release and rerun the workflow. |
249
311
| "Package validation failed" | Verify your package successfully published to the package registry (e.g., npm, PyPI), and that your package has the [necessary verification information](./package-types). |
0 commit comments