Repository navigation
chore: version packages - #1338
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 12:17
f02ccc6 to
d6e823b
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 publish to npm yourself or setup this action to publish 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
mppx@0.21.2
Patch Changes
mppx/client/core,mppx/tempo/clientandmppx/tempo/serverentrypoints, so apps can load the client primitives or only the Tempo method without the other payment methods.mppx/clientandmppx/serverexport the same API as before.tempo/session. Servers accept configurable account (0x05) vouchers and close authorizations whenconfigurableVouchersis set (defaultfalse), advertise it in the challenge, and check each voucher against the signer config commitment recorded at open (OpeningCommitmentRecorded). Configurable account clients open channels with their config commitment as the salt, sign vouchers with configurable account signatures, refuse to open against servers that do not advertiseconfigurableVouchers(ConfigurableVouchersUnsupportedError), and surface top-ups that revert because the signer config changed asSignerConfigChangedError.Voucher.verifyVoucherandVoucher.verifyCloseAuthorizationtake optional{ configurable, openingCommitment }options; without them they accept only primitive signatures, as before.