Bump JS Packages - #1642
Open
pr-bot-solana-mobile[bot] wants to merge 1 commit into
Open
Bump JS Packages#1642pr-bot-solana-mobile[bot] wants to merge 1 commit into
pr-bot-solana-mobile[bot] wants to merge 1 commit into
Conversation
pr-bot-solana-mobile
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
September 3, 2026 16:22
634754b to
f8414ad
Compare
pr-bot-solana-mobile
Bot
force-pushed
the
changeset-release/main
branch
from
September 9, 2026 00:27
f8414ad to
7652f6f
Compare
pr-bot-solana-mobile
Bot
force-pushed
the
changeset-release/main
branch
from
September 10, 2026 20:27
7652f6f to
8141358
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
pr-bot-solana-mobile
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
September 15, 2026 21:29
e24449f to
feb9288
Compare
pr-bot-solana-mobile
Bot
force-pushed
the
changeset-release/main
branch
from
September 25, 2026 23:01
feb9288 to
25feed8
Compare
pr-bot-solana-mobile
Bot
force-pushed
the
changeset-release/main
branch
from
September 25, 2026 23:03
25feed8 to
3c616e2
Compare
This branch has not been 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
@solana-mobile/mobile-wallet-adapter-protocol@2.4.0
Minor Changes
c258ef8: Declare
react-nativeas an optional peer dependency.It was previously a required peer dependency, which npm 7 and later install automatically, so browser-only consumers were pulling the entire React Native toolchain into
node_modules— roughly 32 MB ofreact-nativeitself, plusmetroand the transitive advisories it carries — even though no browser code path imports it. React Native is reached only through thereact-nativeexport condition, so nothing about which code runs where has changed; only the manifest was wrong.React Native consumers are unaffected: they already depend on
react-nativedirectly, and an optional peer dependency resolves identically for them.Patch Changes
e9f68c2: Support Solana v1 transactions.
wallet-standard-mobileThe local wallet now advertises the
supportedTransactionVersionsthe connected MWA wallet reports, instead of always['legacy', 0]. The remote wallet already did this.A wallet that reports
1is now advertised as supporting v1 transactions. A wallet that reports onlylegacyis no longer advertised as supporting v0.mobile-wallet-adapter-protocolsupported_transaction_versionsis typed withSolanaTransactionVersionfrom@solana/wallet-standard-featuresinstead ofTransactionVersionfrom@solana/web3.js, so it includes1.Requires
@solana/wallet-standard-features^1.5.0(also bumped inwallet-standard-mobileandwallet-adapter-mobile).Dropped the unused
@solana/web3.jsdevDependency.784619b: Accept
@solana/kitv8 alongside v7.mobile-wallet-adapter-protocol-kitwidens its@solana/kitpeer dependency and its@solana/transaction-messages/@solana/transactionsdependencies to^7.0.0 || ^8.0.0, andmobile-wallet-adapter-protocolwidens its@solana/kitdependency the same way. Apps on kit 8 previously ended up with a duplicate kit 7 tree innode_modules(and a peer-dependency conflict on@solana/kit); with the widened ranges everything dedupes against the app's kit tree, whichever major it uses. Every kit API these packages touch is unchanged between v7 and v8, so no code changes were needed.@solana-mobile/mobile-wallet-adapter-protocol-kit@2.4.0
Minor Changes
@solana-mobile/mobile-wallet-adapter-protocoland@solana-mobile/mobile-wallet-adapter-protocol-web3js. The three protocol packages are now released together as a fixed group, so from this release onward they always share the same version number. This is a versioning change only; there are no code or API changes in this package beyond those listed separately.Patch Changes
784619b: Accept
@solana/kitv8 alongside v7.mobile-wallet-adapter-protocol-kitwidens its@solana/kitpeer dependency and its@solana/transaction-messages/@solana/transactionsdependencies to^7.0.0 || ^8.0.0, andmobile-wallet-adapter-protocolwidens its@solana/kitdependency the same way. Apps on kit 8 previously ended up with a duplicate kit 7 tree innode_modules(and a peer-dependency conflict on@solana/kit); with the widened ranges everything dedupes against the app's kit tree, whichever major it uses. Every kit API these packages touch is unchanged between v7 and v8, so no code changes were needed.Updated dependencies [c258ef8]
Updated dependencies [e9f68c2]
Updated dependencies [784619b]
@solana-mobile/wallet-adapter-mobile@2.4.0
Minor Changes
c258ef8: Declare
react-nativeand@react-native-async-storage/async-storageas optional peer dependencies, moving async-storage out ofoptionalDependenciesand widening its accepted range to^1.17.7 || ^2.0.0, and load async-storage lazily.react-nativewas a required peer dependency and async-storage sat inoptionalDependencies, both of which package managers install by default, so browser-only consumers were pulling the entire React Native toolchain — includingmetroand the transitive advisories it carries — intonode_modules. Both packages are reached only through thereact-nativeexport condition, so which code runs where is unchanged; a browser-only install no longer containsreact-native,metro, or async-storage.Action required for React Native consumers that use the default authorization result cache. If you call
createDefaultAuthorizationResultCache(), add@react-native-async-storage/async-storageto your own app dependencies — it is no longer installed transitively. The release also adds runtime validation: async-storage is now resolved lazily, on first use, andcreateDefaultAuthorizationResultCache()throws a descriptive error when it is missing or unusable (such as when its native module has not been linked) instead of failing silently into an inert cache. Apps that pass their ownauthorizationResultCachenever load async-storage and do not need it installed; the lazyrequiresits inside atryblock, which Metro's defaultallowOptionalDependenciesconfiguration treats as an optional dependency, so their builds keep working without it.Patch Changes
e9f68c2: Support Solana v1 transactions.
wallet-standard-mobileThe local wallet now advertises the
supportedTransactionVersionsthe connected MWA wallet reports, instead of always['legacy', 0]. The remote wallet already did this.A wallet that reports
1is now advertised as supporting v1 transactions. A wallet that reports onlylegacyis no longer advertised as supporting v0.mobile-wallet-adapter-protocolsupported_transaction_versionsis typed withSolanaTransactionVersionfrom@solana/wallet-standard-featuresinstead ofTransactionVersionfrom@solana/web3.js, so it includes1.Requires
@solana/wallet-standard-features^1.5.0(also bumped inwallet-standard-mobileandwallet-adapter-mobile).Dropped the unused
@solana/web3.jsdevDependency.Updated dependencies [f72388e]
Updated dependencies [c258ef8]
Updated dependencies [e9f68c2]
Updated dependencies [c258ef8]
Updated dependencies [50ccaca]
Updated dependencies [784619b]
@solana-mobile/wallet-standard-mobile@0.7.0
Minor Changes
c258ef8: Move
@react-native-async-storage/async-storagefromoptionalDependenciesto an optional peer dependency, widen the accepted range to^1.17.7 || ^2.0.0, and load it lazily.optionalDependenciesare installed by default by every package manager — "optional" means only that a failed install is tolerated, not that the package is skipped — so browser-only consumers were pulling async-storage and, through its own peer dependency onreact-native, the entire React Native toolchain intonode_modules. Together with the matching fix in@solana-mobile/mobile-wallet-adapter-protocol, a browser-only install of this package drops from about 207 MB to about 42 MB and from 334 packages to 93, and the seven high-severitymetroadvisories it used to surface innpm auditgo away entirely. Downstream lockfiles will shrink substantially on the next update; that is this change taking effect, not packages going missing.Action required for React Native consumers that use the default authorization cache. If you call
createDefaultAuthorizationCache(), add@react-native-async-storage/async-storageto your own app dependencies — it is no longer installed transitively. The release also adds runtime validation: async-storage is now resolved lazily, on first use, andcreateDefaultAuthorizationCache()throws a descriptive error when it is missing or unusable (such as when its native module has not been linked) instead of failing silently into an inert cache. Apps that pass their ownauthorizationCachenever load async-storage and do not need it installed; the lazyrequiresits inside atryblock, which Metro's defaultallowOptionalDependenciesconfiguration treats as an optional dependency, so their builds keep working without it.50ccaca: Make
authorizationCache,chainSelectorandonWalletNotFoundoptional inregisterMwaand the wallet constructors, defaulting tocreateDefaultAuthorizationCache(),createDefaultChainSelector()andcreateDefaultWalletNotFoundHandler()respectively. The config shapes are now exported asSolanaMobileWalletAdapterWalletConfig, withLocalSolanaMobileWalletAdapterWalletConfig,RemoteSolanaMobileWalletAdapterWalletConfigandNostrSolanaMobileWalletAdapterWalletConfigextending it. Existing callers that pass all properties are unaffected.Patch Changes
f72388e: Fix connection deadlock on loopback-origin dapps (localhost dev via
adb reverse). Local Network Access only gates requests that cross into a more private address space, so a page served fromlocalhost,*.localhost,127.0.0.0/8, or[::1]fetching loopback is exempt — the browser never shows the permission prompt and the permission state can never leave "prompt", which left the connection hanging until the association timeout. Loopback origins now skip the permission gate entirely and go straight to the association intent; non-loopback origins keep the existing prompt flow.e9f68c2: Support Solana v1 transactions.
wallet-standard-mobileThe local wallet now advertises the
supportedTransactionVersionsthe connected MWA wallet reports, instead of always['legacy', 0]. The remote wallet already did this.A wallet that reports
1is now advertised as supporting v1 transactions. A wallet that reports onlylegacyis no longer advertised as supporting v0.mobile-wallet-adapter-protocolsupported_transaction_versionsis typed withSolanaTransactionVersionfrom@solana/wallet-standard-featuresinstead ofTransactionVersionfrom@solana/web3.js, so it includes1.Requires
@solana/wallet-standard-features^1.5.0(also bumped inwallet-standard-mobileandwallet-adapter-mobile).Dropped the unused
@solana/web3.jsdevDependency.Updated dependencies [c258ef8]
Updated dependencies [e9f68c2]
Updated dependencies [784619b]
@solana-mobile/mobile-wallet-adapter-protocol-web3js@2.4.0
Patch Changes
@solana-mobile/mobile-wallet-adapter-walletlib@1.4.6
Patch Changes
35fc89f: Stop advertising a CommonJS build that is never produced.
The
nodecondition declared"require": "./lib/cjs/index.js", but this package builds ESM only —tsdown.config.tsemitsformat: 'esm'intolib/esm, andpostbuildwrites only thelib/esmtype marker. Nothing has producedlib/cjssince the build moved to tsdown, so the file was absent from the published tarball andrequire('@solana-mobile/mobile-wallet-adapter-walletlib')failed withMODULE_NOT_FOUNDnaming a path that had never existed.The
nodecondition now points at the ESM build that is actually shipped. Importers are unaffected;requirecallers on Node 22.12 and later load it throughrequire(esm), and on older versions get a plain "cannot require an ES module" error instead of a missing-file one.