Skip to content

chore(deps): bump the production-dependencies group across 1 directory with 17 updates - #3765

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-5dd8cf159b
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-5dd8cf159b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 17 updates in the / directory:

Package From To
@sentry/node 11.4.0 11.12.0
eventsource 5.1.2 5.1.5
jose 6.2.12 6.2.17
postgres 3.4.9 4.1.1
dotenv 18.0.5 18.0.10
express 5.2.1 5.3.0
express-rate-limit 8.7.0 8.7.4
@aws-sdk/client-cloudwatch 3.1146.0 3.1168.0
@aws-sdk/client-s3 3.1146.0 3.1168.0
@aws-sdk/credential-providers 3.1146.0 3.1168.0
@aws-sdk/s3-request-presigner 3.1146.0 3.1168.0
axios 1.20.0 1.21.1
posthog-node 5.55.0 5.73.0
@anthropic-ai/sdk 0.131.0 1.8.0
google-auth-library 11.1.0 11.3.4
@aws-sdk/client-ses 3.1146.0 3.1168.0
@sentry/core 11.4.0 11.12.0

Updates @sentry/node from 11.4.0 to 11.12.0

Release notes

Sourced from @​sentry/node's releases.

11.12.0

Important Changes

  • feat(bundler-plugins): Enable hidden source maps and remove them after upload (#25637, #25645, #25646, #25647, #25648)

    The Sentry Rollup, Vite, webpack and esbuild plugins now turn on hidden source maps when your bundler has no source maps enabled and the plugin can upload them. They upload the maps to Sentry and remove them from the build output. You no longer need to set sourcemap: 'hidden' or filesToDeleteAfterUpload globs:

    sentryVitePlugin({ org, project, authToken });

    The new sourcemaps.deleteSourcemapsAfterUpload option controls the removal:

    • Unset: the plugin removes only the source maps it turned on itself. Source maps you enabled yourself stay in the build output, as before.
    • true: the plugin also removes source maps you enabled yourself, and switches visible source maps to hidden. Set this if you already use sourcemap: 'hidden' and want to drop your filesToDeleteAfterUpload globs.
    • false: the plugin never removes source maps.

    Builds in development mode or without an auth token, org and project do not change.

  • feat(cloudflare): Propagate tracing context through Queue messages (#25306)

    Cloudflare Queue consumers can now link to the traces of the producers that sent the messages. Set queueTracePropagationBindings to the producer bindings that should add trace data to plain-object message bodies. Consumers remove this data before your handler runs, and the queue.process span links to every producer in the batch.

    export default Sentry.withSentry(
      env => ({
        dsn: env.SENTRY_DSN,
        queueTracePropagationBindings: ['BILLING_QUEUE', /^JOBS_/],
      }),
      handler,
    );
  • feat(core): Answer managed tunnel requests in the runtime (#25997, #25998, #25999, #26000, #26001)

    serveTunnelIntegration() now answers tunnel requests before they reach your app, in Node.js, Bun, Deno, Cloudflare Workers and AWS Lambda. You no longer need a framework integration or a route handler, so any server setup works with only the integration:

    Sentry.init({ dsn, integrations: [Sentry.serveTunnelIntegration()] });

    To answer tunnel requests from your own code, set serveTunnelIntegration({ intercept: false }) and call handleTunnelRequestIfMatched.

Other Changes

  • feat(server-utils): Always warn on Bun when no channel injection is detected (#25857)
  • feat(server-utils): Group the tool spans of an Anthropic session runner under one invoke_agent span (#25995)
  • feat(tanstackstart-react): Deprecate tunnelRoute (#26225)
  • fix(aws-serverless): Fork isolation scope per invocation (#26191)
  • fix(aws-serverless): Omit default port from url.full on function.aws spans (#26227)
  • fix(browser): Keep the current origin for // paths in url.full (#26165)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

11.12.0

Important Changes

  • feat(nuxt): Mark pageloads of cached pages (#26305)

    When Nuxt serves a cached or prerendered page, for example with a swr or isr route rule, the pageload now has the page.server_rendering.type: static attribute and starts its own trace. If the request that rendered the cached page was sampled, the pageload also links to it. So visitors of a cached page no longer continue the trace of the request that rendered it.

  • feat(bundler-plugins): Enable hidden source maps and remove them after upload (#25637, #25645, #25646, #25647, #25648)

    The Sentry Rollup, Vite, webpack and esbuild plugins now turn on hidden source maps when your bundler has no source maps enabled and the plugin can upload them. They upload the maps to Sentry and remove them from the build output. You no longer need to set sourcemap: 'hidden' or filesToDeleteAfterUpload globs:

    sentryVitePlugin({ org, project, authToken });

    The new sourcemaps.deleteSourcemapsAfterUpload option controls the removal:

    • Unset: the plugin removes only the source maps it turned on itself. Source maps you enabled yourself stay in the build output, as before.
    • true: the plugin also removes source maps you enabled yourself, and switches visible source maps to hidden. Set this if you already use sourcemap: 'hidden' and want to drop your filesToDeleteAfterUpload globs.
    • false: the plugin never removes source maps.

    Builds in development mode or without an auth token, org and project do not change.

  • feat(cloudflare): Propagate tracing context through Queue messages (#25306)

    Cloudflare Queue consumers can now link to the traces of the producers that sent the messages. Set queueTracePropagationBindings to the producer bindings that should add trace data to plain-object message bodies. Consumers remove this data before your handler runs, and the queue.process span links to every producer in the batch.

    export default Sentry.withSentry(
      env => ({
        dsn: env.SENTRY_DSN,
        queueTracePropagationBindings: ['BILLING_QUEUE', /^JOBS_/],
      }),
      handler,
    );
  • feat(core): Answer managed tunnel requests in the runtime (#25997, #25998, #25999, #26000, #26001)

    serveTunnelIntegration() now answers tunnel requests before they reach your app, in Node.js, Bun, Deno, Cloudflare Workers and AWS Lambda. You no longer need a framework integration or a route handler, so any server setup works with only the integration:

    Sentry.init({ dsn, integrations: [Sentry.serveTunnelIntegration()] });

    To answer tunnel requests from your own code, set serveTunnelIntegration({ intercept: false }) and call handleTunnelRequestIfMatched.

Other Changes

  • feat(server-utils): Always warn on Bun when no channel injection is detected (#25857)

... (truncated)

Commits
  • 8bebd29 release: 11.12.0
  • e8ebd8e meta(changelog): Update changelog for 11.12.0 (#26248)
  • 7be0b7a meta(changelog): Update changelog for 11.12.0
  • 0f3145f fix(ci): prune unused rimraf lockfile entries (#26247)
  • a6b06ad fix(cloudflare): Initialize the SDK before constructing a Durable Object (#26...
  • 83f29b7 perf(ci): cache WebKit system package downloads (#26198)
  • d320067 chore: Add external contributor to CHANGELOG.md (#26245)
  • 2fe81bb chore: Add external contributor to CHANGELOG.md (#26244)
  • 312de2e chore: use native node:fs for removal scripts (#26219)
  • 39b10d8 fix(cloudflare): Keep framework-managed methods when a Durable Object constru...
  • Additional commits viewable in compare view

Updates eventsource from 5.1.2 to 5.1.5

Release notes

Sourced from eventsource's releases.

v5.1.5

Patch Changes

v5.1.4

Patch Changes

  • #372 0769591 Thanks @​edsonsims! - Copy URL objects during construction so later caller mutations do not change the exposed URL or reconnection target.

v5.1.3

Patch Changes

  • #369 d3fe0d3 Thanks @​rexxars! - Accept case variations of text/event-stream and reject different MIME subtypes such as text/event-streaming.

  • #370 02634eb Thanks @​rexxars! - Avoid double-encoding non-ASCII event IDs when reconnecting with Cloudflare Workers' native fetch.

  • #367 fd62d79 Thanks @​OsamaAnsar! - Fixed Last-Event-ID not being sent as UTF-8 on reconnect

    The event ID was passed to fetch() as a plain string header value, but header values are byte strings. An ID containing a character above U+00FF, eg €, made fetch() throw a TypeError on every reconnect attempt, so the connection was never re-established. An ID with characters in the U+0080 to U+00FF range, eg é, was sent as a single Latin-1 byte instead of its UTF-8 encoding. The header now carries the UTF-8 bytes of the ID, as the specification requires.

Changelog

Sourced from eventsource's changelog.

5.1.5

Patch Changes

5.1.4

Patch Changes

  • #372 0769591 Thanks @​edsonsims! - Copy URL objects during construction so later caller mutations do not change the exposed URL or reconnection target.

5.1.3

Patch Changes

  • #369 d3fe0d3 Thanks @​rexxars! - Accept case variations of text/event-stream and reject different MIME subtypes such as text/event-streaming.

  • #370 02634eb Thanks @​rexxars! - Avoid double-encoding non-ASCII event IDs when reconnecting with Cloudflare Workers' native fetch.

  • #367 fd62d79 Thanks @​OsamaAnsar! - Fixed Last-Event-ID not being sent as UTF-8 on reconnect

    The event ID was passed to fetch() as a plain string header value, but header values are byte strings. An ID containing a character above U+00FF, eg €, made fetch() throw a TypeError on every reconnect attempt, so the connection was never re-established. An ID with characters in the U+0080 to U+00FF range, eg é, was sent as a single Latin-1 byte instead of its UTF-8 encoding. The header now carries the UTF-8 bytes of the ID, as the specification requires.

Commits
  • ae47b1c chore(release): version packages (#381)
  • 46bf752 chore: keep Node and Deno major versions floating in CI (#388)
  • ed8db79 chore(deps): update dev dependencies (#382)
  • f35a5b3 chore(deps): update changesets/action action to v2.1.2 (#383)
  • 03436f4 chore(deps): update npm to v12.2.2 (#387)
  • 0ce156b fix(deps): update dependency eventsource-parser to ^4.1.3 (#376)
  • f23b42e ci: use the npm lockfile for Bun and Deno tests (#380)
  • cf4f3dc ci: generate changesets for Renovate runtime dependency updates (#379)
  • a6194ab ci: make the iOS simulator test opt-in (#378)
  • 242ba18 chore(config): migrate config .github/renovate.json (#377)
  • Additional commits viewable in compare view

Updates jose from 6.2.12 to 6.2.17

Release notes

Sourced from jose's releases.

v6.2.17

Fixes

  • jwt: reject negative maxTokenAge (a5b422c)

v6.2.16

Fixes

  • expose invalid options in general JWS and JWE (e41e54e), closes #920

v6.2.15

Fixes

  • jwe: cancel decompression when output exceeds the limit (67541aa)
  • jwks: reject negative cache durations (a3b296f)
  • jwt: reject negative clockTolerance (67d6c83)

v6.2.14

Fixes

  • types: preserve contextual JWT payload inference (0dbf7a0), closes #911

v6.2.13

Refactor

  • align terminology with JOSE specifications (bafcb74)
  • preserve underlying error causes (724ba24), closes #908
Changelog

Sourced from jose's changelog.

6.2.17 (2026-11-09)

Fixes

  • jwt: reject negative maxTokenAge (a5b422c)

6.2.16 (2026-11-08)

Fixes

  • expose invalid options in general JWS and JWE (e41e54e), closes #920

6.2.15 (2026-11-01)

Fixes

  • jwe: cancel decompression when output exceeds the limit (67541aa)
  • jwks: reject negative cache durations (a3b296f)
  • jwt: reject negative clockTolerance (67d6c83)

6.2.14 (2026-10-29)

Fixes

  • types: preserve contextual JWT payload inference (0dbf7a0), closes #911

6.2.13 (2026-10-20)

Refactor

  • align terminology with JOSE specifications (bafcb74)
  • preserve underlying error causes (724ba24), closes #908
Commits
  • 273bec4 chore(release): 6.2.17
  • a5b422c fix(jwt): reject negative maxTokenAge
  • 66a657a chore: cleanup after release
  • 63b80ff chore(release): 6.2.16
  • e41e54e fix: expose invalid options in general JWS and JWE
  • 607c3f7 ci: lock workflow action dependencies
  • c9b739c ci: group monthly dependency updates
  • ecf313b chore(deps-dev): bump workerd in /tap/workerd
  • 961f942 ci: schedule updates on the first monday
  • cd4e496 ci: update shared workflows to v1
  • Additional commits viewable in compare view

Updates postgres from 3.4.9 to 4.1.1

Release notes

Sourced from postgres's releases.

v4.1.1

Fixed

  • A statement sql.begin sends after its own COMMIT or ROLLBACK is rejected (#1320). A statement the callback did not await, sent between the transaction's COMMIT or ROLLBACK and the release of its connection, ran outside the transaction, and after a rollback its write was kept. It now rejects with UNSAFE_TRANSACTION, as a statement after the transaction has ended does.
  • A command after a select in a multi-statement simple query has no columns (#1321). In sql.unsafe('select …; rollback') the ROLLBACK result had the columns of the SELECT before it.
  • A query queued behind one with an untyped string or boolean parameter resolves on Cloudflare Hyperdrive (#1319). Such a query is described first, and 4.1.0 sent its Bind, Execute and Sync together with the next query, which never resolved through Hyperdrive. On Cloudflare Workers the next query now waits until the described one is done, as in 3.4.9. Other runtimes still pipeline it.
  • .cursor() yields the rows of SHOW, EXPLAIN and other commands without a row count. Their last batch was only passed on when the command tag had a count, so a cursor over them yielded nothing.
  • PGSSLMODE is kept when a url has sslrootcert, sslcert or sslkey. Such a url without an sslmode used require even if PGSSLMODE was set, so PGSSLMODE=verify-full dropped the host name check and PGSSLMODE=disable used TLS.
  • A connection error without a stack rejects the waiting queries (#1312). Adding the calling line to such an error threw, so the queries waiting for a connection never settled and the pool stopped retrying. On Bun a DNS error such as EAI_AGAIN has no stack, so a query to a host that doesn't resolve hung forever.
  • A canceled sql.batch no longer keeps the process alive for cancel_timeout (#1317, #1318). The timer that waits for the cancel to be answered was left running after the batch rejected, so the process stayed up for 5 seconds after sql.end().
  • A JSON key ending with _ no longer makes toCamel and toPascal throw (#1313). With transform: postgres.camel, such a key made the whole query throw. The trailing _ is now kept, so a_ stays a_, and an empty key stays empty instead of becoming undefined.

porsager/postgres@v4.1.0...v4.1.1

v4.1.0

New

  • query_timeout (#1278). Seconds a query may take, waiting for a connection and running together, before it is canceled and rejects with QUERY_TIMEOUT. Off by default. Unlike statement_timeout it also ends a query whose server or network has gone silent, which TCP alone takes many minutes to notice. Transaction control queries and forEach are limited too; cursors, streams and sql.listen are not.
  • cancel_timeout, 5 seconds by default: how long a canceled query may take to end before its connection is closed.
  • sql.batch([queries]) sends queries in one round trip with a single Sync: outside a transaction they commit or roll back together, and the batch rejects with the failing query's position in error.index.
  • json on a transform (#1169). The built-in transforms rename the keys of JSON values in results but send JSON values as they are. json: false leaves JSON values as they are both ways, and json: true renames their keys when sending too, with the transform's column.to. Without it nothing changes.
  • eager_types: true reads array types and domains when the pool starts instead of when a query first meets one.
  • sql.identifier(...parts) (#1292). An identifier from its parts, each quoted as it is and joined with ., for a name that contains a dot, which sql(name) reads as a separator: sql.identifier('acme.inc', 'users') gives "acme.inc"."users". The transform is not applied. With no parts it throws NO_PARTS.
  • Node.js 18 is supported again: engines is >=18 and CI runs it. Nothing in Postgres.js needs 20; using, await using and tracing are used where the runtime has them. Loading it with require still needs Node.js 20.19 or 22.12.
  • sql`...`.parsers(parsers) (#1294). A query's own parsers, for its rows only: by type, { [oid]: parse }, on top of the instance's types, or a function that gets each column and returns the parser for it, null for the server's text. A library that knows how to decode some queries' columns can decode them once, inside the row reader, while every other query on the instance and its pool keeps the instance's parsers. Such a query receives every column as text, so bytea and the integer arrays otherwise read in binary reach its parsers as text. A query without .parsers() reads its rows as before.

Fixed

  • sql.listen keeps its connection after the last unlisten() (#1298). The connection was closed so the process could exit (#1022), which made every following listen() connect again: about 3.5 ms instead of 0.1 ms per listen. It now stays open without keeping the process alive once nothing is listened.
  • PGSSLMODE is read (#1307). It was ignored, so PGSSLMODE=verify-full connected in plain text without an error. This may change how existing setups connect: require now uses TLS and fails against a server without it, and verify-ca and verify-full check the certificate against Node's CAs, not ~/.postgresql/root.crt or PGSSLROOTCERT. A url or an ssl option still comes first.
  • An insert helper after a quoted schema and an unquoted table builds the insert (#1304). In insert into ${ sql('s') }.t ${ sql(row) } or insert into "s".t, the quoted schema and the table were read as two words, so the row was taken for a list of identifiers and threw x.replace is not a function.
  • sql.listen keeps reconnecting when its first reconnect fails (#1285, #1286). After the listen connection closed, it was reopened once, and if that attempt failed, as it does while a restarting server still refuses connections, nothing tried again, so onlisten was never called and notifications were lost. A failed reconnect is now retried after backoff, until it succeeds, the channel is unlistened or the pool ends.
  • A canceled query whose server never answers no longer waits forever. .cancel(), .signal() and now query_timeout send a cancel request and waited for the server to end the query, so a server or network gone silent left both the query and the promise .cancel() returns pending until TCP gave up. This applies to every cancel, also without query_timeout: when the server doesn't answer within cancel_timeout, the connection is closed and the pool connects again. Whether the queries on it ran is unknown, so they reject with CONNECTION_DESTROYED (a timed out one with QUERY_TIMEOUT) whose cause is CANCEL_UNANSWERED, not with 57014. The cancel request's own connection is limited by cancel_timeout too, and a cancel is no longer sent for a query whose result has already arrived, where it could only hit the query after it. A cancel request whose own connection fails, as over TLS to a server gone silent, no longer crashes the process with an unhandled rejection. A query that times out while it waits behind another one on its connection is canceled only after it has had its own query_timeout once its turn comes, instead of the moment its turn comes, when it had usually finished and the cancel stopped the next query; if the server sends nothing for cancel_timeout while it waits, the connection is closed. A query waiting for types to be read rejects with QUERY_TIMEOUT without closing its connection, and the read of array types and domains is limited by query_timeout too.
  • sslrootcert, sslcert and sslkey in a url are used (#1308). They were sent to the server as startup parameters, so ?sslrootcert=system failed with unrecognized configuration parameter. Files are read into ca, cert and key. As in libpq, a root certificate with require or verify-ca checks the CA but not the host name, and verify-full checks both, as does ssl: true. A file without an sslmode means require.
  • A transaction the server ends rejects with the server's error (#1283, #1284). When a transaction_timeout (25P04), an idle_in_transaction_session_timeout (25P03) or pg_terminate_backend (57P01) ended the session, sql.begin rejected with CONNECTION_CLOSED, so a timeout or a termination looked the same as a network drop; it now rejects with the FATAL error the server sent before closing, as a query in flight already did, and a later query on that connection rejects with CONNECTION_CLOSED that has it as cause. A server restart or failover ends sessions with 57P01, so code that retries a transaction on CONNECTION_CLOSED should retry on that code too. A FATAL in answer to COMMIT rejects with CONNECTION_CLOSED that has it as cause, as the outcome is unknown, as it is when the connection is lost during COMMIT.
  • A server certificate is verified against an IP host (#1309). With ssl: 'verify-full' or ssl: true and an IP as the host, a connection upgraded to TLS checked the certificate against localhost, so a certificate for localhost from a trusted CA passed for any IP and a correct certificate for the IP failed. Direct TLS was not affected.
  • A savepoint or nested begin rejects when its transaction's connection is lost (#1281, #1282). One whose callback was still running when the connection went resolved with the callback's result after the transaction had already rejected; it now rejects with the transaction's error.
  • A connection closed while the pool reads its array and domain types counts as a failed connection attempt (#1279). Reconnecting follows backoff and waiting queries reject once connect_timeout has passed, instead of reconnecting as fast as the server accepts for as long as it keeps closing. With connect_timeout set to 0, null or false the pool now keeps trying for as long as it takes, as the option says, also after a refused or closed startup, which used to reject the waiting queries at once.
  • A query failed by a FATAL error gives that error to the queries pipelined behind it as well, instead of CONNECTION_CLOSED.
  • A FATAL error with the severity only in the S field is recognised as one. The non-localized V field is optional in the protocol: PostgreSQL sends it since 9.6, and a pooler that builds its own errors, such as PgBouncer, may send only the localized S. Such an error was not seen as FATAL, so the query, a sql.begin and the queries pipelined behind it rejected with CONNECTION_CLOSED without a cause instead of with the error. error.severity now falls back to severity_local when V is missing.
  • Each query on a connection that closes gets its own error. They shared one error object, so every query pipelined on the connection reported the first one's query and parameters.
  • A cached prepared statement no longer keeps the query that prepared it (#1287). Each connection's entry for a prepared statement kept that query's values and rows for as long as the statement stayed cached, up to 1,000 statements per connection, so an app with many distinct statements grew by their results until every cache was full: about 1.1 GB with 10 connections and 50-row results. They are let go once the query settles. On 4.0.0, prepare: false avoids it.
  • Destroying a copy ... to stdout stream frees the connection (#1306). After destroy(), breaking out of for await or a failed pipeline, the connection stayed paused for good and the queries behind it never ran. The rest of the copy is now read and dropped, so the connection is free once the server has sent it. The query is not canceled, so in a transaction the next query still succeeds.

Performance

  • An ssl object with a ca builds its TLS context once (#1280). The connections made with it share one context instead of each parsing the whole ca list again, so with a provider's CA bundle a new connection takes about half the time and CPU, and a burst of them no longer blocks the event loop. Replacing one of the object's values, as with a renewed cert, builds a new context for the connections after it.
  • A new statement whose untyped values are all numbers or null is prepared, described and run in one round trip, as one whose parameter types are all known is, since those values are written the same for any type the server picks; one with other values only the server can type is still described first, once per connection.

... (truncated)

Changelog

Sourced from postgres's changelog.

v4.1.1 - 11 November 2026

Fixed

  • A statement sql.begin sends after its own COMMIT or ROLLBACK is rejected (#1320). A statement the callback did not await, sent between the transaction's COMMIT or ROLLBACK and the release of its connection, ran outside the transaction, and after a rollback its write was kept. It now rejects with UNSAFE_TRANSACTION, as a statement after the transaction has ended does.
  • A command after a select in a multi-statement simple query has no columns (#1321). In sql.unsafe('select …; rollback') the ROLLBACK result had the columns of the SELECT before it.
  • A query queued behind one with an untyped string or boolean parameter resolves on Cloudflare Hyperdrive (#1319). Such a query is described first, and 4.1.0 sent its Bind, Execute and Sync together with the next query, which never resolved through Hyperdrive. On Cloudflare Workers the next query now waits until the described one is done, as in 3.4.9. Other runtimes still pipeline it.
  • .cursor() yields the rows of SHOW, EXPLAIN and other commands without a row count. Their last batch was only passed on when the command tag had a count, so a cursor over them yielded nothing.
  • PGSSLMODE is kept when a url has sslrootcert, sslcert or sslkey. Such a url without an sslmode used require even if PGSSLMODE was set, so PGSSLMODE=verify-full dropped the host name check and PGSSLMODE=disable used TLS.
  • A connection error without a stack rejects the waiting queries (#1312). Adding the calling line to such an error threw, so the queries waiting for a connection never settled and the pool stopped retrying. On Bun a DNS error such as EAI_AGAIN has no stack, so a query to a host that doesn't resolve hung forever.
  • A canceled sql.batch no longer keeps the process alive for cancel_timeout (#1317, #1318). The timer that waits for the cancel to be answered was left running after the batch rejected, so the process stayed up for 5 seconds after sql.end().
  • A JSON key ending with _ no longer makes toCamel and toPascal throw (#1313). With transform: postgres.camel, such a key made the whole query throw. The trailing _ is now kept, so a_ stays a_, and an empty key stays empty instead of becoming undefined.

v4.1.0 - 5 November 2026

New

  • query_timeout (#1278). Seconds a query may take, waiting for a connection and running together, before it is canceled and rejects with QUERY_TIMEOUT. Off by default. Unlike statement_timeout it also ends a query whose server or network has gone silent, which TCP alone takes many minutes to notice. Transaction control queries and forEach are limited too; cursors, streams and sql.listen are not.
  • cancel_timeout, 5 seconds by default: how long a canceled query may take to end before its connection is closed.
  • sql.batch([queries]) sends queries in one round trip with a single Sync: outside a transaction they commit or roll back together, and the batch rejects with the failing query's position in error.index.
  • json on a transform (#1169). The built-in transforms rename the keys of JSON values in results but send JSON values as they are. json: false leaves JSON values as they are both ways, and json: true renames their keys when sending too, with the transform's column.to. Without it nothing changes.
  • eager_types: true reads array types and domains when the pool starts instead of when a query first meets one.
  • sql.identifier(...parts) (#1292). An identifier from its parts, each quoted as it is and joined with ., for a name that contains a dot, which sql(name) reads as a separator: sql.identifier('acme.inc', 'users') gives "acme.inc"."users". The transform is not applied. With no parts it throws NO_PARTS.
  • Node.js 18 is supported again: engines is >=18 and CI runs it. Nothing in Postgres.js needs 20; using, await using and tracing are used where the runtime has them. Loading it with require still needs Node.js 20.19 or 22.12.
  • sql`...`.parsers(parsers) (#1294). A query's own parsers, for its rows only: by type, { [oid]: parse }, on top of the instance's types, or a function that gets each column and returns the parser for it, null for the server's text. A library that knows how to decode some queries' columns can decode them once, inside the row reader, while every other query on the instance and its pool keeps the instance's parsers. Such a query receives every column as text, so bytea and the integer arrays otherwise read in binary reach its parsers as text. A query without .parsers() reads its rows as before.

Fixed

  • sql.listen keeps its connection after the last unlisten() (#1298). The connection was closed so the process could exit (#1022), which made every following listen() connect again: about 3.5 ms instead of 0.1 ms per listen. It now stays open without keeping the process alive once nothing is listened.
  • PGSSLMODE is read (#1307). It was ignored, so PGSSLMODE=verify-full connected in plain text without an error. This may change how existing setups connect: require now uses TLS and fails against a server without it, and verify-ca and verify-full check the certificate against Node's CAs, not ~/.postgresql/root.crt or PGSSLROOTCERT. A url or an ssl option still comes first.
  • An insert helper after a quoted schema and an unquoted table builds the insert (#1304). In insert into ${ sql('s') }.t ${ sql(row) } or insert into "s".t, the quoted schema and the table were read as two words, so the row was taken for a list of identifiers and threw x.replace is not a function.
  • sql.listen keeps reconnecting when its first reconnect fails (#1285, #1286). After the listen connection closed, it was reopened once, and if that attempt failed, as it does while a restarting server still refuses connections, nothing tried again, so onlisten was never called and notifications were lost. A failed reconnect is now retried after backoff, until it succeeds, the channel is unlistened or the pool ends.
  • A canceled query whose server never answers no longer waits forever. .cancel(), .signal() and now query_timeout send a cancel request and waited for the server to end the query, so a server or network gone silent left both the query and the promise .cancel() returns pending until TCP gave up. This applies to every cancel, also without query_timeout: when the server doesn't answer within cancel_timeout, the connection is closed and the pool connects again. Whether the queries on it ran is unknown, so they reject with CONNECTION_DESTROYED (a timed out one with QUERY_TIMEOUT) whose cause is CANCEL_UNANSWERED, not with 57014. The cancel request's own connection is limited by cancel_timeout too, and a cancel is no longer sent for a query whose result has already arrived, where it could only hit the query after it. A cancel request whose own connection fails, as over TLS to a server gone silent, no longer crashes the process with an unhandled rejection. A query that times out while it waits behind another one on its connection is canceled only after it has had its own query_timeout once its turn comes, instead of the moment its turn comes, when it had usually finished and the cancel stopped the next query; if the server sends nothing for cancel_timeout while it waits, the connection is closed. A query waiting for types to be read rejects with QUERY_TIMEOUT without closing its connection, and the read of array types and domains is limited by query_timeout too.
  • sslrootcert, sslcert and sslkey in a url are used (#1308). They were sent to the server as startup parameters, so ?sslrootcert=system failed with unrecognized configuration parameter. Files are read into ca, cert and key. As in libpq, a root certificate with require or verify-ca checks the CA but not the host name, and verify-full checks both, as does ssl: true. A file without an sslmode means require.
  • A transaction the server ends rejects with the server's error (#1283, #1284). When a transaction_timeout (25P04), an idle_in_transaction_session_timeout (25P03) or pg_terminate_backend (57P01) ended the session, sql.begin rejected with CONNECTION_CLOSED, so a timeout or a termination looked the same as a network drop; it now rejects with the FATAL error the server sent before closing, as a query in flight already did, and a later query on that connection rejects with CONNECTION_CLOSED that has it as cause. A server restart or failover ends sessions with 57P01, so code that retries a transaction on CONNECTION_CLOSED should retry on that code too. A FATAL in answer to COMMIT rejects with CONNECTION_CLOSED that has it as cause, as the outcome is unknown, as it is when the connection is lost during COMMIT.
  • A server certificate is verified against an IP host (#1309). With ssl: 'verify-full' or ssl: true and an IP as the host, a connection upgraded to TLS checked the certificate against localhost, so a certificate for localhost from a trusted CA passed for any IP and a correct certificate for the IP failed. Direct TLS was not affected.
  • A savepoint or nested begin rejects when its transaction's connection is lost (#1281, #1282). One whose callback was still running when the connection went resolved with the callback's result after the transaction had already rejected; it now rejects with the transaction's error.
  • A connection closed while the pool reads its array and domain types counts as a failed connection attempt (#1279). Reconnecting follows backoff and waiting queries reject once connect_timeout has passed, instead of reconnecting as fast as the server accepts for as long as it keeps closing. With connect_timeout set to 0, null or false the pool now keeps trying for as long as it takes, as the option says, also after a refused or closed startup, which used to reject the waiting queries at once.
  • A query failed by a FATAL error gives that error to the queries pipelined behind it as well, instead of CONNECTION_CLOSED.
  • A FATAL error with the severity only in the S field is recognised as one. The non-localized V field is optional in the protocol: PostgreSQL sends it since 9.6, and a pooler that builds its own errors, such as PgBouncer, may send only the localized S. Such an error was not seen as FATAL, so the query, a sql.begin and the queries pipelined behind it rejected with CONNECTION_CLOSED without a cause instead of with the error. error.severity now falls back to severity_local when V is missing.
  • Each query on a connection that closes gets its own error. They shared one error object, so every query pipelined on the connection reported the first one's query and parameters.
  • A cached prepared statement no longer keeps the query that prepared it (#1287). Each connection's entry for a prepared statement kept that query's values and rows for as long as the statement stayed cached, up to 1,000 statements per connection, so an app with many distinct statements grew by their results until every cache was full: about 1.1 GB with 10 connections and 50-row results. They are let go once the query settles. On 4.0.0, prepare: false avoids it.
  • Destroying a copy ... to stdout stream frees the connection (#1306). After destroy(), breaking out of for await or a failed pipeline, the connection stayed paused for good and the queries behind it never ran. The rest of the copy is now read and dropped, so the connection is free once the server has sent it. The query is not canceled, so in a transaction the next query still succeeds.

Performance

  • An ssl object with a ca builds its TLS context once (#1280). The connections made with it share one context instead of each parsing the whole ca list again, so with a provider's CA bundle a new connection takes about half the time and CPU, and a burst of them no longer blocks the event loop. Replacing one of the object's values, as with a renewed cert, builds a new context for the connections after it.
  • A new statement whose untyped values are all numbers or null is prepared, described and run in one round trip, as one whose parameter types are all known is, since those values are written the same for any type the server picks; one with other values only the server can type is still described first, once per connection.
  • Array types and domains are read when a query first meets a type the pool does not know (an oid from 16384 up), instead of when the pool starts: a pool that only uses built-in types never sends that query, and a new pool's first query costs no more than any other. The connection that met the type waits for it, read on another connection. With custom types given by name they are still read at startup, as their oids are needed before the first query. Leases and values typed as a type the pool hasn't read yet still wait for it. A read whose connection fails is retried after backoff, and once connect_timeout has passed the connections waiting for it are closed and their queries reject, as for a failed startup. eager_types: true reads them when the pool starts, as before.
  • timestamptz, and timestamp and date read as UTC, are decoded straight from the bytes when they use the built-in parsers, with the text parser for anything else (BC, infinity, years before 1000); about 20% more rows per second for rows with timestamps.

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 2, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/production-dependencies-5dd8cf159b branch 3 times, most recently from 97d70fa to c697cbd Compare November 13, 2026 23:22
…y with 17 updates

Bumps the production-dependencies group with 17 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@sentry/node](https://github.com/getsentry/sentry-javascript) | `11.4.0` | `11.12.0` |
| [eventsource](https://github.com/EventSource/eventsource) | `5.1.2` | `5.1.5` |
| [jose](https://github.com/panva/jose) | `6.2.12` | `6.2.17` |
| [postgres](https://github.com/porsager/postgres) | `3.4.9` | `4.1.1` |
| [dotenv](https://github.com/motdotla/dotenv) | `18.0.5` | `18.0.10` |
| [express](https://github.com/expressjs/express) | `5.2.1` | `5.3.0` |
| [express-rate-limit](https://github.com/express-rate-limit/express-rate-limit) | `8.7.0` | `8.7.4` |
| [@aws-sdk/client-cloudwatch](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-cloudwatch) | `3.1146.0` | `3.1168.0` |
| [@aws-sdk/client-s3](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3) | `3.1146.0` | `3.1168.0` |
| [@aws-sdk/credential-providers](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/packages/credential-providers) | `3.1146.0` | `3.1168.0` |
| [@aws-sdk/s3-request-presigner](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/packages/s3-request-presigner) | `3.1146.0` | `3.1168.0` |
| [axios](https://github.com/axios/axios) | `1.20.0` | `1.21.1` |
| [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) | `5.55.0` | `5.73.0` |
| [@anthropic-ai/sdk](https://github.com/anthropics/anthropic-sdk-typescript) | `0.131.0` | `1.8.0` |
| [google-auth-library](https://github.com/googleapis/google-cloud-node/tree/HEAD/core/packages/google-auth-library-nodejs) | `11.1.0` | `11.3.4` |
| [@aws-sdk/client-ses](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-ses) | `3.1146.0` | `3.1168.0` |
| [@sentry/core](https://github.com/getsentry/sentry-javascript) | `11.4.0` | `11.12.0` |



Updates `@sentry/node` from 11.4.0 to 11.12.0
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@11.4.0...11.12.0)

Updates `eventsource` from 5.1.2 to 5.1.5
- [Release notes](https://github.com/EventSource/eventsource/releases)
- [Changelog](https://github.com/EventSource/eventsource/blob/main/CHANGELOG.md)
- [Commits](EventSource/eventsource@v5.1.2...v5.1.5)

Updates `jose` from 6.2.12 to 6.2.17
- [Release notes](https://github.com/panva/jose/releases)
- [Changelog](https://github.com/panva/jose/blob/main/CHANGELOG.md)
- [Commits](panva/jose@v6.2.12...v6.2.17)

Updates `postgres` from 3.4.9 to 4.1.1
- [Release notes](https://github.com/porsager/postgres/releases)
- [Changelog](https://github.com/porsager/postgres/blob/master/CHANGELOG.md)
- [Commits](porsager/postgres@v3.4.9...v4.1.1)

Updates `dotenv` from 18.0.5 to 18.0.10
- [Changelog](https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md)
- [Commits](motdotla/dotenv@v18.0.5...v18.0.10)

Updates `express` from 5.2.1 to 5.3.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@v5.2.1...v5.3.0)

Updates `express-rate-limit` from 8.7.0 to 8.7.4
- [Release notes](https://github.com/express-rate-limit/express-rate-limit/releases)
- [Commits](express-rate-limit/express-rate-limit@v8.7.0...v8.7.4)

Updates `@aws-sdk/client-cloudwatch` from 3.1146.0 to 3.1168.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-cloudwatch/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1168.0/clients/client-cloudwatch)

Updates `@aws-sdk/client-s3` from 3.1146.0 to 3.1168.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-s3/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1168.0/clients/client-s3)

Updates `@aws-sdk/credential-providers` from 3.1146.0 to 3.1168.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/packages/credential-providers/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1168.0/packages/credential-providers)

Updates `@aws-sdk/s3-request-presigner` from 3.1146.0 to 3.1168.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/packages/s3-request-presigner/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1168.0/packages/s3-request-presigner)

Updates `axios` from 1.20.0 to 1.21.1
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v1.20.0...v1.21.1)

Updates `posthog-node` from 5.55.0 to 5.73.0
- [Release notes](https://github.com/PostHog/posthog-js/releases)
- [Changelog](https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md)
- [Commits](https://github.com/PostHog/posthog-js/commits/posthog-node@5.73.0/packages/node)

Updates `@anthropic-ai/sdk` from 0.131.0 to 1.8.0
- [Release notes](https://github.com/anthropics/anthropic-sdk-typescript/releases)
- [Changelog](https://github.com/anthropics/anthropic-sdk-typescript/blob/main/CHANGELOG.md)
- [Commits](anthropics/anthropic-sdk-typescript@sdk-v0.131.0...sdk-v1.8.0)

Updates `google-auth-library` from 11.1.0 to 11.3.4
- [Release notes](https://github.com/googleapis/google-cloud-node/releases)
- [Changelog](https://github.com/googleapis/google-cloud-node/blob/main/core/packages/google-auth-library-nodejs/CHANGELOG.md)
- [Commits](https://github.com/googleapis/google-cloud-node/commits/google-auth-library-v11.3.4/core/packages/google-auth-library-nodejs)

Updates `@aws-sdk/client-ses` from 3.1146.0 to 3.1168.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-ses/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1168.0/clients/client-ses)

Updates `@sentry/core` from 11.4.0 to 11.12.0
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@11.4.0...11.12.0)

---
updated-dependencies:
- dependency-name: "@anthropic-ai/sdk"
  dependency-version: 1.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
- dependency-name: "@aws-sdk/client-cloudwatch"
  dependency-version: 3.1161.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@aws-sdk/client-s3"
  dependency-version: 3.1161.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@aws-sdk/client-ses"
  dependency-version: 3.1161.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@aws-sdk/credential-providers"
  dependency-version: 3.1161.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@aws-sdk/s3-request-presigner"
  dependency-version: 3.1161.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@sentry/core"
  dependency-version: 11.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@sentry/node"
  dependency-version: 11.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: axios
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: dotenv
  dependency-version: 18.0.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: eventsource
  dependency-version: 5.1.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: express
  dependency-version: 5.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: express-rate-limit
  dependency-version: 8.7.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: google-auth-library
  dependency-version: 11.3.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: jose
  dependency-version: 6.2.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: postgres
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
- dependency-name: posthog-node
  dependency-version: 5.61.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/production-dependencies-5dd8cf159b branch from c697cbd to ff9f009 Compare November 16, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants