Repository navigation
Release packages - #2288
Merged
Merged
Release packages#2288
Conversation
Contributor
[High impact] This release PR appears safe to merge. Reviews (2) · Last reviewed commit: "Release packages" · Reviewed by Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 6, 2026 02:26
22156cb to
dc5e426
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 6, 2026 13:32
dc5e426 to
eb29a2f
Compare
manu-xmint
approved these changes
Nov 6, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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@5.0.0
Major Changes
a55b5e4: BREAKING:
CrossmintPaymentMethodManagementno longer renders a built-in submit button. ThehideSubmitButtonprop is removed — the component always asks the host to submit viaref.submit(), which must be wired to your own button. The iframe no longer draws the message of aninvalidorfailedsubmit: show themessagethatref.submit()returns. Field errors stay in the iframe.CrossmintPaymentMethodManagementaddsonReadyandonChange({ mode, empty, complete }), like Stripe'sreadyandchangeevents, so your button can stay disabled until a submit can succeed.invalid,failedandunavailablesubmit results now carry acode(for exampleincomplete_card,save_failed,timeout); a code the component does not know becomesunknown. The code lists are exported asPAYMENT_METHOD_SUBMIT_INVALID_CODES,PAYMENT_METHOD_SUBMIT_FAILED_CODESandPAYMENT_METHOD_SUBMIT_UNAVAILABLE_CODES.@crossmint/client-sdk-react-ui@5.0.0
Major Changes
a55b5e4: BREAKING:
CrossmintPaymentMethodManagementno longer renders a built-in submit button. ThehideSubmitButtonprop is removed — the component always asks the host to submit viaref.submit(), which must be wired to your own button. The iframe no longer draws the message of aninvalidorfailedsubmit: show themessagethatref.submit()returns. Field errors stay in the iframe.CrossmintPaymentMethodManagementaddsonReadyandonChange({ mode, empty, complete }), like Stripe'sreadyandchangeevents, so your button can stay disabled until a submit can succeed.invalid,failedandunavailablesubmit results now carry acode(for exampleincomplete_card,save_failed,timeout); a code the component does not know becomesunknown. The code lists are exported asPAYMENT_METHOD_SUBMIT_INVALID_CODES,PAYMENT_METHOD_SUBMIT_FAILED_CODESandPAYMENT_METHOD_SUBMIT_UNAVAILABLE_CODES.Patch Changes
stagingFundand send USDXM. The bring-your-own-auth links point at the current docs page.@crossmint/client-sdk-auth@1.3.36
Patch Changes
@crossmint/client-sdk-auth1.3.4 the client stores the session ascrossmint-jwt-<projectId>andcrossmint-refresh-token-<projectId>, but the server SDK only read and wrotecrossmint-jwtandcrossmint-refresh-token, sogetSession(request)saw no session and a custom refresh route stored cookies the client never read.getSession(request),handleCustomRefreshandlogoutnow read the scoped names, and the legacy names only when no scoped cookie is present.storeAuthMaterial(and sogetSession(request, response),handleCustomRefreshandlogout) writes the scoped names;logoutalso expires the legacy ones. NewgetAuthCookieNames(projectId)returns the scoped names, for code with no request object such as a Next.js Server Component;validateAPIKeyis re-exported so the project ID can be read from the API key. The naming helpergetScopedCookieNamenow lives in@crossmint/common-sdk-authand the client uses it.@crossmint/client-sdk-react-base@2.5.5
Patch Changes
@crossmint/client-sdk-react-native-ui@2.1.5
Patch Changes
stagingFundand send USDXM. The bring-your-own-auth links point at the current docs page.@crossmint/client-sdk-verifiable-credentials@3.4.112
Patch Changes
@crossmint/client-sdk-smart-wallet@0.3.87
Patch Changes
@crossmint/common-sdk-auth@1.1.34
Patch Changes
@crossmint/client-sdk-auth1.3.4 the client stores the session ascrossmint-jwt-<projectId>andcrossmint-refresh-token-<projectId>, but the server SDK only read and wrotecrossmint-jwtandcrossmint-refresh-token, sogetSession(request)saw no session and a custom refresh route stored cookies the client never read.getSession(request),handleCustomRefreshandlogoutnow read the scoped names, and the legacy names only when no scoped cookie is present.storeAuthMaterial(and sogetSession(request, response),handleCustomRefreshandlogout) writes the scoped names;logoutalso expires the legacy ones. NewgetAuthCookieNames(projectId)returns the scoped names, for code with no request object such as a Next.js Server Component;validateAPIKeyis re-exported so the project ID can be read from the API key. The naming helpergetScopedCookieNamenow lives in@crossmint/common-sdk-authand the client uses it.@crossmint/server-sdk@1.2.98
Patch Changes
@crossmint/client-sdk-auth1.3.4 the client stores the session ascrossmint-jwt-<projectId>andcrossmint-refresh-token-<projectId>, but the server SDK only read and wrotecrossmint-jwtandcrossmint-refresh-token, sogetSession(request)saw no session and a custom refresh route stored cookies the client never read.getSession(request),handleCustomRefreshandlogoutnow read the scoped names, and the legacy names only when no scoped cookie is present.storeAuthMaterial(and sogetSession(request, response),handleCustomRefreshandlogout) writes the scoped names;logoutalso expires the legacy ones. NewgetAuthCookieNames(projectId)returns the scoped names, for code with no request object such as a Next.js Server Component;validateAPIKeyis re-exported so the project ID can be read from the API key. The naming helpergetScopedCookieNamenow lives in@crossmint/common-sdk-authand the client uses it.@crossmint/wallets-sdk@1.22.1
Patch Changes
stagingFundand send USDXM. The bring-your-own-auth links point at the current docs page.@crossmint/auth-ssr-nextjs-demo@0.4.213
Patch Changes
crossmint-auth-node@1.1.109
Patch Changes
@crossmint/client-sdk-nextjs-starter@2.0.63
Patch Changes
@crossmint/wallets-playground-expo@0.0.49
Patch Changes
@crossmint/wallets-quickstart-devkit@0.2.83
Patch Changes
@crossmint/wallets-playground-react@0.0.46
Patch Changes
@crossmint/integration-tests@0.0.13
Patch Changes