Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 3d4c750 The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 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 |
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-google-signin
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
jescalan
force-pushed
the
je/remove-postmark
branch
from
August 28, 2026 14:52
c4792b7 to
3d4c750
Compare
This branch was successfully deployed
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.
Summary
Follow-up to the Postmark send-path removal (clerk_go#21398). That PR deleted the behavior; this one deletes the field.
The setting no longer affects anything: routing, unverified-DNS suppression, template forcing, and the magic-link validator were all removed, and every remaining instance was flipped to
falsein production on 2026-08-26 (20 production + 14 development). What is left is an inert boolean on the API surface, plus dead config.Rollout ordering
Only one ordering constraint remains:
enhanced_email_deliverability, and the dashboard reads it today for the email-logs banner. The failure mode is soft — the value would just read asundefinedand the banner would hide — but shipping the consumer first avoids a window where the dashboard reads a field the API no longer returns.Everything else is independent and can land in any order: backoffice#724 is type-only with no reader, terraform-app-infra#3193 removes config nothing reads (the cenv constants went out with #21398), clk#49 is documentation, and the SDK PRs land on their owners' release cadence.
No released API contract changes. An earlier revision of clerk_go#21613 removed the field from the base FAPI
Clientschema — which is inherited by all six API versions, so it would have dropped arequiredfield from five stable versions that clients pin to. FAPI and BAPI now keep serializing it asfalseinstead.Still outstanding after this
The
ENHANCED_DELIVERABILITY_POSTMARK_SERVER_TOKENsecrets remain in four SOPS-encrypted files (production and staging,api_commonandpubsubworker). They need someone with sops keys. The Postmark account itself also still needs decommissioning.Changes in this repo
Removes the retired
enhancedEmailDeliverabilitysetting from@clerk/backend: theInstanceApi.updateInstanceparam, theInstanceSettingsresource, and its JSON type. The param has been a server-side no-op since the delivery path was retired, and the Backend API now ignores it entirely.Breaking change to a public type, so a major changeset is included. Flagged as draft for the SDK owners to slot into their release cadence - no rush, the server tolerates clients that still send the field.
Companion PRs