kysely
0.29.9 · 12 Nov 2026MIT32M / weekRepositoryHomepagenpmAtom feed
Upgrading kysely From 0.29.0 to 0.29.9
9 releases in betweenevery note read
Reading releases, release notes and advisories…
- 2
- changes to make
- 0
- advisories fixed
- 1
- new
- 20
- fixes
Before you upgrade
Tick each one off as you go- Breaking0.29.9
- Breaking0.29.3
Release by release
- Breaking
key()andat()no longer accept a 2nd type argument for the output type (e.g..key<'url', number>('url')). It was never documented. Use$castTo<T>()to override the output type. (#2228) - Fixed
Inline
key()/at()JSON path references inferunknowninjsonBuildObject. - Fixed
Migration timestamps go backwards when the clock jumps back.
- Fixed
withSchemacrashes onfor ... ofandjson_agg/to_jsontables in subqueries. - Fixed
pglite: Reject commits that roll back aborted transactions
- Breaking
- Fixed
postgres: Discard clients after failed rollbacks
- Fixed
postgres: Reject commits that roll back aborted transactions
- Fixed
- Fixed
Release controlled transaction connection when begin fails
- Fixed
Share completion state between controlled transaction handles
- Fixed
Release controlled transaction connection when rollback fails
- Fixed
Serialize controlled transaction commands with queries
- Fixed
postgres: Release the client when destroyed while acquiring a connection by @abebelagua & @igalklebanov
- Fixed
mssql: Escape
jsonBuildObjectkeys. - Fixed
mssql: Escape JSON in
jsonBuildObject
- Fixed
- Fixed
Allow immutable columns in
doUpdateSet'swhere.
- Fixed
- New
Add missing beforeThrow calls in getInflightQueryAbortHandler
- Fixed
Fix infinite type check recursion
- New
- Fixed
Fix postgres password not being passed to control client by @CakeWithDivinity & @igalklebanov
- Fixed
sqlite: Returning clauses wrongfuly output after order by and limit in delete queries.
- Fixed
- Breaking
PostgreSQL migrations now use session-level advisory locks, including when transactions are enabled. This is incompatible with PgBouncer transaction pooling and other transaction-mode connection poolers. Run migrations through a direct connection, session pooling, or custom migration locking. Otherwise, migration locks can remain held on pooled connections and block subsequent migration runs. See #1919 and #2200.
- Fixed
PostgreSQL and MSSQL migrations are not running exclusively when
disableTransactions: true. by @morgan-coded & @igalklebanov
- Breaking
- Fixed
$narrowTypemishandling branded types.
- Fixed
5 other lines we could not sort, mostly version bumps
- 0.29.8
Clients whose rollback fails are discarded instead of returned to the pool for reuse.
- 0.29.8
Commits that PostgreSQL turns into rollbacks now throw
AbortedTransactionErrorinstead of reporting success. Controlled transactions are marked as rolled back and release their connection; a subsequentrollback().execute()safely succeeds without sending another rollback. - 0.29.7
Commit, rollback, and savepoint commands now wait for ongoing queries and streams to finish.
- 0.29.7
Close or exhaust active streams before awaiting these commands.
- 0.29.7
A failed rollback now releases the connection and marks the transaction as rolled back.
125 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.