You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Workers] Announce Request.signal default on November 17 - #34424
Announce that incoming Request.signal abort events become the default for compatibility dates on or after November 17, 2026. Update the compatibility-flag metadata and Request reference, and add an October 17 advance changelog with a cancellation example and guidance for opting in early or opting out. request_signal_passthrough is unchanged.
Companion runtime PR: cloudflare/workerd#7798. 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.
Validation: Astro and Worker type checks, changelog Prettier formatting, and git diff --check pass. Full-site builds were not completed locally.
@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 /draft-never-stale to keep it open.
irvinebroque
changed the title
[Workers] Announce Request.signal default on November 1
[Workers] Announce Request.signal default on November 8
Oct 23, 2026
@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 /draft-never-stale to keep it open.
irvinebroque
changed the title
[Workers] Announce Request.signal default on November 8
[Workers] Announce Request.signal default on November 12
Oct 30, 2026
irvinebroque
changed the title
[Workers] Announce Request.signal default on November 12
[Workers] Announce Request.signal default on November 17
Oct 31, 2026
Fix the following review findings in PR #34424 (https://github.com/cloudflare/cloudflare-docs/pull/34424).
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-0f153426 | src/content/docs/workers/runtime-apis/request.mdx:268 | Month name and four-digit year in prose outside changelog
The added prose contains the month name `November` and the four-digit year `2026` in `November 17, 2026`. The time-sensitive content rules apply to this file (it is outside `src/content/changelog/`), and the exceptions do not cover this line: it is body prose, not a code block, backtick span, frontmatter field, URL, or example data. Month references and years must be removed or rewritten so the reference reads as timeless.
Style Guide
src/content/docs/workers/runtime-apis/request.mdx:268 · Month name and four-digit year in prose outside changelog
The added prose contains the month name November and the four-digit year 2026 in November 17, 2026. The time-sensitive content rules apply to this file (it is outside src/content/changelog/), and the exceptions do not cover this line: it is body prose, not a code block, backtick span, frontmatter field, URL, or example data. Month references and years must be removed or rewritten so the reference reads as timeless.
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
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 incoming
Request.signalabort events become the default for compatibility dates on or after November 17, 2026. Update the compatibility-flag metadata and Request reference, and add an October 17 advance changelog with a cancellation example and guidance for opting in early or opting out.request_signal_passthroughis unchanged.Companion runtime PR: cloudflare/workerd#7798. 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.
Validation: Astro and Worker type checks, changelog Prettier formatting, and
git diff --checkpass. Full-site builds were not completed locally.Documentation checklist