Repository navigation
docs(sandbox-agent): sync from rivet-dev/agents - #127
NathanFlurry wants to merge 1 commit into
Conversation
|
🚅 Deployed to the website-pr-127 environment in rivet-website
|
![the-company-company[bot]](https://avatars.githubusercontent.com/in/3874572?s=60&v=4){kind=small}
| } | ||
| } | ||
| }, | ||
| "McpCommand": { |
There was a problem hiding this comment.
🟠 Medium · Removing MCP schemas leaves the published API reference unresolved
McpServerConfig still references #/components/schemas/McpCommand, McpOAuthConfigOrDisabled, and McpRemoteTransport, so the updated openapi.json now has three unresolved component references. Its generated mcpserverconfig.mdx page also still links to the deleted schema pages, producing dead documentation links. Keep these component definitions/pages, or inline/update every remaining reference as part of the generated sync.
0798f7c to
af9bbd7
Compare
| } | ||
| } | ||
| }, | ||
| "McpCommand": { |
There was a problem hiding this comment.
🟠 Medium · Removing MCP schemas leaves the published API reference unresolved
McpServerConfig still references #/components/schemas/McpCommand, McpOAuthConfigOrDisabled, and McpRemoteTransport; validating this head finds all three references unresolved. Its generated schema page also still links to the deleted pages, so the site’s internal-link check will fail. Keep these component definitions/pages, or inline/update every remaining reference as part of the generated sync.
af9bbd7 to
c7c0faf
Compare
| } | ||
| } | ||
| }, | ||
| "McpCommand": { |
There was a problem hiding this comment.
🟠 Medium · Removing MCP schemas leaves the published API reference unresolved
McpServerConfig still references #/components/schemas/McpCommand, McpOAuthConfigOrDisabled, and McpRemoteTransport, so this document retains three unresolved component references. Its generated schema page also still links to the deleted pages, causing the site’s internal-link check to fail. Keep these component definitions/pages, or inline/update every remaining reference as part of the generated sync.
c7c0faf to
39e0ba5
Compare
| } | ||
| } | ||
| }, | ||
| "McpCommand": { |
There was a problem hiding this comment.
🟠 Medium · Removing MCP schemas leaves the published API reference unresolved
McpServerConfig still references #/components/schemas/McpCommand, McpOAuthConfigOrDisabled, and McpRemoteTransport, so the 0.5.1 document retains three unresolved component references. Its generated schema page also still links to the deleted pages, causing the site’s internal-link check to fail. Keep these component definitions/pages, or inline/update every remaining reference as part of the generated sync.
39e0ba5 to
8c23425
Compare
| } | ||
| } | ||
| }, | ||
| "McpCommand": { |
There was a problem hiding this comment.
🟠 Medium · Removing MCP schemas leaves the published API reference unresolved
McpServerConfig still references #/components/schemas/McpCommand, McpOAuthConfigOrDisabled, and McpRemoteTransport, so the 0.5.1 document retains three unresolved component references. Its generated schema page also still links to the deleted pages, causing the site’s internal-link check to fail. Keep these component definitions/pages, or inline/update every remaining reference as part of the generated sync.
8c23425 to
73ef046
Compare
| } | ||
| } | ||
| }, | ||
| "McpCommand": { |
There was a problem hiding this comment.
🟠 Medium · Removing MCP schemas leaves the published API reference unresolved
McpServerConfig still references #/components/schemas/McpCommand, McpOAuthConfigOrDisabled, and McpRemoteTransport, so the 0.5.2 document retains three unresolved component references. Its generated schema page also still links to the deleted pages, causing the site’s internal-link check to fail. Keep these component definitions/pages, or inline/update every remaining reference as part of the generated sync.
![rivet-docs-sync[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
73ef046 to
de94076
Compare
| } | ||
| } | ||
| }, | ||
| "McpCommand": { |
There was a problem hiding this comment.
🟠 Medium · Removing MCP schemas leaves the published API reference unresolved
McpServerConfig still references #/components/schemas/McpCommand, McpOAuthConfigOrDisabled, and McpRemoteTransport, so the 0.5.2 document retains three unresolved component references. Its generated schema page also still links to the deleted pages, causing the site’s internal-link check to fail. Keep these component definitions/pages, or inline/update every remaining reference as part of the generated sync.
This branch was successfully deployed
1 participant
Automated docs sync from
rivet-dev/agents@420c726.Do not edit
vendor/sandbox-agent/here. Edit the docs inrivet-dev/agentsand this PR updates itself.