[wrangler] Fix email sending commands to use correct API endpoints#14240
Merged
Conversation
🦋 Changeset detectedLatest commit: 1765ba0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 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 |
Contributor
|
Codeowners approval required for this PR:
Show detailed file reviewers |
…ll, simplify changeset
petebacondarwin
requested changes
Jun 11, 2026
… use fetchListResult
petebacondarwin
approved these changes
Jun 11, 2026
workers-devprod
approved these changes
Jun 11, 2026
workers-devprod
left a comment
Contributor
There was a problem hiding this comment.
Codeowners reviews satisfied
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: |
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.
EMAIL-1854
Wrangler's
email sendingcommands targeted API endpoints that do not exist (e.g./zones/{id}/email/sending/enable,/zones/{id}/email/sending/disable,/zones/{id}/email/sending, and/zones/{id}/email/sending/dns), so they failed against the real API.Email Sending is managed through sending subdomains, so these commands now use the correct endpoints:
email sending enable <domain>creates a sending subdomain (POST /zones/{id}/email/sending/subdomains)email sending disable <domain>deletes the sending subdomain (DELETE /zones/{id}/email/sending/subdomains/{tag})email sending settings <domain>reads a single sending subdomain (GET /zones/{id}/email/sending/subdomains/{tag})email sending dns get <domain>always reads the subdomain's DNS records (GET /zones/{id}/email/sending/subdomains/{tag}/dns)email sending listnow lists sending subdomains: all subdomains across the account by default, or a single zone's subdomains when a domain or--zone-idis givenemail sendingcommands are in open beta and the user-facing command surface (arguments and output) is described via--help; this change corrects the underlying API endpoints so the existing commands work.