What is the current maintenance status of Postgres.js? #1222

Hi, could we get an update on the maintenance status of Postgres.js and what users and contributors should expect regarding PR reviews and releases?

I recently reported #1219, where fetch_types: false causes reserve() to hang indefinitely. Another contributor opened #1220 with a small control-flow fix and a regression test, but there hasn’t been a maintainer response yet.

That PR is only a week old, so it wouldn’t be concerning on its own. What prompted this question is seeing other production-impacting bugs with small proposed fixes still open. These are just a few examples, not an exhaustive list:

• #1016, January 2025: queries can hang indefinitely after a COPY stream. The proposed fix adds one source line to resume the socket, plus a regression test. The maintainer responded positively, the author subsequently reported green CI, and multiple users have reported production impact since.
• #1120, October 2025: an error partway through a query leaves a stale row counter, causing subsequent queries to return malformed result arrays. The proposed fix adds one source line resetting the counter, plus a regression test.
• #1167, April 2026: cursor errors between batches can be silently swallowed, so iteration appears to finish successfully with missing rows. The proposed fix adds a few lines to preserve and propagate the error, plus a regression test.

I appreciate the work that has gone into this library, and I know even small database client changes need careful review. For those of us depending on it, though, it’s difficult to know whether to wait for upstream fixes, maintain patches locally, or reconsider that dependency.

Is there an expected cadence for reviewing fixes and publishing releases? Even a brief status update would help users plan and contributors understand whether their work is likely to receive feedback.