[Docs Site] Update pinned api-schemas commit#2
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
…159af2f933527465f72
Author
|
Hey there, we've marked this pull request as stale because there's no recent activity on it. This label is helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant). |
cf-rhett
pushed a commit
that referenced
this pull request
Apr 6, 2026
…e#28501) * Migrate Agents docs to Workers AI examples Replace OpenAI-specific examples with Workers AI / AI SDK usage across Agents docs. Examples now use an Env AI binding, createWorkersAI / workers-ai-provider, and streamText/generateText from the ai SDK instead of direct OpenAI clients or API keys. Updated WebSocket/SSE streaming, long-running model examples, and SQL/state persistence to consume this.env.AI.run streams/responses. Updated Wrangler/config mentions to use the ai binding and clarified AI Gateway/model routing guidance. Files changed: browse-the-web.mdx, http-sse.mdx, store-and-sync-state.mdx, using-ai-models.mdx, index.mdx. * formatting * docs: clarify Agent class and add LLM patterns Revise agent-class.mdx to clarify the Agent/Server/DurableObject layering, tighten wording, fix small code snippets (ws.send, storage access, Response usage), standardize PartyKit/Server references, and add a new Layer 3 section describing AIChatAgent. Replace calling-llms.mdx with a complete rewrite that focuses on using LLMs inside stateful Agents: explains state-as-context, surviving disconnections, autonomous model calls, multi-model pipelines, and caching; adds multiple TypeScript examples and Next Steps link cards, and updates the page tag to "AI". * docs: fix MCP docs bugs and inconsistencies - authorization.mdx: remove orphaned <diagram> tag, fix broken anchor (#3 -> #2), fix "oAuth" -> "OAuth", add pcx_content_type, rewrite permission code to use correct MCP tool handler signature, replace MyMCPServer.Router with .serve(), remove unused DirectoryListing import - mcp-client-api.mdx: fix this.env bug in createMcpOAuthProvider (capture env before returning object literal), fix import path for error utils, remove dead code after return, replace OpenAI example with Workers AI - mcp-handler-api.mdx: fix misleading intro (stateless vs stateful, not SSE), fix storage.kv -> storage.get/put, fix {} as ExecutionContext, wrap global McpServer in factory function, fix "accessable" typo - remote-mcp-server.mdx: fix MyMCP.Router -> .serve(), fix Auth0/WorkOS anchors pointing to #stytch, fix https://localhost -> http://localhost, fix broken MCP client link - securing-mcp-server.mdx: fix apiHandlers -> apiRoute + apiHandler - test-remote-mcp-server.mdx: fix https -> http localhost, fix "lets you to test" typo, remove outdated claim about Claude Desktop - tools.mdx: add missing tags, add .js extension to import, remove unused Render import, fix stale repo link - governance.mdx: add pcx_content_type, remove empty import - index.mdx: fix http -> https links for Claude and Cursor - mcp-servers-for-cloudflare.mdx: fix "streamble-http" typo, remove unused Render import, fix link to source code -> docs - transport.mdx: remove unused Render/TabItem/Tabs imports - oauth-mcp-client.mdx: fix extends Agent -> Agent<Env> (5 instances) - connect-mcp-client.mdx: fix extends Agent -> Agent<Env> (3 instances) Co-authored-by: Cursor <cursoragent@cursor.com> * docs: rewrite MCP tools page, fix handler and authorization docs tools.mdx: Full rewrite from 36-line stub to comprehensive reference. Covers tool definitions, results, error handling, descriptions best practices, Zod input validation, and usage with both createMcpHandler and McpAgent. All examples use the factory function pattern. mcp-handler-api.mdx: Add missing State type definition in stateful example, fix onMcpRequest -> onRequest in Worker handler, remove unused Render import. authorization.mdx: Rewrite bottom half to show auth context usage for both McpAgent (this.props) and createMcpHandler (getMcpAuthContext), with proper type definitions. Clarify the two permission approaches (check inside handler vs conditional registration) and when to use each. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
cf-rhett
pushed a commit
that referenced
this pull request
Apr 6, 2026
…shooting (cloudflare#28780) * [Registrar] Rewrite transfer page and add registration limits troubleshooting Restructure the transfer-domain-to-cloudflare page into two clear phases (add domain to Cloudflare, then transfer registration) instead of the previous flat 10-step list. Inline partials, add DNSSEC/nameserver provider links, explain why each step is needed, and add registration limits content with actionable guidance. Add new troubleshooting section for transfers rejected due to registration period limits (10-year max for most TLDs, 5-year for .co). Clarify vague language throughout: specific WHOIS status explanations, concrete 45-day expiration rule, ICANN contact-change lock details. * [Registrar] Simplify transfer timeline language in opening paragraph * [Registrar] Address PR review feedback and restore grace period transfer scenario - Break opening paragraph into scannable bullet list (#1) - Lead with action instead of comparison to other registrars (#2) - Replace IDN jargon with plain language and example (#3) - Lead with actionable advice in Restrictions block (#5) - Cross-link 'active on Cloudflare' to full-setup docs (#6) - Replace inlined DNSSEC links with dnssec-providers partial (#7) - Slim 'Add your domain' section to cross-link full-setup page (#8) - Reorder unlock section to put action before context (#9) - Restore 45-day grace period scenario with concrete date example and ICANN refund entitlement, matching FAQ content (#10) * [Registrar] Simplify transfer page, move details to troubleshooting - Simplify opening: shorter total time bullet, one-line prereq - Move Restrictions block content to troubleshooting page - Move registration limits and 'domain not available' Details blocks to troubleshooting page as standalone sections with full examples - Add 45-day grace period note in Before you begin with FAQ link - Update TLD page to link to troubleshooting instead of removed anchor - Simplify approve-transfer section for non-technical audience - Convert caution to note for Active status requirement - Make authoritative DNS requirement a bullet in Before you begin - Remove redundant 'Go to Transfer Domains page' text (DashButton CTA) * [Registrar] Restore auth code callout in opening note block
cf-rhett
pushed a commit
that referenced
this pull request
Apr 6, 2026
* [Registrar] Rewrite transfer page and add registration limits troubleshooting Restructure the transfer-domain-to-cloudflare page into two clear phases (add domain to Cloudflare, then transfer registration) instead of the previous flat 10-step list. Inline partials, add DNSSEC/nameserver provider links, explain why each step is needed, and add registration limits content with actionable guidance. Add new troubleshooting section for transfers rejected due to registration period limits (10-year max for most TLDs, 5-year for .co). Clarify vague language throughout: specific WHOIS status explanations, concrete 45-day expiration rule, ICANN contact-change lock details. * [Registrar] Simplify transfer timeline language in opening paragraph * [Registrar] Address PR review feedback and restore grace period transfer scenario - Break opening paragraph into scannable bullet list (#1) - Lead with action instead of comparison to other registrars (#2) - Replace IDN jargon with plain language and example (#3) - Lead with actionable advice in Restrictions block (#5) - Cross-link 'active on Cloudflare' to full-setup docs (#6) - Replace inlined DNSSEC links with dnssec-providers partial (#7) - Slim 'Add your domain' section to cross-link full-setup page (#8) - Reorder unlock section to put action before context (#9) - Restore 45-day grace period scenario with concrete date example and ICANN refund entitlement, matching FAQ content (#10) * [Registrar] Simplify transfer page, move details to troubleshooting - Simplify opening: shorter total time bullet, one-line prereq - Move Restrictions block content to troubleshooting page - Move registration limits and 'domain not available' Details blocks to troubleshooting page as standalone sections with full examples - Add 45-day grace period note in Before you begin with FAQ link - Update TLD page to link to troubleshooting instead of removed anchor - Simplify approve-transfer section for non-technical audience - Convert caution to note for Active status requirement - Make authoritative DNS requirement a bullet in Before you begin - Remove redundant 'Go to Transfer Domains page' text (DashButton CTA) * [Registrar] Restore auth code callout in opening note block * [Registrar] Address review feedback on auth codes, GoDaddy proxy, and ccTLD transfer pricing * [Registrar] Replace unverified GoDaddy domain forwarding claim with accurate transfer guidance * [Registrar] Simplify 45-day transfer registration language and move detail to FAQ * [Registrar] Address review feedback: restore notes and add email verification section
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.
This PR updates the api-schemas commit reference to the latest version (6b852f9040e6f578aa91b159af2f933527465f72).