Skip to content

Update recently added compatibility flags - #29683

Merged
jasnell merged 1 commit into
cloudflare:productionfrom
jasnell:jasnell/update-compat-flag-docs
Apr 22, 2026
Merged

Update recently added compatibility flags#29683
jasnell merged 1 commit into
cloudflare:productionfrom
jasnell:jasnell/update-compat-flag-docs

Conversation

@jasnell

@jasnell jasnell commented Apr 7, 2026

Copy link
Copy Markdown
Contributor

Adding multiple workerd compat flags

@jasnell
jasnell requested a review from a team April 7, 2026 23:10
@github-actions github-actions Bot added the size/l label Apr 7, 2026
@jasnell
jasnell force-pushed the jasnell/update-compat-flag-docs branch from 2265df1 to 0ea6cad Compare April 8, 2026 02:45

@harrishancock harrishancock left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some nitpicky comments, but I don't think we should block on them -- we should get this merged and followup on anything important.

Comment thread src/content/compatibility-flags/websocket-standard-binary-type.md Outdated
@jasnell
jasnell force-pushed the jasnell/update-compat-flag-docs branch from 0ea6cad to 2384294 Compare April 21, 2026 17:40
@jasnell

jasnell commented Apr 21, 2026

Copy link
Copy Markdown
Contributor Author

Let's do the additional runtime API doc updates separately. Will need to collect more information on them

@jasnell
jasnell enabled auto-merge (squash) April 21, 2026 17:41
disable_flag: "disable_global_performance_classes"
---

When `enable_global_performance_classes` is enabled, the following classes are available on the global scope: `PerformanceEntry`, `PerformanceMark`, `PerformanceMeasure`, `PerformanceResourceTiming`, `PerformanceObserver`, and `PerformanceObserverEntryList`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we ever changelogged this? Can we?

@irvinebroque

Copy link
Copy Markdown
Contributor

/bonk

@jasnell
jasnell merged commit a7c899a into cloudflare:production Apr 22, 2026
10 checks passed

@ask-bonk ask-bonk Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Post-merge review. Found two content issues in remove-nodejs-compat-eol-v23.md that need follow-up fixes. Everything else looks correct.

disable_flag: "add_nodejs_compat_eol_v23"
---

When `remove_nodejs_compat_eol_v23` is enabled, APIs that reached end-of-life in Node.js 23.x (EOL June 2025) are removed.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Node.js 23.x reached EOL in May 2025, not June 2025.

Suggested change
When `remove_nodejs_compat_eol_v23` is enabled, APIs that reached end-of-life in Node.js 23.x (EOL June 2025) are removed.
When `remove_nodejs_compat_eol_v23` is enabled, APIs that reached end-of-life in Node.js 23.x (EOL May 2025) are removed.


When `remove_nodejs_compat_eol_v23` is enabled, APIs that reached end-of-life in Node.js 23.x (EOL June 2025) are removed.

This flag is automatically enabled when the `remove_nodejs_compat_eol_v24` flag is enabled after 2025-09-01.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy-paste error: this should reference the parent remove_nodejs_compat_eol flag, not the v24-specific flag.

Suggested change
This flag is automatically enabled when the `remove_nodejs_compat_eol_v24` flag is enabled after 2025-09-01.
This flag is automatically enabled when the `remove_nodejs_compat_eol` flag is enabled after 2025-09-01.

@ask-bonk

ask-bonk Bot commented Apr 22, 2026

Copy link
Copy Markdown
Contributor

Submitted a post-merge review on PR #29683.

Found 2 issues in remove-nodejs-compat-eol-v23.md:

  1. Line 14 — Node.js 23.x EOL date is incorrect. It reached EOL in May 2025, not June 2025.
  2. Line 16 — Copy-paste error referencing remove_nodejs_compat_eol_v24 instead of the parent remove_nodejs_compat_eol flag.

Posted both as inline suggestions in the review: Review link

The other 46 new compatibility flag files look correct — frontmatter is valid, links are well-formed, and technical descriptions are accurate.

github run

@github-actions
github-actions Bot deleted the jasnell/update-compat-flag-docs branch June 21, 2026 05:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants