Repository navigation
[docs] List the Cloudflare World under Managed - #4618
Conversation
The worlds index buckets each World into Managed, Self-Hosted, or Embedded. Managed is an explicit allowlist and Self-Hosted is the fallback, so the Cloudflare World was showing under Self-Hosted. Cloudflare Durable Objects is a managed platform — you deploy to it rather than run it yourself (the World is flagged `requiresDeployment` in worlds-manifest.json, same as Vercel), so add it to `managedIds`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
|
Sim WorldSimulated world deterministic testing for races. Traces 🟠 world-sim scenario book — 1 fail of 42 total
Full trace: |
VaguelySerious
left a comment
There was a problem hiding this comment.
Cloudflare does not declare the encryption feature in worlds-manifest.json (Vercel does), so "e2e encrypted" no longer holds for every World in this section. I left the copy alone since the ask was scoped to the move
Reword would be good
The Managed blurb listed "e2e encrypted" alongside the attributes every World in the section shares, which stopped being true once Cloudflare joined it: Cloudflare does not declare the `encryption` feature in worlds-manifest.json, only Vercel does. Each card already renders a visible "Encrypted" badge for Worlds that declare the feature, and the filter chip uses the same label, so point at that marker instead of dropping the claim. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
|
@VaguelySerious reworded in 40771f3. -'Production grade — zero configuration, high throughput, infinitely-scalable, e2e encrypted, and integrated observability'
+'Production grade — zero configuration, high throughput, infinitely-scalable, and integrated observability, plus end-to-end encryption on Worlds marked Encrypted'Rather than just dropping the claim, I scoped it to the marker that already exists: Went with the copy change over adding |
|
No backport to The only changed file is To override, re-run the Backport to stable workflow manually via |
Catches the docs up with SDK changes that landed on Oct 5 without (complete) docs updates. | Change | Source PR | Docs edit | | --- | --- | --- | | zstd is only written to runs whose deployment's Node.js can decode it | #4640 | The encryption page said "gzip, with zstd support in the format". It now states when zstd vs. gzip is used and links `WORKFLOW_COMPRESSION_CODEC` | | Aborting a public writable keeps the accepted prefix and doesn't close the shared stream | #4605 | Added to the existing `releaseLock()` / `close()` callout in Streaming | | Released stream writers retire their WebSocket and continue over HTTP | #4605 | Short paragraph under `WORKFLOW_STREAMS_TRANSPORT` on the Vercel World page, including the "hold the lock for a burst" tip from the `world-vercel` README | I reviewed the other Oct 5 PRs and they need no further docs: NestJS (#4604) shipped its own docs, the `@vercel/queue` bump (#4648) and `world-local` hook fix (#4636) aren't user-facing in the docs, and #4632/#4618 are docs PRs. The Workflows pages in `vercel/front` were also checked and need no changes for these. ## Docs Preview | Page | Preview | | --- | --- | | Encryption | [Compression](https://workflow-docs-git-workflow-docs-cleanup-tue-6-oct.vercel.sh/docs/how-it-works/encryption#compression) | | Streaming | [Writing to another run's stream](https://workflow-docs-git-workflow-docs-cleanup-tue-6-oct.vercel.sh/docs/foundations/streaming#writing-to-another-runs-stream) | | Vercel World | [`WORKFLOW_STREAMS_TRANSPORT`](https://workflow-docs-git-workflow-docs-cleanup-tue-6-oct.vercel.sh/worlds/vercel#workflow_streams_transport) | 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
Moves the Cloudflare World listing on the Worlds index out of Self-Hosted and into Managed, as requested in Slack.
Why it was in the wrong bucket
WorldsFilteredGridsorts Worlds into three sections using two allowlists, with Self-Hosted as the catch-all:Because
managedIdsonly containedvercel, the Cloudflare World fell through to Self-Hosted by default. Cloudflare Durable Objects is a managed platform — you deploy onto it rather than run it yourself — and the World is flaggedrequiresDeployment: trueinworlds-manifest.json, the same as the Vercel World. So the fix is to add it to the allowlist.The change
Resulting sections
Cloudflare sorts after Vercel in Managed, following manifest order. The filter chips (Show all / By Vercel / By Community / Encrypted) are independent of sectioning and are unaffected — Cloudflare still counts as a community World.
Managed section copy
The Managed blurb listed
e2e encryptedamong the attributes every World in the section shares, which stopped holding once Cloudflare joined it — Cloudflare does not declare theencryptionfeature inworlds-manifest.json, only Vercel does. Reworded per review:Scoped to the marker already on the page rather than deleted:
WorldCardSimplerenders a visibleEncryptedbadge for any World declaring the feature, and the filter chip uses the same word. That keeps the claim accurate as Worlds gain the feature, without the blurb needing another edit.Testing
worlds-manifest.jsonto confirm the bucketing above.biome checkpasses on the modified file.🤖 Generated with Claude Code