Skip to content

chore(deps): bump the minor-and-patch group across 1 directory with 18 updates - #1436

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/minor-and-patch-05a022cd87
Open

chore(deps): bump the minor-and-patch group across 1 directory with 18 updates#1436
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/minor-and-patch-05a022cd87

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

Bumps the minor-and-patch group with 18 updates in the / directory:

Package From To
react-hot-toast 2.6.0 2.6.1
lint-staged 17.4.1 17.5.1
@rollup/rollup-linux-x64-gnu 4.63.1 4.63.3
@stellar/stellar-sdk 17.0.1 17.1.0
@tanstack/react-query 5.102.8 5.103.1
@tanstack/react-virtual 3.14.10 3.14.13
next 16.3.3 16.3.5
react 19.2.7 19.3.0
@types/react 19.2.18 19.3.0
react-dom 19.2.7 19.3.0
@types/react-dom 19.2.5 19.3.0
@eslint/eslintrc 3.3.6 3.3.7
@testing-library/dom 10.4.1 10.4.2
@testing-library/user-event 14.6.6 14.6.7
@types/react 19.2.18 19.3.0
@types/react-dom 19.2.5 19.3.0
eslint-config-next 16.3.3 16.3.5
happy-dom 20.12.0 20.14.5
@playwright/test 1.62.1 1.63.0
zod 4.5.4 4.6.5

Updates react-hot-toast from 2.6.0 to 2.6.1

Release notes

Sourced from react-hot-toast's releases.

v2.6.1

  • Made toast styles easier to override with Tailwind CSS by using :where() to lower CSS specificity. (f339d71)
  • Fixed an issue where toasts stopped updating after a component unmounted when multiple hooks shared the same toasterId. Thanks to @​matthernet for reporting the issue and suggesting the fix! (#436)
  • Fixed TypeScript resolution errors in pnpm strict mode by adding @types/react and @types/react-dom as optional peer dependencies. Thanks to @​q121212 for the fix and @​baraknaveh for the report! (#435)

[[Full changelog: v2.6.0 → v2.6.1](https://github.com/timolins/react-hot-toast/compare/v2.6.0...v2.6.1)](https://github.com/timolins/react-hot-toast/compare/v2.6.0...v2.6.1)

Commits
  • e725d38 2.6.1
  • 114cafd Merge pull request #436 from timolins/codex/fix-use-store-subscriber-cleanup
  • ce3f199 Fix useStore subscriber cleanup
  • 52613c1 Merge pull request #435 from q121212/fix/missing-peer-dep-types-react
  • 64e1fff fix(build): add missing @​types/react and @​types/react-dom peer deps for pnpm ...
  • f339d71 Use :where() for easier Tailwind overrides
  • See full diff in compare view

Updates lint-staged from 17.4.1 to 17.5.1

Release notes

Sourced from lint-staged's releases.

v17.5.1

Patch Changes

  • #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

    A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

v17.5.0

Minor Changes

  • #1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.

Patch Changes

  • #1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.

  • #1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.

  • #1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

Changelog

Sourced from lint-staged's changelog.

17.5.1

Patch Changes

  • #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

    A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

17.5.0

Minor Changes

  • #1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.

Patch Changes

  • #1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.

  • #1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.

  • #1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

Commits
  • f8b1ab1 Merge pull request #1853 from lint-staged/changeset-release/main
  • 3b54961 chore(changeset): release
  • 09317ff Merge pull request #1852 from lint-staged/fix-ambient-declaration
  • bfcca94 fix: change defineConfig signature from const to a function
  • dcb59f6 Merge pull request #1846 from lint-staged/changeset-release/main
  • 9c8c6dc chore(changeset): release
  • 586466f Merge pull request #1849 from lint-staged/improve-intent-to-add
  • 45eda5f refactor: improve --intent-to-add detection
  • 26372e3 Merge pull request #1848 from lint-staged/fix-color-detection
  • d718ccc fix: honor FORCE_COLOR/NO_COLOR env variables in non-TTY streams
  • Additional commits viewable in compare view

Updates @rollup/rollup-linux-x64-gnu from 4.63.1 to 4.63.3

Release notes

Sourced from @​rollup/rollup-linux-x64-gnu's releases.

v4.63.3

4.63.3

2026-09-14

Bug Fixes

  • Make sure that the internal shims for basename and extname in the browser build fully match NodeJS (#6473)
  • Always report and recover from failures on invalidation in watch mode (#6506)
  • Respect windows line terminators when tree-shaking in situations where line-breaks need to be removed to prevent automatic semicolon insertion (#6514)

Pull Requests

v4.63.2

4.63.2

2026-09-12

Bug Fixes

  • Fix a bug when filtering logs for nested properties via the CLI (#6511)

Pull Requests

Changelog

Sourced from @​rollup/rollup-linux-x64-gnu's changelog.

4.63.3

2026-09-14

Bug Fixes

  • Make sure that the internal shims for basename and extname in the browser build fully match NodeJS (#6473)
  • Always report and recover from failures on invalidation in watch mode (#6506)
  • Respect windows line terminators when tree-shaking in situations where line-breaks need to be removed to prevent automatic semicolon insertion (#6514)

Pull Requests

4.63.2

2026-09-12

Bug Fixes

  • Fix a bug when filtering logs for nested properties via the CLI (#6511)

Pull Requests

Commits

Updates @stellar/stellar-sdk from 17.0.1 to 17.1.0

Release notes

Sourced from @​stellar/stellar-sdk's releases.

v17.1.0

v17.1.0

Added

  • getClaimableBalanceIdFromResult(result, opIndex): reads the claimable balance ID created by a CreateClaimableBalance operation out of a submitted transaction's xdr.TransactionResult, unwrapping a fee bump when there is one. It returns the same 72-character hex form as Transaction.getClaimableBalanceId(opIndex), which derives the ID before submission; use this one when you only have the result. Horizon's result_xdr is base64, so decode it first with xdr.TransactionResult.fromXdr(result_xdr, "base64"), while rpc.Server.getTransaction already returns a parsed resultXdr. It throws a RangeError for an out-of-range opIndex, and a TypeError when result is not a transaction result, when the transaction failed, or when the operation at opIndex is not a successful CreateClaimableBalance (#1719).

Fixed

  • Generated TypeScript bindings keep the raw spec name for a function parameter or struct field that is a reserved word or not a valid identifier, instead of renaming it: since #1345 a parameter new was typed as new_ while the runtime read new, so the typed call threw Missing field new, and a typed struct read of a renamed field was undefined. Methods and deploy now take a single args object, set(args: { new: number }, options?); call sites are unchanged, callers who used a renamed key switch to the raw name (new_ to new, _1st to args["1st"]), method names still get the trailing _, and a __constructor with no inputs now generates deploy(null, options) instead of deploy(options) (#1733).
  • Horizon call builders now confine a resource identifier to one URL path segment, so a / in it no longer opens a new segment. An identifier that is empty, ., .., or not a string/number/bigint throws a TypeError instead of re-pointing the request at a different endpoint — accountId("") previously reached the collection endpoint and returned a page of records, and accountId([".."]) resolved to the server root. Affects accountId(), transaction(), operation(), offer(), claimableBalance(), ledger(), liquidityPoolId(), loadAccount() and the for*() neighbor filters; liquidityPoolId() was reachable the same way because its hex check is unanchored, which is tracked separately in #1703. A decimal number or bigint identifier still works, and well-formed identifiers are unaffected, since no valid Stellar identifier contains /, ., ? or # (#1702).
  • These TypeErrors are thrown synchronously from call() and stream() rather than as a rejected promise, which matches the existing Too many filters specified error, so a caller that only attaches .catch() needs a try/catch. Three cases sit outside that, all unchanged by this release: loadAccount() is async, so it rejects and .catch() does work; liquidityPools().liquidityPoolId() throws from the builder method; and ledgers().ledger() with the forLedger() filters coerce the sequence with toString() first, so a nullish sequence throws there rather than reaching this guard (#1702).
  • Templated Horizon _links functions now apply the call builders' path-segment guard to a path variable. One that is empty, ., .., or not a string/number/bigint throws a TypeError instead of re-pointing the request at a different endpoint: account.data({ key: ".." }) previously requested the account endpoint, not the data endpoint. Query values are unaffected. AccountResponse.data() and the server.root() links both take the path variable through an option TypeScript does not declare, so no call that compiles today changes behavior (#1718).
  • StellarToml.Resolver.resolve() now validates the domain and throws Invalid domain before making a request (#1720). It previously put the string straight into the URL, so some inputs reached a different host, or a different path, than the caller named. A domain must be a plain host name with an optional port: credentials and an embedded /, ?, # or \ are rejected, as is an empty domain. Surrounding whitespace and a trailing / are stripped rather than rejected, so input that worked before keeps working. Host names, IP literals, IPv6 literals, and ports still work, but the request URL is normalized, so ACME.com is requested as acme.com.
  • Asset.fromOperation preserves the assetTypeCreditAlphanum12 union arm even when the decoded code is four characters or shorter, instead of re-deriving the arm from code length. Such an asset now re-encodes to the same XDR bytes it was decoded from, and its getAssetType(), contractId(), equals(), and Asset.compare() results reflect the alphanum12 arm. equals() now also compares the asset type, so a decoded short-code alphanum12 asset is no longer equal to the alphanum4 asset with the same code and issuer. User-constructed assets are unaffected: new Asset(code, issuer) still derives the type from code length (#1584).
  • rpc.Server.getContractData no longer reports a transport failure as a missing entry. It previously caught every error from the ledger lookup and rethrew { code: 404 }, so a 429, a 5xx, or a network error looked the same as an absent entry. Those errors now propagate untouched, and only a lookup that returns no entry throws the 404-shaped error, whose shape is unchanged (#1679).

Changed

  • HorizonApi.Predicate gains the unconditional and abs_before_epoch fields it previously omitted, so the type now describes every predicate Horizon serves (#1701). It stays an interface, so declaration merging still works. One case does break at compile time: a consumer who already augmented the namespace to declare unconditional or abs_before_epoch with a different type than the SDK now uses gets TS2717 and must drop that part of their augmentation.
  • Updated the production axios dependency from 1.18.0 to 1.20.0 (#1712).

New Contributors

Full Changelog: stellar/js-stellar-sdk@v17.0.1...v17.1.0

Changelog

Sourced from @​stellar/stellar-sdk's changelog.

v17.1.0

Changed

  • HorizonApi.Predicate gains the unconditional and abs_before_epoch fields it previously omitted, so the type now describes every predicate Horizon serves (#1701). It stays an interface, so declaration merging still works. One case does break at compile time: a consumer who already augmented the namespace to declare unconditional or abs_before_epoch with a different type than the SDK now uses gets TS2717 and must drop that part of their augmentation.
  • Updated the production axios dependency from 1.18.0 to 1.20.0 (#1712).

Added

  • getClaimableBalanceIdFromResult(result, opIndex): reads the claimable balance ID created by a CreateClaimableBalance operation out of a submitted transaction's xdr.TransactionResult, unwrapping a fee bump when there is one. It returns the same 72-character hex form as Transaction.getClaimableBalanceId(opIndex), which derives the ID before submission; use this one when you only have the result. Horizon's result_xdr is base64, so decode it first with xdr.TransactionResult.fromXdr(result_xdr, "base64"), while rpc.Server.getTransaction already returns a parsed resultXdr. It throws a RangeError for an out-of-range opIndex, and a TypeError when result is not a transaction result, when the transaction failed, or when the operation at opIndex is not a successful CreateClaimableBalance (#1719).

Fixed

  • Generated TypeScript bindings keep the raw spec name for a function parameter or struct field that is a reserved word or not a valid identifier, instead of renaming it: since #1345 a parameter new was typed as new_ while the runtime read new, so the typed call threw Missing field new, and a typed struct read of a renamed field was undefined. Methods and deploy now take a single args object, set(args: { new: number }, options?); call sites are unchanged, callers who used a renamed key switch to the raw name (new_ to new, _1st to args["1st"]), method names still get the trailing _, and a __constructor with no inputs now generates deploy(null, options) instead of deploy(options) (#1733).
  • Horizon call builders now confine a resource identifier to one URL path segment, so a / in it no longer opens a new segment. An identifier that is empty, ., .., or not a string/number/bigint throws a TypeError instead of re-pointing the request at a different endpoint — accountId("") previously reached the collection endpoint and returned a page of records, and accountId([".."]) resolved to the server root. Affects accountId(), transaction(), operation(), offer(), claimableBalance(), ledger(), liquidityPoolId(), loadAccount() and the for*() neighbor filters; liquidityPoolId() was reachable the same way because its hex check is unanchored, which is tracked separately in #1703. A decimal number or bigint identifier still works, and well-formed identifiers are unaffected, since no valid Stellar identifier contains /, ., ? or # (#1702).
  • These TypeErrors are thrown synchronously from call() and stream() rather than as a rejected promise, which matches the existing Too many filters specified error, so a caller that only attaches .catch() needs a try/catch. Three cases sit outside that, all unchanged by this release: loadAccount() is async, so it rejects and .catch() does work; liquidityPools().liquidityPoolId() throws from the builder method; and ledgers().ledger() with the forLedger() filters coerce the sequence with toString() first, so a nullish sequence throws there rather than reaching this guard (#1702).
  • Templated Horizon _links functions now apply the call builders' path-segment guard to a path variable. One that is empty, ., .., or not a string/number/bigint throws a TypeError instead of re-pointing the request at a different endpoint: account.data({ key: ".." }) previously requested the account endpoint, not the data endpoint. Query values are unaffected. AccountResponse.data() and the server.root() links both take the path variable through an option TypeScript does not declare, so no call that compiles today changes behavior (#1718).
  • StellarToml.Resolver.resolve() now validates the domain and throws Invalid domain before making a request (#1720). It previously put the string straight into the URL, so some inputs reached a different host, or a different path, than the caller named. A domain must be a plain host name with an optional port: credentials and an embedded /, ?, # or \ are rejected, as is an empty domain. Surrounding whitespace and a trailing / are stripped rather than rejected, so input that worked before keeps working. Host names, IP literals, IPv6 literals, and ports still work, but the request URL is normalized, so ACME.com is requested as acme.com.
  • Asset.fromOperation preserves the assetTypeCreditAlphanum12 union arm even when the decoded code is four characters or shorter, instead of re-deriving the arm from code length. Such an asset now re-encodes to the same XDR bytes it was decoded from, and its getAssetType(), contractId(), equals(), and Asset.compare() results reflect the alphanum12 arm. equals() now also compares the asset type, so a decoded short-code alphanum12 asset is no longer equal to the alphanum4 asset with the same code and issuer. User-constructed assets are unaffected: new Asset(code, issuer) still derives the type from code length (#1584).
  • rpc.Server.getContractData no longer reports a transport failure as a missing entry. It previously caught every error from the ledger lookup and rethrew { code: 404 }, so a 429, a 5xx, or a network error looked the same as an absent entry. Those errors now propagate untouched, and only a lookup that returns no entry throws the 404-shaped error, whose shape is unchanged (#1679).
Commits
  • e07ded5 chore(release): prepare v17.1.0 (#1735)
  • fc652a0 fix(bindings): use raw spec names as property keys in generated types (#1733)
  • 0e83a37 chore(deps): bump the minor-and-patch group across 1 directory with 13 update...
  • 9492b6a fix(horizon): complete HorizonApi.Predicate, document the SEP-0051 path (#1701)
  • 33cd064 fix(toml): keep a malformed domain from redirecting the request (#1720)
  • cb7d998 chore(deps): bump stellar/stellar-cli in the all-actions group (#1711)
  • 32a314f update contributing policy for external contributors (#1728)
  • f106d0e feat(base): read claimable balance IDs from transaction results (#1719)
  • 9330f2b fix: guard the path variables in templated Horizon links (#1718)
  • d79f361 fix: keep Horizon call builder ids in one URL path segment (#1702)
  • Additional commits viewable in compare view

Updates @tanstack/react-query from 5.102.8 to 5.103.1

Release notes

Sourced from @​tanstack/react-query's releases.

@​tanstack/react-query-devtools@​5.103.1

Patch Changes

  • Updated dependencies []:
    • @​tanstack/query-devtools@​5.103.1
    • @​tanstack/react-query@​5.103.1

@​tanstack/react-query-next-experimental@​5.103.1

Patch Changes

  • Updated dependencies []:
    • @​tanstack/react-query@​5.103.1

@​tanstack/react-query-persist-client@​5.103.1

Patch Changes

  • Updated dependencies []:
    • @​tanstack/query-persist-client-core@​5.103.1
    • @​tanstack/react-query@​5.103.1

@​tanstack/react-query@​5.103.1

Patch Changes

@​tanstack/react-query-devtools@​5.103.0

Patch Changes

  • #11501 9567367 - Declare dependencies used by the published devtools source and type declarations so they resolve with strict package managers. Keep runtime dependencies bundled in the compiled devtools.

    Declare the React types used by React Query Devtools as a peer dependency, compatible with React 18 and 19.

  • Updated dependencies [9567367]:

    • @​tanstack/query-devtools@​5.103.0
    • @​tanstack/react-query@​5.103.0

@​tanstack/react-query-next-experimental@​5.103.0

Patch Changes

  • Updated dependencies []:
    • @​tanstack/react-query@​5.103.0

@​tanstack/react-query-persist-client@​5.103.0

Patch Changes

  • Updated dependencies [4c7cdbb]:
    • @​tanstack/query-persist-client-core@​5.103.0
    • @​tanstack/react-query@​5.103.0

... (truncated)

Changelog

Sourced from @​tanstack/react-query's changelog.

5.103.1

Patch Changes

5.103.0

Patch Changes

Commits
  • c08f576 ci: Version Packages (#11511)
  • 19ccf27 ci: Version Packages (#11339)
  • 2da46cd chore(*): use eslint description syntax for grandfathered 'no-restricted-synt...
  • 58ad3e2 fix: isolate TypeScript test output (#11503)
  • d63afc7 Simplifed query methods/internal tests new lint (#11347)
  • 23fbdc3 test({react,preact,solid,angular}-query): remove 'fromGenericOptionsQueryFn' ...
  • 50680b9 test({react,preact,solid,svelte}-query,angular-query-experimental): rename 'm...
  • 0b326b6 test({react,preact}-query/useMutation): add tests for 'MutationFunctionContex...
  • a1119e5 ref(hydration): remove outdated dehydratedAt fallback (#11436)
  • 1a51bb8 docs(*): clarify 'Promise.all' only waits for all mutateAsync calls when they...
  • Additional commits viewable in compare view

Updates @tanstack/react-virtual from 3.14.10 to 3.14.13

Release notes

Sourced from @​tanstack/react-virtual's releases.

@​tanstack/react-virtual@​3.14.13

Patch Changes

  • #1282 b48e3b0 - Skip flushSync for the synchronous notify raised from measureElement. React calls measureElement from a ref callback, i.e. while it is committing, and flushSync cannot flush there — it warns in development instead. The commit phase already runs at discrete (sync) priority, so the update lands in the same lane and the same frame without flushSync. Notifies from every other path (ResizeObserver re-measures, scroll adjustments) still flush synchronously.

  • Updated dependencies [06d1b6b, 2c0a0ea]:

    • @​tanstack/virtual-core@​3.17.11

@​tanstack/react-virtual@​3.14.12

Patch Changes

  • Updated dependencies [ab3278c]:
    • @​tanstack/virtual-core@​3.17.10

@​tanstack/react-virtual@​3.14.11

Patch Changes

  • Updated dependencies [4a0adf3]:
    • @​tanstack/virtual-core@​3.17.9
Changelog

Sourced from @​tanstack/react-virtual's changelog.

3.14.13

Patch Changes

  • #1282 b48e3b0 - Skip flushSync for the synchronous notify raised from measureElement. React calls measureElement from a ref callback, i.e. while it is committing, and flushSync cannot flush there — it warns in development instead. The commit phase already runs at discrete (sync) priority, so the update lands in the same lane and the same frame without flushSync. Notifies from every other path (ResizeObserver re-measures, scroll adjustments) still flush synchronously.

  • Updated dependencies [06d1b6b, 2c0a0ea]:

    • @​tanstack/virtual-core@​3.17.11

3.14.12

Patch Changes

  • Updated dependencies [ab3278c]:
    • @​tanstack/virtual-core@​3.17.10

3.14.11

Patch Changes

  • Updated dependencies [4a0adf3]:
    • @​tanstack/virtual-core@​3.17.9
Commits
  • 78371e8 ci: Version Packages (#1279)
  • b48e3b0 fix(react-virtual): skip flushSync while measuring from the ref callback (#1282)
  • 1a57cf7 test(react-virtual): wait for smooth scrolls to settle instead of a fixed 2s ...
  • 2c0a0ea fix(virtual-core): keep a travelling smooth scroll alive through a prepend (#...
  • df47889 ci: Version Packages (#1277)
  • 171029d ci: Version Packages (#1269)
  • 4a0adf3 fix(virtual-core): re-issue clamped end-anchor compensation once the sizer gr...
  • See full diff in compare view

Updates next from 16.3.3 to 16.3.5

Release notes

Sourced from next's releases.

v16.3.5

The following bug fixes have been backported. It does not include all pending features/changes on canary.

  • next/image: Skip 0-byte entries when initializing disk LRU cache (#98185)
  • next/image: Reject empty images when reading/writing to the disk cache (#98186)
  • Emit whole-app server NFTs when output: 'standalone' is used with an adapter (#98167)
  • Add CSP nonce to script tags of loading and template files (#98403)
  • Fix use cache prerender signal retention (#98448)

v16.3.4

Follow-up release to v16.3.3 re-enabling AVIF Image Optimization (#97949).

The following bug fixes have been backported. It does not include all pending features/changes on canary.

  • testmode: Fix infinite recursion in testmode passthrough fetch (#97691)
  • Fix build error when aliasing typescript to @​typescript/typescript6 (#97997)
  • Fix unset crossOrigin in Turbopack manifests (#97930)

Credits

Huge thanks to @​eps1lon, @​mischnic, and @​timneutkens for helping!

Commits
  • ca2c75e v16.3.5
  • 14fb290 [backport] Fix use cache prerender signal retention (#98448)
  • 2b1f28d [16.3.x] Add CSP nonce to script tags of loading and template files (#98403)
  • 4b56cee [16.3.x] Backport docs fixes (#98317)
  • 5568a02 [backport] docs: local development: Rewrite docker section, add Windows Dev D...
  • 93249ab [16.3.X] Emit whole-app server NFTs when output: 'standalone' is used with ...
  • 6549fd7 [16.3.x] next/image: reject empty image on read/write to disk cache (#98186)
  • d9eac96 [16.3.x] next/image: skip 0-byte entries when initializing disk LRU cache (#9...
  • 84b35fe [test] Fix 16.3 deploy test assertions (#98133)
  • 14f9c1a [16.3.x][ci] Run flake detection and new deploy tests when merged and on back...
  • Additional commits viewable in compare view

Updates react from 19.2.7 to 19.3.0

Release notes

Sourced from react's releases.

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

@dependabot
chore(deps): bump the minor-and-patch group across 1 directory with 1…
b8a69d3 
…8 updates

Bumps the minor-and-patch group with 18 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [react-hot-toast](https://github.com/timolins/react-hot-toast) | `2.6.0` | `2.6.1` |
| [lint-staged](https://github.com/lint-staged/lint-staged) | `17.4.1` | `17.5.1` |
| [@rollup/rollup-linux-x64-gnu](https://github.com/rollup/rollup) | `4.63.1` | `4.63.3` |
| [@stellar/stellar-sdk](https://github.com/stellar/js-stellar-sdk) | `17.0.1` | `17.1.0` |
| [@tanstack/react-query](https://github.com/TanStack/query/tree/HEAD/packages/react-query) | `5.102.8` | `5.103.1` |
| [@tanstack/react-virtual](https://github.com/TanStack/virtual/tree/HEAD/packages/react-virtual) | `3.14.10` | `3.14.13` |
| [next](https://github.com/vercel/next.js) | `16.3.3` | `16.3.5` |
| [react](https://github.com/react/react/tree/HEAD/packages/react) | `19.2.7` | `19.3.0` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.2.18` | `19.3.0` |
| [react-dom](https://github.com/react/react/tree/HEAD/packages/react-dom) | `19.2.7` | `19.3.0` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `19.2.5` | `19.3.0` |
| [@eslint/eslintrc](https://github.com/eslint/eslintrc) | `3.3.6` | `3.3.7` |
| [@testing-library/dom](https://github.com/testing-library/dom-testing-library) | `10.4.1` | `10.4.2` |
| [@testing-library/user-event](https://github.com/testing-library/user-event) | `14.6.6` | `14.6.7` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.2.18` | `19.3.0` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `19.2.5` | `19.3.0` |
| [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) | `16.3.3` | `16.3.5` |
| [happy-dom](https://github.com/capricorn86/happy-dom) | `20.12.0` | `20.14.5` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.62.1` | `1.63.0` |
| [zod](https://github.com/colinhacks/zod) | `4.5.4` | `4.6.5` |



Updates `react-hot-toast` from 2.6.0 to 2.6.1
- [Release notes](https://github.com/timolins/react-hot-toast/releases)
- [Commits](timolins/react-hot-toast@v2.6.0...v2.6.1)

Updates `lint-staged` from 17.4.1 to 17.5.1
- [Release notes](https://github.com/lint-staged/lint-staged/releases)
- [Changelog](https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md)
- [Commits](lint-staged/lint-staged@v17.4.1...v17.5.1)

Updates `@rollup/rollup-linux-x64-gnu` from 4.63.1 to 4.63.3
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.63.1...v4.63.3)

Updates `@stellar/stellar-sdk` from 17.0.1 to 17.1.0
- [Release notes](https://github.com/stellar/js-stellar-sdk/releases)
- [Changelog](https://github.com/stellar/js-stellar-sdk/blob/main/CHANGELOG.md)
- [Commits](stellar/js-stellar-sdk@v17.0.1...v17.1.0)

Updates `@tanstack/react-query` from 5.102.8 to 5.103.1
- [Release notes](https://github.com/TanStack/query/releases)
- [Changelog](https://github.com/TanStack/query/blob/main/packages/react-query/CHANGELOG.md)
- [Commits](https://github.com/TanStack/query/commits/@tanstack/react-query@5.103.1/packages/react-query)

Updates `@tanstack/react-virtual` from 3.14.10 to 3.14.13
- [Release notes](https://github.com/TanStack/virtual/releases)
- [Changelog](https://github.com/TanStack/virtual/blob/main/packages/react-virtual/CHANGELOG.md)
- [Commits](https://github.com/TanStack/virtual/commits/@tanstack/react-virtual@3.14.13/packages/react-virtual)

Updates `next` from 16.3.3 to 16.3.5
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.3.3...v16.3.5)

Updates `react` from 19.2.7 to 19.3.0
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.3.0/packages/react)

Updates `@types/react` from 19.2.18 to 19.3.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `react-dom` from 19.2.7 to 19.3.0
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.3.0/packages/react-dom)

Updates `@types/react-dom` from 19.2.5 to 19.3.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `@eslint/eslintrc` from 3.3.6 to 3.3.7
- [Release notes](https://github.com/eslint/eslintrc/releases)
- [Changelog](https://github.com/eslint/eslintrc/blob/main/CHANGELOG.md)
- [Commits](eslint/eslintrc@eslintrc-v3.3.6...eslintrc-v3.3.7)

Updates `@testing-library/dom` from 10.4.1 to 10.4.2
- [Release notes](https://github.com/testing-library/dom-testing-library/releases)
- [Changelog](https://github.com/testing-library/dom-testing-library/blob/main/CHANGELOG.md)
- [Commits](testing-library/dom-testing-library@v10.4.1...v10.4.2)

Updates `@testing-library/user-event` from 14.6.6 to 14.6.7
- [Release notes](https://github.com/testing-library/user-event/releases)
- [Changelog](https://github.com/testing-library/user-event/blob/main/CHANGELOG.md)
- [Commits](testing-library/user-event@v14.6.6...v14.6.7)

Updates `@types/react` from 19.2.18 to 19.3.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `@types/react-dom` from 19.2.5 to 19.3.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `eslint-config-next` from 16.3.3 to 16.3.5
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](https://github.com/vercel/next.js/commits/v16.3.5/packages/eslint-config-next)

Updates `happy-dom` from 20.12.0 to 20.14.5
- [Release notes](https://github.com/capricorn86/happy-dom/releases)
- [Commits](capricorn86/happy-dom@v20.12.0...v20.14.5)

Updates `@playwright/test` from 1.62.1 to 1.63.0
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.62.1...v1.63.0)

Updates `zod` from 4.5.4 to 4.6.5
- [Release notes](https://github.com/colinhacks/zod/releases)
- [Commits](colinhacks/zod@v4.5.4...v4.6.5)

---
updated-dependencies:
- dependency-name: react-hot-toast
  dependency-version: 2.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: lint-staged
  dependency-version: 17.5.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@rollup/rollup-linux-x64-gnu"
  dependency-version: 4.63.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: "@stellar/stellar-sdk"
  dependency-version: 17.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@tanstack/react-query"
  dependency-version: 5.103.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@tanstack/react-virtual"
  dependency-version: 3.14.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: next
  dependency-version: 16.3.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: react
  dependency-version: 19.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@types/react"
  dependency-version: 19.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: react-dom
  dependency-version: 19.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@types/react-dom"
  dependency-version: 19.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@eslint/eslintrc"
  dependency-version: 3.3.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: "@testing-library/dom"
  dependency-version: 10.4.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: "@testing-library/user-event"
  dependency-version: 14.6.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: "@types/react"
  dependency-version: 19.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@types/react-dom"
  dependency-version: 19.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: eslint-config-next
  dependency-version: 16.3.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: happy-dom
  dependency-version: 20.14.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@playwright/test"
  dependency-version: 1.63.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: zod
  dependency-version: 4.6.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 21, 2026
@dependabot dependabot Bot mentioned this pull request Sep 21, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants