Conversation
dcramer
commented
Sep 8, 2025
dcramer
commented
- Update Cloudflare docs: deployment and overview
- Add turbo config for mcp-cloudflare
- Update wrangler and vite configs
- Adjust Cloudflare server types and index
- Update MCP prompts and resources definitions
- Refresh deploy and smoke-test workflows
- Update package manifests and lockfile
- Add docs package scaffold
- Update smoke tests
…ions - Update Cloudflare docs: deployment and overview - Add turbo config for mcp-cloudflare - Update wrangler and vite configs - Adjust Cloudflare server types and index - Update MCP prompts and resources definitions - Refresh deploy and smoke-test workflows - Update package manifests and lockfile - Add docs package scaffold - Update smoke tests Co-Authored-By: Codex CLI Agent <noreply@openai.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
|
im not convinced this is the simplest path forward. I took this prototype much farther and honestly it gets super complex. hyp[othetically it makes a lot of sense to abstract things into diff workers, but in this case, for example, we probably would want ALL UI (at minimum) to be in one worker. we could easily abstract the mcp service into its own worker, which actually would be of some value, but even that creates a bunch of packaging complexity. i will probably hold on this and reconsider later. |
| if [ "$STATUS" -ne 200 ]; then | ||
| echo "Unexpected status: $STATUS"; cat /tmp/docs_canary.html; exit 1; fi | ||
| if ! grep -q "<title>Documentation" /tmp/docs_canary.html; then | ||
| echo "Title check failed"; cat /tmp/docs_canary.html; exit 1; fi |
There was a problem hiding this comment.
Bug: HTML Title Mismatch Blocks Deployments
The docs worker's HTML title in packages/docs/client/index.html is <title>Sentry MCP Docs</title>. However, the deploy workflow and smoke tests expect <title>Documentation. This mismatch causes docs canary and production smoke tests to fail, blocking deployments and triggering rollbacks.
Additional Locations (2)
| "dev": { | ||
| "port": 8791 | ||
| } | ||
| } |
There was a problem hiding this comment.
Bug: Canary Deployment Fails Due to Missing Assets Binding
The wrangler.canary.jsonc configuration is missing the assets binding. The docs worker relies on c.env.ASSETS.fetch() for static assets, which will be undefined. This prevents the canary deployment from serving content properly.
1 participant
