[wrangler] Add top-level addresses config field for Email Routing - #14470
Merged
Conversation
🦋 Changeset detectedLatest commit: 0ac6690 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 |
This was referenced Jun 29, 2026
DiogoSantoss
force-pushed
the
dsantos/EMAIL-1880
branch
3 times, most recently
from
June 30, 2026 10:36
f016d6d to
a7e1830
Compare
DiogoSantoss
marked this pull request as ready for review
June 30, 2026 10:54
workers-devprod
requested review from
a team and
NuroDev
and removed request for
a team
June 30, 2026 10:54
Contributor
|
Codeowners approval required for this PR:
Show detailed file reviewers |
NuroDev
requested changes
Jul 2, 2026
@cloudflare/autoconfig
@cloudflare/config
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: |
DiogoSantoss
force-pushed
the
dsantos/EMAIL-1880
branch
from
July 3, 2026 14:11
1401089 to
3194924
Compare
NuroDev
approved these changes
Jul 3, 2026
workers-devprod
approved these changes
Jul 3, 2026
workers-devprod
left a comment
Contributor
There was a problem hiding this comment.
Codeowners reviews satisfied
DiogoSantoss
force-pushed
the
dsantos/EMAIL-1880
branch
from
July 14, 2026 21:57
3194924 to
ea37296
Compare
Contributor
|
Codeowners approval required for this PR:
Show detailed file reviewers |
DiogoSantoss
force-pushed
the
dsantos/EMAIL-1880
branch
from
July 15, 2026 08:32
ea37296 to
ec39336
Compare
added 2 commits
July 15, 2026 09:46
EMAIL-1880: parse and validate the new top-level `addresses` field in wrangler config (literal recipients or `*@domain` catch-alls). It is top-level only (cannot be set under `env.*`), validated locally (array of non-empty strings, no exact duplicates), and printed on `wrangler deploy --dry-run` without any network calls. Applying the addresses during deploy follows in EMAIL-1882.
DiogoSantoss
force-pushed
the
dsantos/EMAIL-1880
branch
from
July 15, 2026 08:46
ec39336 to
827abcf
Compare
Merged
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.
Adds a top-level
addressesfield to Wrangler configuration for Email Routing.You can declare the inbound email addresses handled by a Worker directly in
wrangler.json:{ "name": "my-worker", "main": "src/index.ts", "compatibility_date": "2026-05-21", "addresses": ["support@example.com", "*@example.com"] }Each entry is a literal recipient address or a
*@domaincatch-all.addressesis top-level only (it applies to every environment and cannot be set underenv.*) and is validated locally (array of non-empty strings, no exact duplicates).wrangler deploy --dry-runvalidates the field and prints the resolved set without any network calls. Applying the addresses duringwrangler deployfollows in a stacked PR.Internal tracking: EMAIL-1880 / RM-29262.
wrangler.jsonfeature (separate ticket); this PR is config parsing/validation only.🐱