Skip to content

chore(deps): update node dependencies (major)#794

Open
loopingz wants to merge 1 commit into
mainfrom
renovate/major-node-dependencies
Open

chore(deps): update node dependencies (major)#794
loopingz wants to merge 1 commit into
mainfrom
renovate/major-node-dependencies

Conversation

@loopingz
Copy link
Copy Markdown
Contributor

@loopingz loopingz commented Jan 14, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
@hono/node-server dependencies major ^1.19.5 → ^2.0.2
@hono/node-server@<1.19.10 pnpm.overrides major ^1.19.10 → ^2.0.2
@rollup/plugin-commonjs (source) devDependencies major ^28.0.8 → ^29.0.2
@rollup/plugin-commonjs (source) devDependencies major ^28.0.3 → ^29.0.2
@rollup/plugin-terser (source) devDependencies major ^0.4.4 → ^1.0.0
@smithy/types (source) devDependencies major ^3.7.2 → ^4.14.1
@types/koa (source) devDependencies major ^2.15.0 → ^3.0.2
@types/node (source) devDependencies major ^24.1.0 → ^25.7.0
@types/node (source) dependencies major ^24.1.0 → ^25.7.0
@types/node (source) devDependencies major ^24.1.0 → ^25.7.0
@types/node (source) pnpm.overrides major ^24.1.0 → ^25.7.0
@vertesia/client (source) dependencies major 0.82.1 → 1.2.0
ajv@>=6.0.0 <6.14.0 (source) pnpm.overrides major [^6.14.0 → ^8.20.0](https://renovatebot.com/diffs/npm/ajv@>=6.0.0 <6.14.0/6.14.0/8.20.0)
ansi-escapes dependencies major ^6.2.0 → ^7.3.0
brace-expansion@>=1.0.0 <2.0.0 pnpm.overrides major [^1.1.12 → ^5.0.6](https://renovatebot.com/diffs/npm/brace-expansion@>=1.0.0 <2.0.0/1.1.12/5.0.6)
brace-expansion@>=2.0.0 <3.0.0 pnpm.overrides major [^2.0.2 → ^5.0.6](https://renovatebot.com/diffs/npm/brace-expansion@>=2.0.0 <3.0.0/2.0.2/5.0.6)
cli-spinners dependencies major ^2.9.1 → ^3.4.0
cross-spawn@<6.0.6 pnpm.overrides major ^6.0.6 → ^7.0.6
debounce dependencies major ^2.2.0 → ^3.0.0
diff@>=4.0.0 <5.0.0 pnpm.overrides major [^4.0.4 → ^9.0.0](https://renovatebot.com/diffs/npm/diff@>=4.0.0 <5.0.0/4.0.4/9.0.0)
diff@>=5.0.0 <5.2.2 pnpm.overrides major [^5.2.2 → ^9.0.0](https://renovatebot.com/diffs/npm/diff@>=5.0.0 <5.2.2/5.2.2/9.0.0)
diff@>=6.0.0 <8.0.3 pnpm.overrides major [^8.0.3 → ^9.0.0](https://renovatebot.com/diffs/npm/diff@>=6.0.0 <8.0.3/8.0.3/9.0.0)
dotenv dependencies major ^16.6.1 → ^17.4.2
eventsource dependencies major ^3.0.6 → ^4.1.0
eventsource-parser dependencies major ^1.1.1 → ^3.0.8
firebase (source, changelog) dependencies major ^10.12.2 → ^12.13.0
glob dependencies major ^11.1.0 → ^13.0.6
glob@>=10.2.0 <10.5.0 pnpm.overrides major [^10.5.0 → ^13.0.6](https://renovatebot.com/diffs/npm/glob@>=10.2.0 <10.5.0/10.5.0/13.0.6)
jws@>=3.0.0 <3.2.3 pnpm.overrides major [^3.2.3 → ^4.0.1](https://renovatebot.com/diffs/npm/jws@>=3.0.0 <3.2.3/3.2.3/4.0.1)
log-update dependencies major ^6.1.0 → ^8.0.0
mocha (source) devDependencies major ^10.2.0 → ^11.7.5
open dependencies major ^10.1.0 → ^11.0.0
ora dependencies major ^8.2.0 → ^9.4.0
p-limit dependencies major ^6.2.0 → ^7.3.0
picomatch@<2.3.2 pnpm-workspace.overrides major ^2.3.2 → ^4.0.4
picomatch@<2.3.2 pnpm.overrides major ^2.3.2 → ^4.0.4
protobufjs@<7.5.6 pnpm.overrides major ^7.5.6 → ^8.3.0
rimraf devDependencies major ^5.0.5 → ^6.1.3
ts-md5 dependencies major ^1.3.1 → ^2.0.1
undici@>=6.0.0 <6.21.3 (source) pnpm.overrides major [^7.24.1 → ^8.2.0](https://renovatebot.com/diffs/npm/undici@>=6.0.0 <6.21.3/7.24.1/8.2.0)
uuid@>=11.0.0 <11.1.1 pnpm.overrides major [^11.1.1 → ^14.0.0](https://renovatebot.com/diffs/npm/uuid@>=11.0.0 <11.1.1/11.1.1/14.0.0)
zod (source) dependencies major ^3.24.1 → ^4.4.3

Release Notes

honojs/node-server (@​hono/node-server)

v2.0.2

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.0.1...v2.0.2

v2.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/node-server@v2.0.0...v2.0.1

v2.0.0

Compare Source

Now, we release the second major version of the Hono Node.js adapter 🎉 🎉 🎉

The Hono Node.js adapter is now up to 2.3x faster

v2 of the Hono Node.js adapter reaches up to 2.3x the throughput of v1 — that's the peak number, measured on the body-parsing scenario of bun-http-framework-benchmark. The other scenarios (Ping, Query) get a smaller but real boost too.

Install or upgrade with:

npm i @&#8203;hono/node-server@latest
v2

The Node.js adapter is going through a major version bump to v2. That said, the public API stays the same — the headline of this release is the large performance improvement described above.

What does the Node.js adapter do?

A quick refresher on what the Node.js adapter actually does — it exists so that Hono applications can run on Node.js. Hono is built on the Web Standards APIs, but you cannot serve those directly from Node.js. The adapter bridges the Web Standards APIs and the Node.js APIs, which is what lets a Hono app — and more generally a Web-Standards-style app — run on top of Node.js.

If you write the following code and run node ./index.js, a server starts up on localhost:3000. And it really is plain Node.js underneath.

import { Hono } from 'hono'
import { serve } from '@&#8203;hono/node-server'

const app = new Hono()
app.get('/', (c) => c.text('Hello World!'))

serve(app)
The early performance story

The very first implementation of the Node.js adapter looked roughly like this in pseudocode:

export const getRequestListener = (fetchCallback: FetchCallback) => {
  return async (incoming: IncomingMessage, outgoing: ServerResponse) => {
    const method = incoming.method || 'GET'
    const url = `http://${incoming.headers.host}${incoming.url}`

    // ...

    const init = {
      method: method,
      headers: headerRecord,
    }

    // app is a Hono application
    const res = await app.fetch(new Request(url, init))
    const buffer = await res.arrayBuffer()
    outgoing.writeHead(res.status, resHeaderRecord)
    outgoing.end(new Uint8Array(buffer))
  }
}

So the flow was:

  • a request comes in as an IncomingMessage
  • it gets converted into a Request object and handed to the app
  • the Response returned by the app is written back to the outgoing ServerResponse

In diagram form:

IncomingMessage => Request => app => Response => ServerResponse

This is, frankly, inefficient. So whenever Hono went head-to-head with other Node.js frameworks we kept losing — all we could do was shrug and say "well, it's slow on Node.js."

Introducing LightweightRequest / LightweightResponse

The huge step forward that fixed this was a legendary PR from @​usualoma:

#​95

It made things up to 2.7x faster.

SS

I previously wrote about this in detail in this post:

https://zenn.dev/yusukebe/articles/7ac501716ae1f7?locale=en

In short, the trick is wonderfully simple. It just follows the golden rule of performance tuning: don't do work you don't have to do. Lightweight versions of Request and Response are constructed and used first — and that path is fast. Only when something actually needs the contents of the Request, e.g. when you call req.json(), does a real new Request() get instantiated under the hood and used from then on. The result is fast, and behavior stays correct.

…but body parsing was still slow

"Fast" here was for a very simple "Hello World" benchmark — a GET that just returns text.

There are many ways to benchmark, but the one we tend to reach for is this:

https://github.com/SaltyAom/bun-http-framework-benchmark

It tests three scenarios: Ping, Query, and Body. Let's pit Hono against the major Node.js frameworks:

SS

As you can see, the Body case is very slow. The handler being measured is essentially this:

import { Hono } from 'hono'
import { serve } from '@&#8203;hono/node-server'

const app = new Hono()

app.post('/json', async (c) => {
  const data = await c.req.json()
  return c.json(data)
})

serve(app)

c.req.json() is the slow part. The reason is well understood: inside the Node.js adapter, when json() is called the LightweightRequest path can't be used, so a real new Request() ends up being constructed.

perf: optimize request body reading

The 2.3x figure above comes from one PR specifically — PR #​301 by @​mgcrea:

The PR bundles a few changes, but the key one is "optimize request body reading". Quoting from the PR description:

The fix overrides text(), json(), arrayBuffer(), and blob() on the request prototype to read directly from the Node.js IncomingMessage using event-based I/O.

In other words, in the json() case above, we no longer convert into a Request at all — we read the body straight off the Node.js APIs. A classic fast path. That alone gives a large jump in body-parsing throughput.

The same PR also includes two other tuning improvements:

  • URL construction fast-path — skip building a URL object except in edge cases
  • buildOutgoingHttpHeaders optimization — skip the set-cookie header comparison when there are no cookies

v2 ships several other performance PRs as well — newHeadersFromIncoming and signal fast-paths, Response fast-paths and responseViaCache improvements, method-key caching, a regex-based buildUrl rewrite, and more (see the full list below). They all add up, but #​301 is by far the largest single contributor, which is why it gets the spotlight here.

v2 performance

Now let's measure the final v2 build.

First, comparing against the v1 Node.js adapter. dev here is v2. Body improves by 2.3x, and the other scenarios get faster too:

SS

Next, the same comparison against other frameworks. With the Body score jumping, Hono passes Koa and Fastify and takes first place:

SS

[!CAUTION]
Updated: The h3 entry in the earlier framework comparison was an older snapshot. Its successor srvx now ships a FastResponse mode, and in srvx's own benchmark (h3js/srvx/test/bench-node) srvx-fast (≈68,560 req/sec) beats hono-fast (≈59,477 req/sec). The methodology is different from the benchmarks above, but worth being upfront: with FastResponse enabled, srvx is faster than Hono v2 in that setup.

Breaking changes

There are two breaking changes in v2.

Dropped support for Node.js v18

Node.js v18 reached end-of-life, so v2 requires Node.js v20 or later.

Removed the Vercel adapter

The Vercel adapter (@hono/node-server/vercel) has been removed. It is no longer needed for Vercel's modern runtimes, so the recommendation is to deploy without it.

If you still need the previous behavior, the old adapter was a one-liner on top of getRequestListener and you can write the same thing in your own project:

import type { Hono } from 'hono'
import { getRequestListener } from '@&#8203;hono/node-server'

export const handle = (app: Hono) => {
  return getRequestListener(app.fetch)
}

Then use it the same way you used handle from @hono/node-server/vercel before.

All changes

A full list of what landed in PR #​316.

Performance
Features
Breaking changes
Fixes & refactors
Build & tooling
Wrap-up

So that's v2 of the Node.js adapter — significantly faster, with the same API. Just upgrading should give you a real performance boost. No more "Hono is slow on Node.js" excuses. Please use Hono — fast not only on Cloudflare, Bun, and Deno, but now also on Node.js.

v1.19.14

Compare Source

What's Changed
  • fix: add custom inspect to lightweight Request/Response to prevent TypeError on console.log by @​usualoma in #​340

Full Changelog: honojs/node-server@v1.19.13...v1.19.14

rollup/plugins (@​rollup/plugin-commonjs)

v29.0.2

2026-03-06

Bugfixes
  • commonjs: conditional exports (#​1952)

v29.0.1

2026-03-05

Bugfixes
  • commonjs: correctly replaces shorthand "global" property in object (#​1957)

v29.0.0

2025-10-30

Breaking Changes
rollup/plugins (@​rollup/plugin-terser)

v1.0.0

2026-03-05

Breaking Changes
  • terser!: upgrade serialize-javascript to v7 and node to v20 (#​1968)
smithy-lang/smithy-typescript (@​smithy/types)

v4.14.1

Compare Source

Patch Changes
  • 131fce4: add eventStream indicator signal for NodeHttp2ConnectionManager so it does not reuse connections for event streams
  • 52b4789: allow snapshot of credentials for event-stream signing

v4.14.0

Compare Source

Minor Changes
  • cffd868: Introduce default retry behavior modifications slated for 2026. They are:
    less time between server error retries, but slightly more time between throttling errors. Lower retry capacity consumption for throttling, and improved parsing of the retry-after and x-amz-retry-after headers.

v4.13.1

Compare Source

Patch Changes
  • 5340b11: apply resolved endpoint headers to final request

v4.13.0

Compare Source

Minor Changes
  • d0954cc: allow adding new checksum algorithms via extension

v4.12.1

Compare Source

Patch Changes
  • 03c3dc8: update for rollup build externalLiveBindings=false

v4.12.0

Compare Source

Minor Changes
  • 745867a: encode required member count in structure schemas

v4.11.0

Compare Source

Minor Changes
  • 9ccb841: add static union schema as a new type

v4.10.0

Compare Source

Minor Changes
  • 5a56762: make protocol selection easier

v4.9.0

Compare Source

Minor Changes
  • 3926fd7: set release level for schemas

v4.8.1

Compare Source

Patch Changes

v4.8.0

Compare Source

Minor Changes
  • 8a2a912: remove usage of non-static schema classes

v4.7.1

Compare Source

Patch Changes
  • 052d261: fix ordering of static simple schema type

v4.7.0

Compare Source

Minor Changes
  • 761d89c: undeprecate socketTimeout for node:https requests
  • 7f8af58: generation of static schema

v4.6.0

Compare Source

Minor Changes
  • 45ee67f: update dist-cjs generation to use rollup

v4.5.0

Compare Source

Minor Changes
  • bb7c1c1: schema code size optimizations

v4.4.0

Compare Source

Minor Changes
  • 64cda93: set sideEffects bundler metadata
Patch Changes
  • f884df7: enforce consistent-type-imports

v4.3.2

Compare Source

Patch Changes
  • 64e033f: schema serde: http binding and cbor serializer refactoring

v4.3.1

Compare Source

Patch Changes
  • 358c1ff: fix Command interface compatibility with type transformers

v4.3.0

Compare Source

Minor Changes

v4.2.0

Compare Source

Minor Changes
  • e917e61: enforce singular config object during client instantiation

v4.1.0

Compare Source

Minor Changes
  • 2aff9df: Added middleware support to pagination
  • 000b2ae: allow paginator token fallback to be specified by operation input

v4.0.0

Compare Source

Major Changes
  • 20d99be: major version bump for dropping node16 support
vertesia/composableai (@​vertesia/client)

v1.2.0

Compare Source

v1.1.0

Compare Source

v1.0.0

Compare Source

v0.82.4

Compare Source

v0.82.3

Compare Source

v0.82.2

Compare Source

ajv-validator/ajv (ajv@>=6.0.0 <6.14.0)

v8.20.0

Compare Source

What's Changed

Full Changelog: ajv-validator/ajv@v8.19.0...v8.20.0

v8.18.0

Compare Source

What's Changed

New Contributors

Full Changelog: ajv-validator/ajv@v8.17.1...v8.18.0

v8.17.1

Compare Source

What's Changed

Full Changelog: ajv-validator/ajv@v8.17.0...v8.17.1

Plus everything in 8.17.0 which failed to release

The only functional change is to switch from uri-js (which is no longer supported), to fast-uri. This is the second attempt and the team on fast-uri have been really helpful addressing the issues we found last time.

Revert "Revert fast-uri change (#​2444)" by @​gurgunday in #​2448
fix: ignore new eslint error for @​typescript-eslint/no-extraneous-class by @​jasoniangreen in #​2455
docs: clarify behaviour of addVocabulary by @​jasoniangreen in #​2454
docs: refactor to improve legibility by @​blottn in #​2432
Fix grammatical typo in managing-schemas.md by @​wetneb in #​2305
docs: Fix broken strict-mode link by @​alexanderjsx in #​2459
feat: add test for encoded refs and bump fast-uri by @​jasoniangreen in #​2449
fix: changes for @​typescript-eslint/array-type rule by @​jasoniangreen in #​2467
fixes #​2217 - clarify custom keyword naming by @​jasoniangreen in #​2457

v8.16.0

Compare Source

What's Changed

Full Changelog: ajv-validator/ajv@v8.15.0...v8.16.0

v8.15.0

Compare Source

What's Changed

New Contributors

Full Changelog: ajv-validator/ajv@v8.14.0...v8.15.0

v8.14.0

Compare Source

What's Changed

New Contributors

Full Changelog: ajv-validator/ajv@v8.13.0...v8.14.0

v8.13.0

Compare Source

  • add named exports
  • update dependencies
  • update node.js

v8.12.0

Compare Source

v8.11.2

Compare Source

Update dependencies

Export ValidationError and MissingRefError (#​1840, @​dannyb648)

v8.11.1

Compare Source

Update dependencies

Export ValidationError and MissingRefError (#​1840, @​dannyb648)

v8.11.0

Compare Source

Use root schemaEnv when resolving references in oneOf (#​1901, @​asprouse)

Only use equal function in generated code when it is used (#​1922, @​bhvngt)

v8.10.0

Compare Source

uriResolver option (@​zekth, #​1862)

v8.9.0

Compare Source

Option code.esm to generate ESM exports for standalone validation functions (@​rehanvdm, #​1861)
Support discriminator keyword with $ref in oneOf subschemas (@​dfeufel, #​1815)

v8.8.2

Compare Source

Use full RegExp string (with flags) as cache key, related to ajv-validator/ajv-keywords#220

v8.8.1

Compare Source

Fix minContains: 0 (#​1819)

v8.8.0

Compare Source

Fix browser bundles in cdnjs
regExp option allowing to specify alternative RegExp engine, e.g. re2 (@​efebarlas)

v8.7.1

Compare Source

Publish Ajv bundle for JSON Schema 2020-12 to cdnjs.com

v8.7.0

Compare Source

Update JSON Schema Test Suite.
Change minContains: 0 now correctly allows empty array.

v8.6.3

Compare Source

Fix $ref resolution for schemas without $id (@​rbuckton, #​1725)
Support standalone module import from ESM modules without using .default property (@​bhvngt, #​1757)
Update code for breaking TS change - error in catch has type unknown (#​1760)

v8.6.2

Compare Source

Fix JTD serialiser (#​1691)

v8.6.1

Compare Source

Fix "not" keyword preventing validation of "allOf" and some other keywords (#​1668)

v8.6.0

Compare Source

Track evaluated properties with patternProperties that have always valid schemas (e.g., true) (@​P0lip, #​1626)
Option int32range to disable number range checking for int32 and uint32 type in JTD schemas

v8.5.0

Compare Source

Optimize validation code for const keyword with scalar values (@​SoAsEr, #​1561)
Add option schemaId to support ajv-draft-04 - Ajv for JSON Schema drat-04.

v8.4.0

Compare Source

JSON Type Definition schema options:

  • parseDate: parse timestamp type as Date objects.
  • allowDate: non-standard - allow date without time with timestamp type.

v8.3.0

Compare Source

Typescript improvements:

v8.2.0

Compare Source

Add JTDDataType to compile signature (@​erikbrinkman, #​1547)
Improve JSONSchemaType for records (@​erikbrinkman, #​1564)
Use rollup for browser bundles (@​realityking, #​1533)
Docs corrections

v8.1.0

Compare Source

unicodeRegExp option to not use RegExp unicode flag that may be incompatible with some environments (@​asaid-0, #​1530)
Fix JSONSchemaType (@​erikbrinkman, #​1541)
Extended error message for invalid keyword values (@​pcwiek, #​1542)

v8.0.5

Compare Source

Fix: add source code back to npm package, 8.0.4 is breaking ajv-cli (and possibly other things)

v8.0.4

Compare Source

Reduce npm bundle size

v8.0.3

Compare Source

Improve JSONSchemaType errors (@​erikbrinkman, #​1525)

v8.0.2

Compare Source

Support RegExp formats in standalone code (#​1470)
Add schema path to strictTuple error message (@​asaid-0, #​1519)

v8.0.1

Compare Source

Typescript: export function getData (for ajv-errors)

v8.0.0

Compare Source

This document describes changes from v7.2.4 to v8.0.0.

If you are migrating from v6 you can use this document.

New features

Support JSON Schema draft-2020-12: prefixItems keyword and changed semantics of items keyword, dynamic recursive references.
OpenAPI discriminator keyword.
Improved JSON Type Definition support:

  • errors consistent with JTD specification.
  • error objects with additional properties to simplify error handling (see Error objects)
  • internationalized error messages with ajv-i18n
    TypeScript: support type unions in JSONSchemaType

Other changes / improvements

Node.js require works without .default property - see examples in Getting started
Reduce runtime dependency for standalone validation code
Fix resolution of $ref: "#" when $id is present ([#​815](https://redirect.github.com/ajv-validator/a

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Wednesday (* * * * 3)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@loopingz loopingz requested a review from a team as a code owner January 14, 2026 00:18
@loopingz loopingz added the dependencies Pull requests that update a dependency file label Jan 14, 2026
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 5 times, most recently from 0b6bd93 to c829663 Compare January 21, 2026 12:13
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 7 times, most recently from 76ee0f8 to 40b9404 Compare January 29, 2026 00:16
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 4 times, most recently from cba0ef3 to d710f61 Compare February 2, 2026 00:22
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 8 times, most recently from ac290e4 to d9e72ff Compare March 14, 2026 00:51
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 4 times, most recently from ff751e6 to e7051e4 Compare March 19, 2026 00:22
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 9 times, most recently from 83f7faf to 2ebb81c Compare April 7, 2026 01:04
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch from 2ebb81c to a1c45c0 Compare April 8, 2026 12:38
@loopingz loopingz changed the title chore(deps): update node dependencies (major) Update node dependencies (major) Apr 8, 2026
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 2 times, most recently from 2bb4d1c to 1601358 Compare April 10, 2026 04:02
@loopingz loopingz changed the title Update node dependencies (major) chore(deps): update node dependencies (major) Apr 11, 2026
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 6 times, most recently from 01fe750 to f435981 Compare April 18, 2026 00:38
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 5 times, most recently from e43e7c9 to 178c3f1 Compare April 25, 2026 00:38
@loopingz loopingz force-pushed the renovate/major-node-dependencies branch 2 times, most recently from 01393bc to 822d588 Compare April 28, 2026 00:34
@loopingz
Copy link
Copy Markdown
Contributor Author

loopingz commented Apr 28, 2026 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 18 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 30, reused 0, downloaded 0, added 0
Progress: resolved 89, reused 0, downloaded 0, added 0
Progress: resolved 169, reused 0, downloaded 0, added 0
Progress: resolved 170, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/vertesia/composableai/llumiverse/common:
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 25.7.0 (released 2 days ago) of @types/node does not meet the minimumReleaseAge constraint

This error happened while installing a direct dependency of /tmp/renovate/repos/github/vertesia/composableai/llumiverse/common

The latest release of @types/node is "25.7.0". Published at 5/11/2026

Other releases are:
  * ts2.7: 12.12.6 published at 11/5/2019
  * ts2.3: 12.12.6 published at 11/5/2019
  * ts2.4: 12.12.6 published at 11/5/2019
  * ts2.2: 12.12.6 published at 11/5/2019
  * ts2.5: 12.12.6 published at 11/5/2019
  * ts2.1: 12.12.6 published at 11/5/2019
  * ts2.0: 12.12.6 published at 11/5/2019
  * ts2.6: 12.12.6 published at 11/5/2019
  * ts2.8: 13.13.4 published at 4/26/2020
  * ts2.9: 14.0.1 published at 5/13/2020
  * ts3.0: 14.6.0 published at 8/17/2020
  * ts3.1: 14.10.1 published at 9/11/2020
  * ts3.2: 14.14.9 published at 11/19/2020
  * ts3.3: 14.14.20 published at 1/4/2021
  * ts3.4: 14.14.31 published at 2/19/2021
  * ts3.5: 15.6.1 published at 5/25/2021
  * ts3.6: 16.6.2 published at 8/18/2021
  * ts3.7: 16.11.7 published at 11/8/2021
  * ts3.8: 17.0.21 published at 2/23/2022
  * ts3.9: 17.0.41 published at 6/7/2022
  * ts4.0: 18.7.14 published at 8/29/2022
  * ts4.1: 18.11.9 published at 11/1/2022
  * ts4.2: 18.15.3 published at 3/14/2023
  * ts4.4: 20.6.0 published at 9/8/2023
  * ts4.3: 20.6.0 published at 9/8/2023
  * ts4.5: 20.10.0 published at 11/24/2023
  * ts4.6: 20.11.25 published at 3/6/2024
  * ts4.7: 20.14.8 published at 6/22/2024
  * ts4.8: 22.9.0 published at 11/5/2024
  * ts4.9: 22.9.3 published at 11/23/2024
  * ts5.0: 22.13.14 published at 3/27/2025
  * ts5.1: 24.1.0 published at 7/22/2025
  * ts5.2: 25.5.0 published at 3/12/2026
  * ts5.7: 25.7.0 published at 5/11/2026
  * ts5.3: 25.7.0 published at 5/11/2026
  * ts5.5: 25.7.0 published at 5/11/2026
  * ts5.9: 25.7.0 published at 5/11/2026
  * ts5.6: 25.7.0 published at 5/11/2026
  * ts6.0: 25.7.0 published at 5/11/2026
  * ts5.8: 25.7.0 published at 5/11/2026
  * ts5.4: 25.7.0 published at 5/11/2026

If you need the full list of all 2333 published versions run "pnpm view @types/node versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

@loopingz loopingz force-pushed the renovate/major-node-dependencies branch from 822d588 to f1dd6cb Compare April 29, 2026 12:35
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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@loopingz @renovate-bot