Release packages - #2013
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
Reviews (1): Last reviewed commit: "Release packages" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 10, 2026 16:03
d5d835c to
b4f5ecc
Compare
Contributor
|
Reviews (2): Last reviewed commit: "Release packages" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 10, 2026 19:36
b4f5ecc to
9601ef6
Compare
Contributor
|
Reviews (3): Last reviewed commit: "Release packages" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 11, 2026 09:23
9601ef6 to
daea138
Compare
Contributor
|
Reviews (4): Last reviewed commit: "Release packages" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 13:49
daea138 to
2a089d2
Compare
Contributor
|
Reviews (5): Last reviewed commit: "Release packages" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 13:52
2a089d2 to
84405f6
Compare
Contributor
|
Reviews (6): Last reviewed commit: "Release packages" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 12:59
84405f6 to
0cf87e8
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 21:27
0cf87e8 to
2ae41ee
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@crossmint/client-sdk-base@2.8.0
Minor Changes
cfa9710: Added
identityVerificationHandlingto embedded checkout on web. Setting it to"external"stops checkout from rendering the identity verification step, so a merchant can renderCrossmintIdentityVerificationin their own layout usinggetIdentityVerificationCredentials(order).Requires a Crossmint deployment that understands the flag. Against an older one it is ignored, and checkout renders the verification step alongside the merchant's, both against the same inquiry.
a8b6b60:
identityVerificationHandlingis now accepted by React Native embedded checkout, not web only. Setting it to"external"stops checkout from rendering the identity verification step, so you can renderCrossmintIdentityVerificationin your own screen usinggetIdentityVerificationCredentials(order).Patch Changes
@crossmint/client-sdk-react-native-ui@1.6.0
Minor Changes
identityVerificationHandlingis now accepted by React Native embedded checkout, not web only. Setting it to"external"stops checkout from rendering the identity verification step, so you can renderCrossmintIdentityVerificationin your own screen usinggetIdentityVerificationCredentials(order).CrossmintIdentityVerificationto the React Native SDK. It renders Crossmint's hosted identity verification step in a WebView from an order'spayment.preparation.kyccredentials, and reportsonReady,onComplete,onCancelandonError.useIdentityVerificationCredentialshook, so a merchant taking the identity verification step over withidentityVerificationHandling="external"reads the credentials in one line instead of plumbing the order throughgetIdentityVerificationCredentials. The plain function stays exported for orders that do not come from checkout context.Patch Changes
13584ba: The signer OTP field now submits from the keyboard's done key.
BaseCodeInputonly accepted the code via the Submit button, which sits below the field and therefore behind the keyboard the field just opened. Entering a code meant dismissing the keyboard first — and dismissing it reflows the dialog, moving the button that was the only way to continue.returnKeyType="done"withonSubmitEditingsubmits in place, from where the user already is. The Submit button is unchanged.Updated dependencies [cfa9710]
Updated dependencies [3528a4e]
Updated dependencies [a8b6b60]
Updated dependencies [de7771e]
@crossmint/client-sdk-react-ui@4.5.0
Minor Changes
cfa9710: Added
identityVerificationHandlingto embedded checkout on web. Setting it to"external"stops checkout from rendering the identity verification step, so a merchant can renderCrossmintIdentityVerificationin their own layout usinggetIdentityVerificationCredentials(order).Requires a Crossmint deployment that understands the flag. Against an older one it is ignored, and checkout renders the verification step alongside the merchant's, both against the same inquiry.
a8b6b60: Added a
useIdentityVerificationCredentialshook, so a merchant taking the identity verification step over withidentityVerificationHandling="external"reads the credentials in one line instead of plumbing the order throughgetIdentityVerificationCredentials. The plain function stays exported for orders that do not come from checkout context.Patch Changes
cfa9710:
WindowTransportnow matchesevent.sourceagainst the peer window instead of trusting the origin alone.Each client subscribes to the global
messageevent and accepted anything arriving from a matching origin. With one Crossmint iframe per page, no other frame could send from that origin, so the gap stayed invisible. Put two on a page and each client receives the other's events.Embedded checkout with
identityVerificationHandling="external"puts two on the page. The verification iframe sendsui:height.changedat 660, the checkout iframe takes that height after collapsing to 0, and the merchant gets 660px of empty space above their widget. Reverse the order and checkout's 0 reaches the verification iframe and hides the Persona form.A message whose sending window has closed carries a null source. The transport drops it.
OAuth login moves its listeners onto the popup it opens. They used to sit on a
ChildWindowbuilt overwindow.opener || window.parent, which on a merchant's top-level page resolves to that page's own window, so the peer never matched the popup the callback arrives from. That client only ever listened, never sent, so the mismatch was invisible until the peer became part of the receive path. Attaching to the popup also unsubscribes correctly between attempts, where the previousoff(eventName)calls passed an event name to an API that takes a listener id and silently did nothing.Updated dependencies [cfa9710]
Updated dependencies [7d99607]
Updated dependencies [3528a4e]
Updated dependencies [a8b6b60]
Updated dependencies [de7771e]
Updated dependencies [cfa9710]
@crossmint/client-sdk-auth@1.3.19
Patch Changes
@crossmint/client-sdk-react-base@2.2.4
Patch Changes
Crossmint does not work in the following countries and regions) to theregion-blockederror code inuseWallet, instead of treating it asunknown.@crossmint/client-sdk-rn-window@0.3.18
Patch Changes
@crossmint/client-sdk-verifiable-credentials@3.4.96
Patch Changes
@crossmint/client-sdk-smart-wallet@0.3.71
Patch Changes
@crossmint/client-sdk-window@1.1.1
Patch Changes
7d99607:
EventEmitterno longer logsconsole.errorfor a timeout it hands back to the caller as a rejection.sendActionandonActionreject on timeout, andsendActionalso rejects once it exhaustsmaxRetries. Each of those rejections was preceded by aconsole.error, so a caller that catches the rejection and recovers still left an error behind. Only the caller knows whether a timeout is fatal —CrossmintWalletProviderretries the WebView handshake twice and logshandshake.erroritself if those run out.On React Native the duplicate is not just noise.
console.errorraises a LogBox notification, which renders on top of the app: a handshake that timed out at 30s and succeeded on retry 16s later left a toast covering the bottom of the screen, over the app's own controls.cfa9710:
WindowTransportnow matchesevent.sourceagainst the peer window instead of trusting the origin alone.Each client subscribes to the global
messageevent and accepted anything arriving from a matching origin. With one Crossmint iframe per page, no other frame could send from that origin, so the gap stayed invisible. Put two on a page and each client receives the other's events.Embedded checkout with
identityVerificationHandling="external"puts two on the page. The verification iframe sendsui:height.changedat 660, the checkout iframe takes that height after collapsing to 0, and the merchant gets 660px of empty space above their widget. Reverse the order and checkout's 0 reaches the verification iframe and hides the Persona form.A message whose sending window has closed carries a null source. The transport drops it.
OAuth login moves its listeners onto the popup it opens. They used to sit on a
ChildWindowbuilt overwindow.opener || window.parent, which on a merchant's top-level page resolves to that page's own window, so the peer never matched the popup the callback arrives from. That client only ever listened, never sent, so the mismatch was invisible until the peer became part of the receive path. Attaching to the popup also unsubscribes correctly between attempts, where the previousoff(eventName)calls passed an event name to an API that takes a listener id and silently did nothing.@crossmint/common-sdk-auth@1.1.17
Patch Changes
@crossmint/server-sdk@1.2.81
Patch Changes
@crossmint/wallets-sdk@1.12.1
Patch Changes
wallet.isSignerApprovednow throws when the signer state cannot be fetched instead of resolving tofalse, so callers can tell a failed request apart from a signer that is not approved. A signer that is not registered still resolves tofalse. This matches the behavior of the Swift and Kotlin SDKs.@crossmint/auth-ssr-nextjs-demo@0.4.193
Patch Changes
crossmint-auth-node@1.1.92
Patch Changes
@crossmint/client-sdk-nextjs-starter@2.0.43
Patch Changes
@crossmint/wallets-playground-expo@0.0.29
Patch Changes
@crossmint/wallets-quickstart-devkit@0.2.63
Patch Changes
@crossmint/wallets-playground-react@0.0.26
Patch Changes