Repository navigation
chore(deps): update dependency kysely to v0.29.9 - #231
Merged
Merged
Conversation
jackchuka
approved these changes
Nov 16, 2026
jackchuka
left a comment
Member
There was a problem hiding this comment.
kysely 0.29.8 → 0.29.9 (patch, bug fixes incl. migrator timestamp). Safe to merge.
renovate
Bot
force-pushed
the
renovate/kysely-0.x
branch
from
November 16, 2026 02:16
4007623 to
bee99d2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.29.8→0.29.9Release Notes
kysely-org/kysely (kysely)
v0.29.9: 0.29.9Compare Source
Hey 👋
A small batch of bug fixes. Please report any issues. 🤞😰🤞
Kysely's migrator no longer records timestamps that go backwards when the wall clock jumps back during a migration run (WSL2/VM time sync, an NTP step, an unsmeared leap second). Such timestamps made every later
migrateToLatest()fail with "corrupted migrations", even though the migrations ran in the correct order. The migrator now reads the latest recorded timestamp while holding the migration lock, and records each new migration atmax(now, latest + 1ms), so the order holds across runs and hosts. Executed migrations with an invalidtimestampnow fail with "corrupted migrations" instead of being sorted arbitrarily.Migration tables that already have out-of-order timestamps need a one-time repair. Run the query for your dialect below. It goes through executed migrations in name order, which is the order the migrator runs them in by default, and moves every timestamp that isn't later than the previous one to 1 millisecond after it. Running it again changes nothing.
Replace
kysely_migrationwith your migration table's name, prefixed with the schema if you setmigrationTableSchema. Run it while no migrations are running. Skip this if you useallowUnorderedMigrations: true. Name order isn't the execution order in that mode, and out-of-order timestamps don't block migrations there.PostgreSQL and PGlite:
MySQL 8.0+:
MS SQL Server 2016+:
SQLite 3.33+:
The binary collations (
collate "C",cast(name as binary), etc.) make the database sort names the same way the migrator does in JavaScript.Also, PGlite 0.5.15+ commits that roll back aborted transactions now throw
AbortedTransactionError, same as PostgreSQL since0.29.8.🚀 Features
🐞 Bugfixes
key()/at()JSON path references inferunknowninjsonBuildObject. by @igalklebanov in #2228PostgreSQL 🐘 / PGlite 🟨
withSchemacrashes onfor ... ofandjson_agg/to_jsontables in subqueries. by @igalklebanov in #2227PGlite 🟨
📖 Documentation
📦 CICD & Tooling
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)🐤 New Contributors
What's Changed
Full Changelog: kysely-org/kysely@v0.29.8...v0.29.9
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.