Repository navigation
[Workers] Announce module registry default on November 17 - #34425
Merged
Merged
Conversation
github-actions
Bot
added
product:workers
Contributor
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://codex-module-registry-default-docs.previews.developers.cloudflare.com (commit c25942a)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Contributor
|
@irvinebroque This draft pull request has had no activity for 3 days. It will close after 7 days of inactivity. Transition to ready for review if ready. A codeowner can comment |
irvinebroque
changed the title
Contributor
|
@irvinebroque This draft pull request has had no activity for 3 days. It will close after 7 days of inactivity. Transition to ready for review if ready. A codeowner can comment |
irvinebroque
changed the title
irvinebroque
changed the title
irvinebroque
marked this pull request as ready for review
October 31, 2026 20:02
irvinebroque
requested review from
a team,
GregBrimble,
MattieTK,
WalshyDev,
korinne and
vy-ton
as code owners
October 31, 2026 20:02
Contributor
AI Review✅ Reviewed 👉 Fix in your agent 👈Fix the following review findings in PR #34425 (https://github.com/cloudflare/cloudflare-docs/pull/34425).
Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification.
- If you disagree, explain why.
- If you need clarification before deciding, ask those questions.
- Then share your plan for which issues to tackle and in what order.
After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.
The comment must come before the commit because the next review reads PR comments.
## Style Guide
- S-1e4fdef2 | src/content/docs/workers/wrangler/bundling.mdx:30 | Time-sensitive month and year in prose
Per the time-sensitive content rule, prose outside `src/content/changelog/` must not contain month names or four-digit years. `November 17, 2026` appears in plain prose here (not in a code block, backtick span, frontmatter field, URL, or example data).Style Guide
Commands
|
dinasaur404
approved these changes
Nov 2, 2026
irvinebroque
enabled auto-merge
November 2, 2026 17:39
Contributor
Author
|
@jasnell I am merging docs change that announces Nov 17th, so that this can land |
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.
Announce that the new JavaScript module registry becomes the default for compatibility dates on or after November 17, 2026. Add compatibility-flag documentation and migration guidance, update the bundling reference, and add a November 2 advance changelog with an
import.metaexample and guidance for opting in early or retaining the legacy registry. Python Workers retain the legacy registry.Companion runtime PR: cloudflare/workerd#7799. Publish the documentation before November 17 so developers can test ahead of the default change. The changelog date is the announcement date; the compatibility boundary is November 17. Migration guidance covers import-attribute validation,
require(esm)return values, top-levelawait, and legacy-registry-only flags.Validation: Astro and Worker type checks, changelog Prettier formatting, and
git diff --checkpass. Full-site builds were not completed locally.Documentation checklist