[dependabot]

Bumps the npm-patch-and-minor group with 14 updates:

Package	From	To
tsx	4.22.4	4.23.15
@openzeppelin/relayer-plugin-channels	0.20.0	0.21.0
@noble/ciphers	2.2.0	2.4.0
@noble/curves	2.2.0	2.4.0
@noble/hashes	2.2.0	2.4.0
@x402/core	2.14.0	2.28.0
@x402/stellar	2.14.0	2.28.0
passkey-kit	0.12.0	0.19.1
react	19.2.6	19.3.1
@types/react	19.2.15	19.3.0
react-dom	19.2.6	19.3.1
@types/react-dom	19.2.3	19.3.0
react-test-renderer	19.1.0	19.3.1
@types/react-test-renderer	19.1.0	19.3.0

Updates tsx from 4.22.4 to 4.23.15

Release notes

Sourced from tsx's releases.

v4.23.15

4.23.15 (2026-09-20)

Bug Fixes

• exclude bare builtins from namespace inheritance (38e1588)
• expose require.cache and require.extensions to tsImport CommonJS modules (2da3407)
• make namespaced register() overloads portable for declaration emit (562c434)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.14

4.23.14 (2026-09-20)

Bug Fixes

• restore the CJS bridge namespace for Node 24 require(esm) under tsImport() (#802) (6e5236b)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.13

4.23.13 (2026-08-30)

Bug Fixes

• cache: bound shared transform cache memory (#835) (28e1f12)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.12

4.23.12 (2026-08-10)

Bug Fixes

• shim import.meta when tokens are split by comments or newlines (#829) (ed9d330), closes #828

---

This release is also available on:

• npm package (@​latest dist-tag)

... (truncated)

Commits

• ca66105 test: fix drive-less file URLs in ESM resolver fixtures
• 2da3407 fix: expose require.cache and require.extensions to tsImport CommonJS modules
• 38e1588 fix: exclude bare builtins from namespace inheritance
• 562c434 fix: make namespaced register() overloads portable for declaration emit
• edfb1f0 build: upgrade pkgroll and externalize CJS loader reference
• 70e7828 test: upgrade tinyspy for disposable API
• 9ed2022 ci: avoid duplicate release notifications
• 872e77f refactor: use disposables for cleanup
• 6e5236b fix: restore the CJS bridge namespace for Node 24 require(esm) under tsImport...
• 28e1f12 fix(cache): bound shared transform cache memory (#835)
• Additional commits viewable in compare view

Updates @openzeppelin/relayer-plugin-channels from 0.20.0 to 0.21.0

Release notes

Sourced from @​openzeppelin/relayer-plugin-channels's releases.

v0.21.0

Minor Changes

• 3265995: Upgrade @stellar/stellar-sdk to v17 (Stellar Protocol 28). The plugin now parses and validates CAP-71 SOROBAN_CREDENTIALS_ADDRESS_V2 auth entries, introduced in Protocol 27 and emitted by default by @stellar/stellar-sdk v17 clients. Previously such entries were rejected with Invalid func or auth encoding, and v2 auth entries returned by RPC simulation failed to parse. Legacy SOROBAN_CREDENTIALS_ADDRESS (v1) entries continue to be accepted; the plugin does not enforce a v1 cutoff. The auth expiry check (AUTH_EXPIRY_TOO_SHORT) now covers all address credential variants, including SOROBAN_CREDENTIALS_ADDRESS_WITH_DELEGATES.

Changelog

Sourced from @​openzeppelin/relayer-plugin-channels's changelog.

0.21.0

Minor Changes

• 3265995: Upgrade @stellar/stellar-sdk to v17 (Stellar Protocol 28). The plugin now parses and validates CAP-71 SOROBAN_CREDENTIALS_ADDRESS_V2 auth entries, introduced in Protocol 27 and emitted by default by @stellar/stellar-sdk v17 clients. Previously such entries were rejected with Invalid func or auth encoding, and v2 auth entries returned by RPC simulation failed to parse. Legacy SOROBAN_CREDENTIALS_ADDRESS (v1) entries continue to be accepted; the plugin does not enforce a v1 cutoff. The auth expiry check (AUTH_EXPIRY_TOO_SHORT) now covers all address credential variants, including SOROBAN_CREDENTIALS_ADDRESS_WITH_DELEGATES.

Commits

• c7cf073 Version Packages (#124)
• 3265995 feat: upgrade stellar-sdk to v17 for Protocol 28 (CAP-71 v2 auth) (#121)
• See full diff in compare view

Updates @noble/ciphers from 2.2.0 to 2.4.0

Release notes

Sourced from @​noble/ciphers's releases.

2.4.0

• ChaCha / Salsa: reject output buffers that partially overlap unread input
• PRG: using after clean now throws
• Webcrypto: snapshot keys and params
• FF1: sizing for very large domains

Full Changelog: paulmillr/noble-ciphers@2.3.0...2.4.0

2.3.0

Hardening

• AEAD strictness: passing AAD to a cipher that doesn't support it now throws AAD not supported instead of silently ignoring it. Applies to both native ciphers and the webcrypto wrappers via a new withAAD cipher param.
• CBC/ECB padding failures now surface as a generic aes: bad decrypt instead of a padding-specific message, reducing padding-oracle signal.
• FF1: minLen now enforces the NIST SP 800-38G minimum of 2 in addition to radix**minlen >= 100; stricter radix encoding guards.
• Correctness fixes for big-endian CPUs (polyval tag normalization, AES CTR partial-block tails).
• Other minor corrections
• Reduce on-disk package size: 710kb → 531kb (-179kb), by disabling source maps (they became less relevant).

Boost AES-SIV speed by 20%

Full Changelog: paulmillr/noble-ciphers@2.2.0...2.3.0

Changelog

Sourced from @​noble/ciphers's changelog.

2.4.0 (2026-08-27)

• ChaCha / Salsa: reject output buffers that partially overlap unread input
• PRG: using after clean now throws
• Webcrypto: snapshot keys and params
• FF1: sizing for very large domains

2.3.0 (2026-08-08)

Hardening

• AEAD strictness: passing AAD to a cipher that doesn't support it now throws AAD not supported instead of silently ignoring it. Applies to both native ciphers and the WebCrypto wrappers via a new withAAD cipher parameter.
• CBC/ECB padding failures now surface as a generic aes: bad decrypt instead of a padding-specific message, reducing padding-oracle signal.
• FF1: minLen now enforces the NIST SP 800-38G minimum of 2 in addition to radix ** minLen >= 100; stricter radix encoding guards.
• Correctness fixes for big-endian CPUs (POLYVAL tag normalization and AES-CTR partial-block tails).
• Other minor corrections.
• Reduce on-disk package size from 710 KB to 531 KB by disabling source maps, which have become less relevant.
• Boost AES-SIV speed by 20%.

Commits

• d9e8a6a Release 2.4.0.
• 457f440 Add changelog
• 15fdd4a Bump vectors
• 654f9cc README and benchmarks
• 7ce57c6 Bump ci workflows
• 6c0f6bd Add fuzzing
• 5053f90 Fix slow test
• 3557d07 Fix ff1 on bun
• 53466fa Format
• 5d97c84 FF1: do not use fp
• Additional commits viewable in compare view

Updates @noble/curves from 2.2.0 to 2.4.0

Release notes

Sourced from @​noble/curves's releases.

2.4.0

• Harden FROST distributed key generation against round-one transcript substitution.
  • This is not a vulnerability; it's protection against those who don't follow the FROST spec. Spec wants user to preserve rounds.
• FROST: Enforced RFC 9591 point validation for BLS and BN
• POPRF: replace inversion with const-time version
• Weierstrass: harden public-key boundaries & infinity handling
  • ECDH and ECDSA now reject the identity even for point types whose generic codec permits it
  • Curves that disallow infinity cannot encode it, while opted-in curves use the canonical SEC 1 0x00 encoding.
• DER: Bounded ECDSA signature and INTEGER sizes before bigint conversion, preventing malformed inputs from causing disproportionate parsing and allocation work
• Snapshot all security-sensitive state (passed arguments) to ensure it can't be mutated

Special thanks to Red Team (Rob Hamilton, CalleBTC, Omer Talip) and 1Password's Off-by-1 Labs.

Full Changelog: paulmillr/noble-curves@2.3.0...2.4.0

2.3.0

Security & constant-timeness

• Hardened constant-time execution from best-effort to actual guarantees: no measurable timing behavior on 200K samples. Scalar multiplication now uses secret-scalar blinding via CSPRNG, un-precomputed points now use a constant-time fixed-window multiply instead of variable-time fallbacks, and modular arithmetic helpers were hardened. New CT benchmarks track timing behavior.
• General hardening across all modules
• Fixes from the Trail of Bits review: recovered ECDSA signatures are now bound to their recovery id, non-canonical BLS signature encodings are rejected, Edwards <-> Montgomery conversion helpers were corrected, and FROST DKG round-2 retry handling was hardened.

X25519 hardening

It was possible to execute a remote timing attack on X25519, across many samples, and learn up to 4.036 bits of long-term private key. Other 247 bits were NOT affected.

The impact: mainly fingerprinting (recognition of key across deployments), NOT key recovery, NOT X25519 breakage. Maintainer was also not able to escalate to co-residency (SMT).

Reported and found by:

• George Stergiopoulos, Department of Informatics, Athens University of Economics and Business, Greece (geostergiop@aueb.gr)
• Constantinos Patsakis, Department of Informatics, University of Piraeus, 80 Karaoli & Dimitriou str., 18534 Piraeus, Greece (kpatsak@unipi.gr)

Performance

• ECDSA/EdDSA verification up to +32%, Weierstrass ECDH up to +19%, x25519 getPublicKey 2.7×
• BLS signatures 2x
• Init time (first getPublicKey or sign) reduced ~2x for ed25519, p256, p384, p521
• Also faster verification of recovered signatures, pairing tower / FFT / Pippenger optimizations, and joint-MSM paths in FROST and OPRF
• getPublicKey / sign got slower because we've decreased window size (W=8 => W=6) and hardened CT execution (see above). Long-running apps that prefer 2.2.0-level speed can restore it with one line: secp256k1.Point.BASE.precompute(8) (likewise for other curves).

Misc

• Smaller bundles: improved tree-shaking across modules
• Better error messages and type checks
• Upgrade noble-hashes to 2.3.0, with performance boost
• Reduce on-disk size 1831kb → 1548kb (-282kb) by disabling source maps (they became less relevant).

Full Changelog: paulmillr/noble-curves@2.2.0...2.3.0

Changelog

Sourced from @​noble/curves's changelog.

2.4.0 (2026-08-27)

• Harden FROST distributed key generation against round-one transcript substitution.
  • This is not a vulnerability; it's protection against those who don't follow the FROST spec. Spec wants user to preserve rounds.
• FROST: Enforced RFC 9591 point validation for BLS and BN
• POPRF: replace inversion with const-time version
• Weierstrass: harden public-key boundaries & infinity handling
  • ECDH and ECDSA now reject the identity even for point types whose generic codec permits it
  • Curves that disallow infinity cannot encode it, while opted-in curves use the canonical SEC 1 0x00 encoding.
• DER: Bounded ECDSA signature and INTEGER sizes before bigint conversion, preventing malformed inputs from causing disproportionate parsing and allocation work
• Snapshot all security-sensitive state (passed arguments) to ensure it can't be mutated

Special thanks to Red Team (Rob Hamilton, CalleBTC, Omer Talip) and 1Password's Off-by-1 Labs.

2.3.0 (2026-08-06)

Security and constant-timeness

• Hardened constant-time execution from best-effort to actual guarantees, with no measurable timing behavior across 200,000 samples. Scalar multiplication now uses secret-scalar blinding via CSPRNG, unprecomputed points use a constant-time fixed-window multiply instead of variable-time fallbacks, and modular arithmetic helpers were hardened. New constant-time benchmarks track timing behavior.
• General hardening across all modules.
• Applied fixes from the Trail of Bits review: recovered ECDSA signatures are now bound to their recovery ID, non-canonical BLS signature encodings are rejected, Edwards-to-Montgomery conversion helpers were corrected, and FROST DKG round-two retry handling was hardened.

X25519 hardening

It was possible to execute a remote timing attack on X25519 across many samples and learn up to 4.036 bits of a long-term private key. The other 247 bits were not affected.

The impact is primarily fingerprinting—a key can be recognized across deployments—not key recovery or a break of X25519. The maintainer was also unable to escalate the attack to co-residency (SMT).

Reported and found by:

• George Stergiopoulos, Department of Informatics, Athens University of Economics and Business, Greece (geostergiop@aueb.gr).
• Constantinos Patsakis, Department of Informatics, University of Piraeus, 80 Karaoli & Dimitriou Street, 18534 Piraeus, Greece (kpatsak@unipi.gr).

Performance

• Improved ECDSA and EdDSA verification by up to 32%, Weierstrass ECDH by up to 19%, and X25519 getPublicKey by 2.7×.
• Improved BLS signature performance by 2×.
• Reduced initialization time for the first getPublicKey or sign call by approximately 2× for Ed25519, P-256, P-384, and P-521.
• Also improved verification of recovered signatures, pairing tower, FFT, and Pippenger performance, as well as joint-MSM paths in FROST and OPRF.
• getPublicKey and sign became slower because the window size was decreased from 8 to 6 and constant-time execution was hardened. Long-running applications that prefer 2.2.0-level speed can restore it with secp256k1.Point.BASE.precompute(8), and likewise for other curves.

Miscellaneous

• Improved tree-shaking for smaller bundles.
• Improved error messages and type checks.
• Upgraded noble-hashes to 2.3.0 for improved performance.
• Reduced on-disk size from 1,831 KB to 1,548 KB by disabling source maps, which have become less relevant.

Commits

• 656c436 Release 2.4.0.
• ca081f6 Add changelog
• 783fa9b Upgrade noble-hashes to 2.4.0
• 3becb84 readme
• bb52c57 readme
• 41f44d2 Restructure benchmarks. Update README
• 3587575 Bump vectors
• ae43344 Bump ci workflows
• 5c1aa39 Add fuzzing
• d5b95e4 test: add more hardening-related tests
• Additional commits viewable in compare view

Updates @noble/hashes from 2.2.0 to 2.4.0

Release notes

Sourced from @​noble/hashes's releases.

2.4.0

Security and correctness

• Protect passed options against mutation / pollution
• keccakprg: fail until entropy is added
• webcrypto: reject output sizes which crashed engine
• blake3: fix tree merging for multi-terabyte streams
• Improve zeroization

Misc

• Speed-up Argon2 by 20%
• Argon2 cost options are now optional. The defaults are t: 3, m: 1024 ** 2 KiB (1 GiB), p: 1, dkLen: 32, and a 1 GiB maxmem limit; larger-memory calls must set maxmem explicitly.
• Corrected scrypt's default maxmem to work for N: 2 ** 20, r: 8, and p: 1
• nextTick and asyncLoop now yield through scheduler.yield() when available or setTimeout otherwise, allowing timers, I/O, and rendering to progress. They also accept optional rejection cleanup; async Argon2, PBKDF2, and scrypt use it to wipe work state if scheduling is aborted.

Full Changelog: paulmillr/noble-hashes@2.3.0...2.4.0

2.3.0

Improve speed:

• +10-45% 32b inputs across all hashes
• +40% SHA-3 / SHAKE, +50% 1mb KT128 / KT256 / TurboSHAKE, +20% kmac
• 2.2x argon
• +20% pbkdf2 and hkdf

Other changes:

• Better error messages and stricter type checks everywhere
• Bugfix: HMAC _cloneInto now preserves canXOF (#134, ChALkeR); Argon2d typo rename (#135).
• blake2.compress renamed to _compress (marked internal).
• Reduce on-disk unpacked size 869kb → 665kb (-204kb) by disabling source maps (they became less relevant).

Full Changelog: paulmillr/noble-hashes@2.2.0...2.3.0

Changelog

Sourced from @​noble/hashes's changelog.

2.4.0 (2026-08-27)

Security and correctness

• Protect passed options against mutation / pollution
• keccakprg: fail until entropy is added
• webcrypto: reject output sizes which crashed engine
• blake3: fix tree merging for multi-terabyte streams
• Improve zeroization

Misc

• Speed-up Argon2 by 20%
• Argon2 cost options are now optional. The defaults are t: 3, m: 1024 ** 2 KiB (1 GiB), p: 1, dkLen: 32, and a 1 GiB maxmem limit; larger-memory calls must set maxmem explicitly.
• Corrected scrypt's default maxmem to work for N: 2 ** 20, r: 8, and p: 1
• nextTick and asyncLoop now yield through scheduler.yield() when available or setTimeout otherwise, allowing timers, I/O, and rendering to progress. They also accept optional rejection cleanup; async Argon2, PBKDF2, and scrypt use it to wipe work state if scheduling is aborted.

2.3.0 (2026-08-06)

Performance

• Improved 32-byte input performance across all hashes by 10–45%.
• Improved SHA-3 and SHAKE by 40%, one-megabyte KangarooTwelve, MarsupilamiFourteen, and TurboSHAKE by 50%, and KMAC by 20%.
• Improved Argon2 performance by 2.2×.
• Improved PBKDF2 and HKDF performance by 20%.

Other changes

• Added better error messages and stricter type checks throughout the package.
• Fixed HMAC._cloneInto so it preserves canXOF in issue #134, reported by @​ChALkeR, and corrected an Argon2d typo in issue #135.
• Renamed blake2.compress to the internal _compress method.
• Reduced unpacked on-disk size from 869 KB to 665 KB by disabling less-relevant source maps.

Commits

• 663c2ae Release 2.4.0.
• a6f7519 Add changelog
• 1bbc433 webcrypto: snapshot opts
• 5bd2e15 Remove unused files
• a3bc7ff Bump vectors
• fcb6cb6 README
• 64f3033 readme
• 9ac6165 Bump ci workflows
• 6587b51 Fix test on bun
• 91ecf91 Fix tests
• Additional commits viewable in compare view

Updates @x402/core from 2.14.0 to 2.28.0

Commits

• 6b6ee91 chore(go): release (#3629)
• 9320504 Pull request for mintlify/docs-update-1790707394690 (#3626)
• ced627c chore: version typescript packages  (#3627)
• da8c2f4 chore: version python package  (#3628)
• a349e7f feat(svm): Go batch-settlement, unified PaymentChannelStorage, and paymentcha...
• 5eee1e3 docs: show EVM and Solana in middleware README examples (#3619)
• a9955ae feat(evm): add Monad testnet USDC default asset (#3570)
• c84154b perf(svm): cache derived payment-channel PDAs (#3601)
• 5e97d9a docs: fix broken relative links in guides, examples and specs (#3596)
• dd89698 feat(evm): add Arc default stablecoins (#3590)
• Additional commits viewable in compare view

Updates @x402/stellar from 2.14.0 to 2.28.0

Commits

• 6b6ee91 chore(go): release (#3629)
• 9320504 Pull request for mintlify/docs-update-1790707394690 (#3626)
• ced627c chore: version typescript packages  (#3627)
• da8c2f4 chore: version python package  (#3628)
• a349e7f feat(svm): Go batch-settlement, unified PaymentChannelStorage, and paymentcha...
• 5eee1e3 docs: show EVM and Solana in middleware README examples (#3619)
• a9955ae feat(evm): add Monad testnet USDC default asset (#3570)
• c84154b perf(svm): cache derived payment-channel PDAs (#3601)
• 5e97d9a docs: fix broken relative links in guides, examples and specs (#3596)
• dd89698 feat(evm): add Arc default stablecoins (#3590)
• Additional commits viewable in compare view

Updates passkey-kit from 0.12.0 to 0.19.1

Release notes

Sourced from passkey-kit's releases.

passkey-kit v0.18.3

This patch replaces the broken 0.18.2 npm artifact.

Runtime dependencies now use exact package versions instead of workspace protocols. CI and publication verify that these versions match their workspace packages.

The release also updates vitest to 4.1.11. This change removes GHSA-82fw-gwwq-j7x9 from the development dependency audit.

Runtime behavior, the wallet contract, passkey-kit-sdk@0.9.0, and sac-sdk@0.4.4 remain unchanged from 0.18.2.

See CHANGELOG.md for details.

passkey-kit v0.18.2

This patch cleans every published package output before each build. It removes stale generated files from reused worktrees.

Runtime behavior, the wallet contract, passkey-kit-sdk@0.9.0, and sac-sdk@0.4.4 remain unchanged from v0.18.1.

See CHANGELOG.md for details.

passkey-kit v0.18.1

This release removed the vulnerable consumer-only relayer dependency tree and preserved relayer transport diagnostics.

The published tarball contained eight stale, unexported generated files from an earlier build. Use v0.18.2 instead.

passkey-kit v0.18.0

Changes

• Bound package support to @stellar/stellar-sdk ^16.3.0.
• Removed the ignored indexer compatibility option.
• Updated vulnerable npm and safe Cargo dependencies.
• Added dependency audits, relayer type checking, pinned actions, and secret scanning.
• Added an admin-root mismatch regression test.

The canonical contract, passkey-kit-sdk@0.9.0, and sac-sdk@0.4.4 remain unchanged. Read CHANGELOG.md before updating.

passkey-kit v0.17.3

Changes

• Mercury schema-2 credential discovery uses the v2 lookup route.
• Connection rejects passkey signers after their inclusive expiration boundary.
• The parser rejects incomplete, ambiguous, or colliding lookup results.

The contract and generated bindings remain unchanged.

passkey-kit v0.17.2

Security

• Generic signing refuses wallet administration and contract-deploy authority.
• Administrative roots must match the transaction host function exactly.
• Dedicated administrative signing methods declare this authority.

... (truncated)

Changelog

Sourced from passkey-kit's changelog.

0.19.1 — 2026-09-17

• Pinned what signLegacyUpgradeTx will sign. The auth entry must root at the named wallet's own top-level update_contract_code or migrate_signers with no sub-invocations, and an update_contract_code may only carry the canonical legacy-line target (override with expectedTarget). 0.19.0 pinned the root to the transaction's own call but not the function name or the target, so a hostile transaction rooted at another wallet-admin call could have been signed through this path.
• Refused a pointless re-upgrade. buildLegacyUpgradeTx now rejects a wallet already on the legacy-line target.
• Counted an entry as live through its liveUntil ledger inclusive in inspectLegacyWallet.
• Pointed LegacyWalletError at the kit's own helpers, not only at the 0.10.20–0.12.x line.
• Docs. README no longer says this release has no legacy migration path; the guide's application section, restore step (protocol-23 auto-restore), policy-signer boundary, migrate-decision timing, and a live testnet verification of both cohorts through the SDK path.

0.19.0 — 2026-09-17

• Added a safe in-place upgrade target for pre-fix legacy wallets. New contracts-legacy/ workspace builds the last pre-1.0 wallet (e45c42b9…) with signer reads that accept both pre-1.0 storage layouts, plus migrate_signers and get_signer. Wallets on the four mainnet WASM hashes whose update_signer lacks require_auth (0c0a264d…, 19868df3…, b62f6221…, c5509dfa…) can upgrade to c079d3a4136eb6ca68eb724acd3d8af11b0be4a0ed82605925a6dfd4dd83a97c without bricking. The artifact is committed at contracts-legacy/out/smart_wallet.wasm and CI verifies its hash. Earlier post-fix builds brick the two bare-layout hashes. See docs/legacy-wallet-upgrade.md and the new "Known-vulnerable wallet WASM hashes" section in SECURITY.md. The v1 contract is unchanged.
• Named legacy wallets on connect. connectWallet now throws LegacyWalletError (code 2006, WALLET_LEGACY_CODE) when a candidate wallet runs pre-1.0 code, before birth verification would fail it for a less useful reason. vulnerable: true carries the in-place upgrade target and the guide URL; vulnerable: false points at the 0.10.20–0.12.x kit line. The constructor rejects a known-vulnerable walletWasmHash or accepted hash. New exports: LegacyWalletError, KNOWN_VULNERABLE_WALLET_WASM_HASHES, LEGACY_WALLET_WASM_HASHES, LEGACY_UPGRADE_TARGET_WASM_HASH, LEGACY_WALLET_UPGRADE_GUIDE_URL.
• Crafted the legacy upgrade from the wallet's actual state. New kit methods for wallets this kit cannot connect to: inspectLegacyWallet(id) reads the code hash and the liveness of the instance, current-code, and target-code entries and returns a status (vulnerable / legacy / current / unknown), the storage cohort, what is archived, and a plain recommendation; buildLegacyUpgradeTx(id) builds update_contract_code(<target>) (restoring archived entries first when

... (truncated)

Commits

• See full diff in compare view

Updates react from 19.2.6 to 19.3.1

Release notes

Sourced from react's releases.

19.3.1 (October 14th, 2026)

React Server Components

• Improve transport protocol (#37845 by @​unstubbable and @​eps1lon)

19.3.0 (September 9, 2026)

Below is a list of all new features, APIs, and bug fixes.

Read the React 19.3 release post for more information.

New React Features

• <ViewTransition />: Adds <ViewTransition /> and addTransitionType APIs to power View Transition animations in React (@​sebmarkbage, @​jackpope, @​gaearon: #31975, #31987, #31996, #31999, #32001, #32002, #32028, #32029, #32031, #32034, #32038, #32041, #32050, #32090, #32105, #32254, #32379, #32422, #32462, #32540, #32545, #32585, #32599, #32611, #32612, #32617, #32651, #32653, #32656, #32664, #32699, #32723, #32734, #32751, #32752, #32760, #32761, #32764, #32772, #32790, #32819, #32820, #32822, #32833, #32849, #33094, #33191, #33200, #33206, #33293, #33330, #33331, #33332, #33357, #33362, #33433, #33576, #34374, #34450, #34481, #34500, #34502, #34510, #34511, #34539, #35567, #35564, #35485, #35380, #35063, #35060, #34676, #36917, #35337, #35520)
• Fragment Refs: Add Refs to <Fragment /> to support composable platform behavior (@​jackpope, @​sebmarkbage, @​eps1lon, @​Dhakshin2007, @​chirokas, @​teamleaderleo, @​fallintoplace: #32465, #32613, #32619, #32654, #32660, #32682, #32722, #32813, #32814, #33056, #33058, #33093, #34069, #34103, #34544, #34545, #37062, #37061, #37060, #36047, #36010, #35642, #35641, #35637, #35630, #34935, #37457, #37408, #37326, #37251, #37171, #37169, #37168, #37167, #37166, #37165, #37164, #37163, #37162, #37161, #37160, #37125, #37063)

New React DOM Features

• browser(): a new react-dom API that returns a usable which errors during server rendering and resolves in the browser. use(browser()) inside a <Suspense> boundary marks a subtree as browser-only without reporting a recoverable error (@​gnoff: #37143, #37241)
  • Added an onBrowserBailout option to the react-dom/server APIs to observe when a subtree defers to the browser (@​gnoff #37193)

Notable changes

• Enable Trusted Types API integration (@​rickhanlonii #35816)
• Transitions now render independently instead of being entangled into a single render, so a slow transition no longer holds up unrelated ones (@​acdlite #37290)
• Added a DEV-only warning when a component appears to have been unblocked by calling use() conditionally (@​hoxyq, @​eps1lon: #37104, #37203, #37491)

All Changes

React

• Fast Refresh Fixes
  • Fix Fast Refresh to find and remount edits to components wrapped behind lazy() (@​sophiebits #36965)
  • Fix Fast Refresh so edits to a memo() comparison function take effect (@​sophiebits #36964)
  • Fix Fast Refresh crash when an edit changes the kind of a component's type (@​sophiebits #36963)
  • Unify hot reload type resolution for Fast Refresh (@​sophiebits #36962)
  • Fix Fast Refresh to remount correctly when an edit changes the component kind (@​sophiebits #36950)
  • Double invoke effects in StrictMode after Fast Refresh (@​eps1lon #35962)
• Performance Track Fixes
  • Prevent crash when accessing $$typeof in Performance Tracks (@​eps1lon #35679)
  • Handle non-string function names in Performance Tracks (@​eps1lon #35659)
  • Use minus (-) instead of en dash for removed props in Performance Tracks (@​eps1lon #35649)
  • Handle arrays with bigints in deep objects in Performance Tracks (@​eps1lon #35648)
  • Don't enumerate typed array props in Performance Tracks in DEV (@​UditDewan #36913)
  • Bail out of diffing wide objects and arrays in Performance Tracks (@​eps1lon #34742)
  • Clear potentially large performance measures in DEV (@​hoxyq #34803)
  • Fix missing else branch for renders with no props change in Performance Tracks (@​hoxyq #34837)
• Activity Fixes
  • Fix useSyncExternalStore missing store mutations that happened while an Activity tree was hidden (@​sophiebits #36947)
  • Hide portal contents when an Activity is hidden (@​acdlite #35091)
  • Prevent metadata hoisting in hidden <Activity> trees (@​ronnakamoto #34983)

... (truncated)

Changelog

Sourced from react's changelog.

19.3.0 (September 9, 2026)

New React Features

• <ViewTransition />: Adds <ViewTransition /> and addTransitionType APIs to power View Transition animations in React (@​sebmarkbage, @​jackpope, @​gaearon: #31975, #31987, #31996, #31999, #32001, #32002, #32028, #32029, #32031, #32034, #32038, #32041, #32050, #32090, #32105, #32254, #32379, #32422, #32462, #32540, #32545, #32585, #32599, #32611, #32612, #32617, #32651, #32653, #32656, #32664, #32699, #32723, #32734, #32751, #32752, #32760, #32761, #32764, #32772, #32790, #32819, #32820, #32822, #32833, #32849, #33094, #33191, #33200, #33206, #33293, #33330, #33331, #33332, #33357, #33362, #33433, #33576, #34374, #34450, #34481, #34500, #34502, #34510, #34511, #34539,