Skip to content

build(deps): Bump the bun group across 1 directory with 16 updates - #116

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/bun-c6eb3b2351
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/bun-c6eb3b2351

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the bun group with 16 updates in the / directory:

Package From To
oxfmt 0.74.0 0.78.0
oxlint 1.89.0 1.93.0
postgres 3.4.9 4.1.1
tldts 7.4.19 7.5.4
tsdown 0.23.3 0.23.7
hono 4.13.14 4.13.18
wrangler 4.152.0 4.162.0
@astrojs/markdown-satteri 0.4.5 0.4.10
@astrojs/react 7.1.2 7.1.9
@tailwindcss/vite 4.3.3 4.3.5
astro 7.4.2 7.4.12
cn 0.5.0 0.5.2
lucide-react 1.64.0 1.73.0
satteri 0.10.5 0.11.7
tailwindcss 4.3.3 4.3.5
useyuva 0.4.0 0.5.0

Updates oxfmt from 0.74.0 to 0.78.0

Release notes

Sourced from oxfmt's releases.

oxfmt v0.78.0

🐛 Bug Fixes

  • ab78621 formatter_css/less: Print ~ escape consistently (#29089) (Yuji Sugiura)
  • 91721d2 formatter_css/less: Print Less % selectors (#29088) (Yuji Sugiura)
  • 449e91f oxfmt: Format ts-in-astro as TSX (#29080) (leaysgur)
  • 8d8845e formatter/jsdoc: Strip * prefixes from multiline default value (#28910) (leaysgur)
  • cdb1501 formatter/jsdoc: Handle every line terminator in multi-line JSDoc types (#28909) (leaysgur)
  • fd51bff jsdoc: Handle every line terminators as newline (#28902) (leaysgur)
  • 2f80765 formatter_toml: Format whitespace-only document to empty (#28899) (leaysgur)
  • 5e1e02c formatter_graphql: Allow empty document (#28898) (leaysgur)
  • 06e72c0 formatter/tailwind: Normalize CR in Tailwind template with preserveWhitespace (#28896) (leaysgur)

⚡ Performance

  • 934ca98 formatter: Use Arc for tailwind options across embedding (#29079) (leaysgur)
  • dde9c5c formatter_htmlish: Skip </script escape if possible (#29078) (leaysgur)
  • dc4d918 formatter: Format embedded expr of one name without parsing (#29077) (leaysgur)

📚 Documentation

  • eb2eb2d formatter_htmlish: Cover block elements in DIVERGENCES.md#interpolation-element-as-text (#28901) (leaysgur)
  • 0f4ec80 formatter/tailwind: Note Tailwind sorting tears escaped whitespace apart (#28900) (leaysgur)

oxfmt v0.77.0

💥 BREAKING CHANGES

  • 00d1a67 oxfmt: [BREAKING] Format parser:vue files by oxc_formatter_htmlish (#28848) (leaysgur)

🚀 Features

  • 9a81e58 formatter_htmlish: Format Vue templates (#28847) (leaysgur)
  • 119d82f formatter: Format a template's expressions and handlers as JsRoot (#28846) (leaysgur)

🐛 Bug Fixes

  • fa66fde oxlint,oxfmt: Resolve Vite+ config root from the config file directory (#28801) (MK (fengmk2))
  • 4d4104d formatter_htmlish: Preserve doctype case in embedded (#28797) (leaysgur)
  • ebfd40a formatter: Sort Tailwind calls printed as member chains (#28800) (Yuji Sugiura)
  • e62e5cb formatter: Decide quotes of a Tailwind key printed as one class (#28798) (Yuji Sugiura)
  • 959edc1 formatter: Don't sort templates in nested non-Tailwind calls (#28794) (Yuji Sugiura)
  • 6ffbe32 formatter/jsdoc: Prevent @tag from being moved to the line start (#28835) (leaysgur)
  • 94fbef5 formatter_css: Treat comments in style attr as fill items (#28832) (leaysgur)
  • e4a80f7 formatter_css: Normalize selectors inside :deep, :slotted and :local (#28805) (leaysgur)
  • 255c5cc formatter: Measure Tailwind class argument after collapsing whitespace (#28745) (Lee Jaeha / Adam)
  • e6c4fef formatter: Decide template and object key layouts from collapsed Tailwind classes (#28791) (Yuji Sugiura)
  • 0b44164 formatter: Decide JSX opening element layout from collapsed Tailwind class string (#28744) (Lee Jaeha / Adam)
  • b8ba9ae formatter: Print decorators on rest parameters (#28731) (YT)

⚡ Performance

... (truncated)

Commits

Updates oxlint from 1.89.0 to 1.93.0

Release notes

Sourced from oxlint's releases.

oxlint v1.93.0

🚀 Features

  • 6195265 linter/promise/prefer-catch: Implement suggestion (#28919) (Mikhail Baev)

🐛 Bug Fixes

  • 866664e linter/unicorn/no-useless-undefined: Skip var initializers (#29007) (camc314)
  • 30603cb linter/react/exhaustive-deps: Preserve comments in dependency removals (#29047) (camc314)
  • 4630fe4 linter/unicorn/no-useless-undefined: Narrow return type exemptions (#29000) (camc314)
  • b63870a linter/vitest/expect-expect: Recognize benchmark fixtures (#29044) (camc314)
  • 9c62d2a linter/eslint/no-unreachable-loop: Ignore enclosing finalizers for continues (#29004) (camc314)
  • 6303df1 jsdoc: Preserve param tags after unmatched description delimiters (#28923) (Vishal Punjabi)
  • fe66fa7 linter/eslint/no-lone-blocks: Report redundant blocks in function bodies (#29043) (camc314)
  • e1694bd linter/unicorn/no-useless-undefined: Preserve shadowed bindings (#29046) (camc314)
  • 791b5f5 linter/unicorn/prefer-regexp-test: Restrict automatic argument swaps (#29045) (camc314)
  • e7654f6 linter/react/display-name: Ignore unrelated memo and forwardRef calls (#29005) (camc314)
  • 2487360 linter/unicorn/no-useless-undefined: Report guarded indexed access (#29014) (camc314)
  • a791a5b cfg: Resolve continues through stacked loop labels (#29016) (camc314)
  • 287ba19 linter/eslint/id-length: Ignore TypeScript qualified references (#29037) (camc314)
  • b71234f cfg: Skip labeled contexts for unlabeled jumps (#29001) (camc314)
  • bb21a3c linter/import/no-anonymous-default-export: Report parenthesized exports (#29002) (camc314)
  • f38f738 linter/eslint/prefer-destructuring: Skip fixes that remove comments (#29003) (camc314)
  • bf11006 linter/react/exhaustive-deps: Suggest dependency removals (#28925) (camc314)
  • 6bbb92a linter: Remove unused oxlint-disable directives with --fix (#27698) (Ryan Tsao)
  • 3b35cb6 linter/disable-directives: Preserve separators and disable spans (#28921) (camc314)
  • 1253445 linter/eslint/no-restricted-imports: Report re-exported imports once (#28920) (Ramy Akin Saidi)

⚡ Performance

  • da620e6 linter: Start tsgolint before the regular lint pass (#28824) (Max Schwenk)

oxlint v1.92.0

🚀 Features

  • 4a52ba2 oxlint: Discover tsrs for type-aware linting (#28751) (camc314)
  • b7d2c75 linter/eslint/no-redeclare: Add ignoreDeclarationMerge option (#28816) (Cam McHenry)

🐛 Bug Fixes

  • fa66fde oxlint,oxfmt: Resolve Vite+ config root from the config file directory (#28801) (MK (fengmk2))
  • 2091564 linter/jsdoc/require-param: Ignore enclosing function JSDoc (#28866) (camc314)
  • c6ec50b linter/react/only-export-components: Classify JSX values as non-components (#28761) (camc314)
  • 3c051ab linter/vitest/prefer-called-exactly-once-with: Preserve neighboring code in autofix (#28864) (camc314)
  • 674b962 linter/eslint/no-misleading-character-class: Use lazy regex for combining marks (#28822) (Sysix)
  • 838d339 linter/vitest/prefer-called-exactly-once-with: Avoid panic on non-ASCII text (#28850) (YT)
  • 8d24c26 linter/jsx-a11y/aria-role: Allow role={undefined} (#28804) (Abhay Godavarthy)
  • a7143bf linter/eslint/no-restricted-imports: Respect allowTypeImports correctly for empty patterns (#28842) (Cam McHenry)
  • 3d3a6f4 react-compiler: Ignore callback-local reassignments (#28820) (camc314)
  • 0cc6515 linter/unicorn/prefer-type-error: Report throws in unbraced if branches (#28819) (camc314)

... (truncated)

Changelog

Sourced from oxlint's changelog.

Changelog

All notable changes to this package will be documented in this file.

The format is based on Keep a Changelog.

[1.94.0] - 2026-11-16

🚀 Features

  • acd8814 linter/typescript/no-misused-promises: Add flagUnions option (#29380) (camc314)

📚 Documentation

  • cdb5ac4 oxlint: Remove experimental label from typeCheck (#29175) (Yuji Sugiura)

[1.92.0] - 2026-11-06

🚀 Features

  • b7d2c75 linter/eslint/no-redeclare: Add ignoreDeclarationMerge option (#28816) (Cam McHenry)

[1.91.0] - 2026-11-02

🚀 Features

  • 419c1b0 linter: Add allow and allowPattern options to react/capitalized-calls (Christian Vuerings)

[1.90.0] - 2026-10-27

🚀 Features

  • 831cdf1 oxlint: Require mininum oxlint-tsgolint version v7.0.2005 (#28118) (camc314)
  • d1b00f4 linter/typescript: Implement no-unsafe-enum-assignment rule (#28117) (camc314)
  • 165c91f linter/typescript/await-thenable: Support allowMixedPromiseArrays option (#28116) (camc314)
Commits
  • 7d8e1f4 release(apps): oxlint v1.93.0 && oxfmt v0.78.0 (#29090)
  • 29daf90 release(apps): oxlint v1.92.0 && oxfmt v0.77.0 (#28906)
  • b7d2c75 feat(linter/eslint/no-redeclare): add ignoreDeclarationMerge option (#28816)
  • f3fcdcc release(apps): oxlint v1.91.0 && oxfmt v0.76.0 (#28718)
  • 419c1b0 feat(linter): add allow and allowPattern options to react/capitalized-calls
  • 9b6fff4 release(apps): oxlint v1.90.0 && oxfmt v0.75.0 (#28191)
  • 831cdf1 feat(oxlint): require mininum oxlint-tsgolint version v7.0.2005 (#28118)
  • d1b00f4 feat(linter/typescript): implement no-unsafe-enum-assignment rule (#28117)
  • 165c91f feat(linter/typescript/await-thenable): support allowMixedPromiseArrays opt...
  • See full diff 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
  • 1cc66f4 4.1.1
  • a82bf9d v4.1.1 changelog
  • 3d664d4 Changelog entries for #1313 and #1318
  • 26c4b62 A statement sql.begin sends after its own commit or rollback is rejected (#1320)
  • 28ec07d A command after a select in a multi-statement simple query has no columns (#1...
  • 672e52b On Cloudflare Workers, wait for a described query before sending the next (#1...
  • 5b4b90c Keep a trailing underscore in toCamel and toPascal
  • e94a4fd Document the sql.batch and AUTHENTICATION_INCOMPLETE error codes
  • ed087e7 Yield the rows of commands without a row count from a cursor
  • 15c0748 fix: clear the cancel_timeout timer once a canceled sql.batch settles
  • Additional commits viewable in compare view

Updates tldts from 7.4.19 to 7.5.4

Release notes

Sourced from tldts's releases.

v7.5.4

📜 Update Public Suffix List

  • tldts-experimental, tldts

Authors: 1

v7.5.3

📜 Update Public Suffix List

  • tldts-experimental, tldts

Authors: 1

v7.5.2

📜 Update Public Suffix List

  • tldts-experimental, tldts

🔩 Dependencies

Authors: 2

v7.5.1

🐛 Bug Fix

  • tldts-core, tldts-experimental, tldts-icann, tldts-tests, tldts
    • Fix public suffix boundary for trailing dots and empty wildcard labels #2759 (@​remusao)

Authors: 1

v7.5.0

🚀 New Feature

  • tldts-core, tldts-experimental, tldts-icann, tldts-tests, tldts

... (truncated)

Changelog

Sourced from tldts's changelog.

v7.5.4 (Sun Nov 15 2026)

📜 Update Public Suffix List

  • tldts-experimental, tldts

Authors: 1


v7.5.3 (Sat Nov 14 2026)

📜 Update Public Suffix List

  • tldts-experimental, tldts

Authors: 1


v7.5.2 (Fri Nov 13 2026)

📜 Update Public Suffix List

  • tldts-experimental, tldts

🔩 Dependencies

Authors: 2


v7.5.1 (Fri Nov 13 2026)

🐛 Bug Fix

  • tldts-core, tldts-experimental, tldts-icann, tldts-tests, tldts

... (truncated)

Commits
  • c5d091d Bump version to: v7.5.4 [skip ci]
  • a1e5d9c Update CHANGELOG.md [skip ci]
  • 5cc92d6 Update upstream public suffix list (#2764)
  • 4bece9b Bump version to: v7.5.3 [skip ci]
  • cef8cae Update CHANGELOG.md [skip ci]
  • 9be7947 Update upstream public suffix list (#2763)
  • e979ff3 Bump version to: v7.5.2 [skip ci]
  • f88f264 Update CHANGELOG.md [skip ci]

Bumps the bun group with 16 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [oxfmt](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxfmt) | `0.74.0` | `0.78.0` |
| [oxlint](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint) | `1.89.0` | `1.93.0` |
| [postgres](https://github.com/porsager/postgres) | `3.4.9` | `4.1.1` |
| [tldts](https://github.com/remusao/tldts) | `7.4.19` | `7.5.4` |
| [tsdown](https://github.com/rolldown/tsdown) | `0.23.3` | `0.23.7` |
| [hono](https://github.com/honojs/hono) | `4.13.14` | `4.13.18` |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.152.0` | `4.162.0` |
| [@astrojs/markdown-satteri](https://github.com/withastro/astro/tree/HEAD/packages/markdown/satteri) | `0.4.5` | `0.4.10` |
| [@astrojs/react](https://github.com/withastro/astro/tree/HEAD/packages/integrations/react) | `7.1.2` | `7.1.9` |
| [@tailwindcss/vite](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-vite) | `4.3.3` | `4.3.5` |
| [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `7.4.2` | `7.4.12` |
| [cn](https://github.com/shadcn-ui/cn/tree/HEAD/packages/cn) | `0.5.0` | `0.5.2` |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `1.64.0` | `1.73.0` |
| [satteri](https://github.com/bruits/satteri) | `0.10.5` | `0.11.7` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `4.3.3` | `4.3.5` |
| [useyuva](https://github.com/productdevbook/yuva/tree/HEAD/sdk/js) | `0.4.0` | `0.5.0` |



Updates `oxfmt` from 0.74.0 to 0.78.0
- [Release notes](https://github.com/oxc-project/oxc/releases)
- [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxfmt/CHANGELOG.md)
- [Commits](https://github.com/oxc-project/oxc/commits/oxfmt_v0.78.0/npm/oxfmt)

Updates `oxlint` from 1.89.0 to 1.93.0
- [Release notes](https://github.com/oxc-project/oxc/releases)
- [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxlint/CHANGELOG.md)
- [Commits](https://github.com/oxc-project/oxc/commits/oxlint_v1.93.0/npm/oxlint)

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 `tldts` from 7.4.19 to 7.5.4
- [Release notes](https://github.com/remusao/tldts/releases)
- [Changelog](https://github.com/remusao/tldts/blob/master/CHANGELOG.md)
- [Commits](remusao/tldts@v7.4.19...v7.5.4)

Updates `tsdown` from 0.23.3 to 0.23.7
- [Release notes](https://github.com/rolldown/tsdown/releases)
- [Commits](rolldown/tsdown@v0.23.3...v0.23.7)

Updates `hono` from 4.13.14 to 4.13.18
- [Release notes](https://github.com/honojs/hono/releases)
- [Commits](honojs/hono@v4.13.14...v4.13.18)

Updates `wrangler` from 4.152.0 to 4.162.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.162.0/packages/wrangler)

Updates `@astrojs/markdown-satteri` from 0.4.5 to 0.4.10
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/markdown/satteri/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/markdown-satteri@0.4.10/packages/markdown/satteri)

Updates `@astrojs/react` from 7.1.2 to 7.1.9
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/react/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/react@7.1.9/packages/integrations/react)

Updates `@tailwindcss/vite` from 4.3.3 to 4.3.5
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/@tailwindcss-vite)

Updates `astro` from 7.4.2 to 7.4.12
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/astro@7.4.12/packages/astro)

Updates `cn` from 0.5.0 to 0.5.2
- [Release notes](https://github.com/shadcn-ui/cn/releases)
- [Changelog](https://github.com/shadcn-ui/cn/blob/main/packages/cn/CHANGELOG.md)
- [Commits](https://github.com/shadcn-ui/cn/commits/cn@0.5.2/packages/cn)

Updates `lucide-react` from 1.64.0 to 1.73.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.73.0/packages/lucide-react)

Updates `satteri` from 0.10.5 to 0.11.7
- [Release notes](https://github.com/bruits/satteri/releases)
- [Commits](bruits/satteri@satteri-v0.10.5...satteri-v0.11.7)

Updates `tailwindcss` from 4.3.3 to 4.3.5
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/tailwindcss)

Updates `useyuva` from 0.4.0 to 0.5.0
- [Release notes](https://github.com/productdevbook/yuva/releases)
- [Changelog](https://github.com/productdevbook/yuva/blob/main/CHANGELOG.md)
- [Commits](https://github.com/productdevbook/yuva/commits/v0.5.0/sdk/js)

---
updated-dependencies:
- dependency-name: oxfmt
  dependency-version: 0.78.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: bun
- dependency-name: oxlint
  dependency-version: 1.93.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: bun
- dependency-name: postgres
  dependency-version: 4.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: bun
- dependency-name: tldts
  dependency-version: 7.5.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: bun
- dependency-name: tsdown
  dependency-version: 0.23.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: hono
  dependency-version: 4.13.18
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: wrangler
  dependency-version: 4.162.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: bun
- dependency-name: "@astrojs/markdown-satteri"
  dependency-version: 0.4.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: "@astrojs/react"
  dependency-version: 7.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: "@tailwindcss/vite"
  dependency-version: 4.3.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: astro
  dependency-version: 7.4.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: cn
  dependency-version: 0.5.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: lucide-react
  dependency-version: 1.73.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: bun
- dependency-name: satteri
  dependency-version: 0.11.7
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: bun
- dependency-name: tailwindcss
  dependency-version: 4.3.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: bun
- dependency-name: useyuva
  dependency-version: 0.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: bun
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 19, 2026
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