Skip to content

chore(deps): bump the prod-dependencies group across 1 directory with 6 updates - #19

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/prod-dependencies-1c2f992f12
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/prod-dependencies-1c2f992f12

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps the prod-dependencies group with 6 updates in the / directory:

Package From To
near-api-js 7.4.0 7.5.3
@noble/curves 2.2.0 2.4.0
@noble/hashes 2.2.0 2.4.0
@tanstack/react-query 5.64.2 5.107.1
react 19.0.0 19.3.1
react-dom 19.0.0 19.3.1

Updates near-api-js from 7.4.0 to 7.5.3

Release notes

Sourced from near-api-js's releases.

near-api-js@7.5.1

Patch Changes

  • #2040 7162d13 Thanks @​irondevrel! - Add optional limit and afterKey parameters to Account.getAccessKeyList() so callers can paginate access keys on accounts exceeding the RPC node's unpaginated key limit. Existing no-argument calls and the single-page return shape are preserved.

near-api-js@7.5.0

Minor Changes

  • #2032 85af012 Thanks @​irondevrel! - Add NEP-616 deterministic account support: canonical state-init encoding and account-ID derivation, the DeterministicStateInit transaction action, and Account.createDeterministicAccount(). Storage deposits cover storage staking and refund any excess; they do not fund the account's spending balance.

  • #2036 f1f5621 Thanks @​irondevrel! - Expose global contract references from Account.getState() and add decodeSignedDelegate() for Borsh-encoded meta transactions.

    Export SignedDelegate with encode() and decode() methods, reject trailing bytes and nested or reserved delegate tags when decoding signed delegates, and restore Signature instances when decoding signed transactions.

  • #2034 227824b Thanks @​irondevrel! - Update generated RPC types and exhaustive error handling to the official nearcore 2.14.0 OpenAPI schema. Add access-key pagination parameters and expose the new account-view fields.

  • #2035 0c2dca5 Thanks @​irondevrel! - Add protocol-88 universal account support, including canonical state-init construction, raw-byte account ID derivation, the UniversalStateInit action, bootstrap nonces, and nearcore 2.14 RPC types and errors.

Patch Changes

  • #2029 799f5ad Thanks @​irondevrel! - Accept RPC base58 code hashes in global-contract use actions while preserving 64-character hexadecimal and raw-byte inputs. Encode raw-byte hashes as base58 when querying global contract code.
Changelog

Sourced from near-api-js's changelog.

7.5.3

Patch Changes

  • #2055 40a2741 Thanks @​irondevrel! - Clarify public API documentation for transaction execution, signing, token amounts and registration, key encodings, and state initialization. Document read-after-write consistency considerations for RPC endpoints with multiple backends. No runtime behavior changes.

7.5.2

Patch Changes

  • #2052 d42272c Thanks @​irondevrel! - Recognize nearcore's flattened contract panic messages as HostGuestPanicError, exposing panicMessage consistently with structured guest panic errors.

7.5.1

Patch Changes

  • #2040 7162d13 Thanks @​irondevrel! - Add optional limit and afterKey parameters to Account.getAccessKeyList() so callers can paginate access keys on accounts exceeding the RPC node's unpaginated key limit. Existing no-argument calls and the single-page return shape are preserved.

7.5.0

Minor Changes

  • #2032 85af012 Thanks @​irondevrel! - Add NEP-616 deterministic account support: canonical state-init encoding and account-ID derivation, the DeterministicStateInit transaction action, and Account.createDeterministicAccount(). Storage deposits cover storage staking and refund any excess; they do not fund the account's spending balance.

  • #2036 f1f5621 Thanks @​irondevrel! - Expose global contract references from Account.getState() and add decodeSignedDelegate() for Borsh-encoded meta transactions.

    Export SignedDelegate with encode() and decode() methods, reject trailing bytes and nested or reserved delegate tags when decoding signed delegates, and restore Signature instances when decoding signed transactions.

  • #2034 227824b Thanks @​irondevrel! - Update generated RPC types and exhaustive error handling to the official nearcore 2.14.0 OpenAPI schema. Add access-key pagination parameters and expose the new account-view fields.

  • #2035 0c2dca5 Thanks @​irondevrel! - Add protocol-88 universal account support, including canonical state-init construction, raw-byte account ID derivation, the UniversalStateInit action, bootstrap nonces, and nearcore 2.14 RPC types and errors.

Patch Changes

  • #2029 799f5ad Thanks @​irondevrel! - Accept RPC base58 code hashes in global-contract use actions while preserving 64-character hexadecimal and raw-byte inputs. Encode raw-byte hashes as base58 when querying global contract code.
Commits

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

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

Updates @tanstack/react-query from 5.64.2 to 5.107.1

Release notes

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

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

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

@​tanstack/react-query@​5.107.1

Patch Changes

  • Updated dependencies []:
    • @​tanstack/query-core@​5.107.1

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

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

@​tanstack/react-query@​5.107.0

Patch Changes

... (truncated)

Changelog

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

5.107.1

Patch Changes

  • Updated dependencies []:
    • @​tanstack/query-core@​5.107.1

5.107.0

Patch Changes

  • Updated dependencies [b6add89]:
    • @​tanstack/query-core@​5.107.0

5.106.1

Patch Changes

  • Updated dependencies []:
    • @​tanstack/query-core@​5.106.1

5.106.0

Patch Changes

  • Updated dependencies []:
    • @​tanstack/query-core@​5.106.0

5.105.3

Patch Changes

5.105.2

Patch Changes

  • #12230 1e1caa5 - Update the observer options before subscribing so revealing an <Activity> tree whose query key changed while hidden no longer fetches the previous key.

  • #12480 8d0dc27 - Exclude status from the filters accepted by QueryClient.isMutating, useIsMutating, and injectIsMutating. These APIs always count mutations with status: 'pending'.

  • Updated dependencies [2ee2fd9, 8d0dc27, e69cac6, f2215d2, 86e7957, b6576b3, af0e0ef, 05d9b6a]:

    • @​tanstack/query-core@​5.105.2

5.105.1

Patch Changes

  • #11373 7ccba6e - fix({react,preact,angular,solid,vue}-query/infiniteQueryOptions): correct the overload selected for a possibly-undefined 'initialData'

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​tanstack/react-query since your current version.


Updates react from 19.0.0 to 19.3.1

Release notes

Sourced from react's releases.

19.3.1 (October 14th, 2026)

React Server Components

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

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

All Changes

React

  • Fast Refresh Fixes
  • 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

... (truncated)

Changelog

Sourced from react's changelog.

19.3.0 (September 9, 2026)

New React Features

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

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 c...

      Description has been truncated

… 6 updates

Bumps the prod-dependencies group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [near-api-js](https://github.com/near/near-api-js) | `7.4.0` | `7.5.3` |
| [@noble/curves](https://github.com/paulmillr/noble-curves) | `2.2.0` | `2.4.0` |
| [@noble/hashes](https://github.com/paulmillr/noble-hashes) | `2.2.0` | `2.4.0` |
| [@tanstack/react-query](https://github.com/TanStack/query/tree/HEAD/packages/react-query) | `5.64.2` | `5.107.1` |
| [react](https://github.com/react/react/tree/HEAD/packages/react) | `19.0.0` | `19.3.1` |
| [react-dom](https://github.com/react/react/tree/HEAD/packages/react-dom) | `19.0.0` | `19.3.1` |



Updates `near-api-js` from 7.4.0 to 7.5.3
- [Release notes](https://github.com/near/near-api-js/releases)
- [Changelog](https://github.com/near/near-api-js/blob/master/CHANGELOG.md)
- [Commits](https://github.com/near/near-api-js/commits)

Updates `@noble/curves` from 2.2.0 to 2.4.0
- [Release notes](https://github.com/paulmillr/noble-curves/releases)
- [Changelog](https://github.com/paulmillr/noble-curves/blob/main/CHANGELOG.md)
- [Commits](paulmillr/noble-curves@2.2.0...2.4.0)

Updates `@noble/hashes` from 2.2.0 to 2.4.0
- [Release notes](https://github.com/paulmillr/noble-hashes/releases)
- [Changelog](https://github.com/paulmillr/noble-hashes/blob/main/CHANGELOG.md)
- [Commits](paulmillr/noble-hashes@2.2.0...2.4.0)

Updates `@tanstack/react-query` from 5.64.2 to 5.107.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.107.1/packages/react-query)

Updates `react` from 19.0.0 to 19.3.1
- [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.1/packages/react)

Updates `react-dom` from 19.0.0 to 19.3.1
- [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.1/packages/react-dom)

---
updated-dependencies:
- dependency-name: near-api-js
  dependency-version: 7.5.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-dependencies
- dependency-name: "@noble/curves"
  dependency-version: 2.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-dependencies
- dependency-name: "@noble/hashes"
  dependency-version: 2.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-dependencies
- dependency-name: "@tanstack/react-query"
  dependency-version: 5.107.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-dependencies
- dependency-name: react
  dependency-version: 19.3.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-dependencies
- dependency-name: react-dom
  dependency-version: 19.3.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added automated Bot-created PRs dependencies Dependency update PRs labels Nov 16, 2026
@github-actions github-actions Bot added frontend Web application and user interface backend Backend services, indexer, or APIs labels Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Bot-created PRs backend Backend services, indexer, or APIs dependencies Dependency update PRs frontend Web application and user interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants