Graduate autoconfig from experimental to stable#14276
Conversation
🦋 Changeset detectedLatest commit: 8217a04 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
That's just a leftover inconsistency (one test still passes My review is complete. The change is a clean, well-tested flag rename/graduation. The only substantive consideration is backward compatibility for the removed experimental flags, but:
This is intentional and acceptable. There are no logic bugs, security issues, or incorrect API behaviors. The tests are updated consistently, the metrics allow-list key is correctly renamed, and the open-next delegation correctly forwards verbatim args. LGTM |
|
✅ All changesets look good |
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
|
Codeowners approval required for this PR:
Show detailed file reviewers |
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
Autoconfig has been turned on by default for a long time now and it was supposed to be stabilized much sooner, in any case I am graduating it in this PR since I don't think that the feature needs to still be experimental.
Note: The programmatic API is still experimental though, I think this will be useful as it will allow us to extract those function in their own package without neither being a breaking change for wrangler or forcing wrangler to re-export them.
A picture of a cute animal (not mandatory, but encouraged)