Update dependency postgres to v4.1.1 #240

Merged
renovate-bot merged 1 commits from renovate/postgres-4.x into main 2026-11-12 05:29:11 +01:00
Collaborator

This PR contains the following updates:

Package Change Age Confidence
postgres 4.1.0 → 4.1.1 age confidence

Release Notes

porsager/postgres (postgres)

v4.1.1

Compare Source

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.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [postgres](https://github.com/porsager/postgres) | [`4.1.0` → `4.1.1`](https://renovatebot.com/diffs/npm/postgres/4.1.0/4.1.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/postgres/4.1.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/postgres/4.1.0/4.1.1?slim=true) | --- ### Release Notes <details> <summary>porsager/postgres (postgres)</summary> ### [`v4.1.1`](https://github.com/porsager/postgres/blob/HEAD/CHANGELOG.md#v411---11-November-2026) [Compare Source](https://github.com/porsager/postgres/compare/v4.1.0...v4.1.1) ##### Fixed - **A statement `sql.begin` sends after its own `COMMIT` or `ROLLBACK` is rejected** ([#&#8203;1320](https://github.com/porsager/postgres/issues/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** ([#&#8203;1321](https://github.com/porsager/postgres/issues/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** ([#&#8203;1319](https://github.com/porsager/postgres/issues/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** ([#&#8203;1312](https://github.com/porsager/postgres/issues/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`** ([#&#8203;1317](https://github.com/porsager/postgres/issues/1317), [#&#8203;1318](https://github.com/porsager/postgres/issues/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** ([#&#8203;1313](https://github.com/porsager/postgres/issues/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`. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4yMjUuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjIyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate-bot added 1 commit 2026-11-12 05:19:38 +01:00
Update dependency postgres to v4.1.1
CI / full-gate (push) Successful in 5m37s
Mirror / github-mirror (push) Successful in 3s
Release / retag-image (push) Successful in 16s
Release / publish-overview (push) Successful in 3s
fca74e5f7c
Release-Bump: patch
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-11-12 05:19:38 +01:00
renovate-bot merged commit fca74e5f7c into main 2026-11-12 05:29:11 +01:00
renovate-bot deleted branch renovate/postgres-4.x 2026-11-12 05:29:12 +01:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: larvit/plainpages#240