Expose compatibility-date.capnp and add AGENTS.md guidance for new APIs - #7274
Merged
Conversation
Contributor
|
LGTM |
git-bruh
approved these changes
Sep 8, 2026
jasnell
reviewed
Sep 8, 2026
jasnell
reviewed
Sep 8, 2026
jasnell
reviewed
Sep 8, 2026
fhanau
reviewed
Sep 8, 2026
fhanau
approved these changes
Sep 8, 2026
jasnell
approved these changes
Sep 8, 2026
harrishancock
force-pushed
the
harris/EW-10964-snapshot-global-scope
branch
from
September 8, 2026 16:29
99d44e2 to
9b15a33
Compare
|
The generated output of |
The global-scope snapshot needs flag names, including flags with no enable date. Export the schema source so a text-based build rule can read those names without a compiled helper. Assisted-by: Codex:gpt-6
A new global can switch existing Workers from a polyfill to the runtime implementation without any action by their authors. Require an explicit compatibility decision for API enablements, including those caused by V8 flags or upstream defaults. Assisted-by: Codex:gpt-6
harrishancock
force-pushed
the
harris/EW-10964-snapshot-global-scope
branch
from
September 8, 2026 16:58
9b15a33 to
3e8e74b
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7274 +/- ##
==========================================
- Coverage 37.56% 37.33% -0.24%
==========================================
Files 801 801
Lines 253637 251822 -1815
Branches 20021 20021
==========================================
- Hits 95286 94011 -1275
+ Misses 146993 146453 -540
Partials 11358 11358 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
5 participants
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.
The intent here is to prevent a recurrence of #6907.
An internal test will surface new APIs for compatibility review, with either a compatibility flag or explicit risk acceptance as valid outcomes. In order to write that test, we need to expose compatibility-date.capnp, so we can easily enumerate every existing non-experimental compatibility flag. We can't just use future compatibility dates to "enable everything", because many flags have no enable-date, and we want to guarantee their API stability, too.