Repository navigation
chore: version package - #344
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 15, 2026 16:23
05f210b to
bb58dbb
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.
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
@openfort/react@2.1.2
Patch Changes
#342
ded4137Thanks @condor-agent! - Fixed the embedded wallet list being discarded when the user is published beside it, which made a returning user look like they owned no wallets and routed the modal to wallet creation.#341
31b9a58Thanks @condor-agent! - Fixed Solana sponsored sends, which failed withUnknown method: transferTransactionbefore broadcast. The paymaster method the send flow relied on is no longer routed by the Openfort Solana RPC endpoint, sowalletConfig.solana.sponsorFeescould not complete a transfer. The transfer instructions are now built client-side and submitted throughsignAndSendTransaction, which is the supported path.Added
{ feeToken }as a value forwalletConfig.solana.sponsorFees, for projects whose gas sponsorship charges the end user in an SPL token instead of paying the fee for them. The fee payment instruction is quoted from the paymaster and appended to the transfer, and is rejected if it names an account outside that fee transfer.