Kysely v0.29.9
0.29.9
This release fixes migration timestamp ordering when the system clock moves backwards, preventing valid migration histories from being treated as corrupted. It also fixes JSON-path type inference and PostgreSQL/PGlite subquery behavior, and includes a breaking change to the typing API for `key()` and `at()`.
Users relying on the second type argument to `key()` or `at()` must update their code; users with previously out-of-order migration timestamps may need to repair their migration table.
Update affected `key()` and `at()` calls to use `$castTo<T>()`, and repair existing out-of-order migration timestamps using the provided query for your database dialect if applicable.
- 01If the migration table already contains out-of-order timestamps, run the dialect-specific repair query from the release notes once, while no migrations are running. Replace `kysely_migration` with the actual migration table name, including its schema if configured.
- 02Skip the timestamp repair if `allowUnorderedMigrations: true` is enabled.
# community_signal
How useful is this release to your stack?
Sign in with GitHub to cast your vote.
You’ll return to this release, then choose your vote.