Repository navigation
ci(docs-mcp): deploy from Toolkit after main CI - #1664
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
betegon
force-pushed
the
ci/docs-mcp-deploy
branch
from
October 29, 2026 09:32
749216b to
9cb1859
Compare
betegon
marked this pull request as ready for review
October 29, 2026 09:32
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9cb1859. Configure here.
betegon
force-pushed
the
ci/docs-mcp-deploy
branch
from
October 29, 2026 09:53
9cb1859 to
77e8ac9
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Toolkit merges currently deploy only the main MCP Worker. Add
Deploy Docs MCPafter a successfulTestpush run for the currentmaincommit, following the main MCP's Node/pnpm setup, store cache, revision gates, and protectedproductionCloudflare credentials.The workflow uploads to the existing private
docs-mcpWorker without autocreating resources, activates the exact uploaded version, and waits for Cloudflare's deployment list to propagate before verifying its ownership and 100% traffic. The bounded wait reuses the main MCP'slistSettledhelper. Runtime variables and secrets are retained. The main MCP rollout is unchanged; its public HTTP smoke tests and recovery workflow do not apply to this private Worker.Validation passed after rebasing onto current
main: actionlint, 94 CI/helper tests, full lint, documentation links, and the actual shell revision guards. Replaying the workflow's real verification code reproduces the original stale-read failure, confirms retry success and bounded timeout, and rejects invalid ownership, version, or traffic. No Cloudflare API calls were made during these checks.Before merging: disconnect the old
cli-init-apiWorkers Builds connection and let any in-flight build finish, so Init cannot overwrite Toolkit's deployment. The first production deployment still needs a functional check through the private service binding. No deployment was executed while preparing this PR.