25 June, 2026

This release introduces the keel db reset command and automatic seeding for fresh databases, streamlining local development workflows.

keel db reset Command

A new keel db reset command drops and recreates your project's development database. This replaces the previous keel run --reset flag, which is now deprecated.

The recommended workflow for resetting your local database is now:

keel db reset
keel run

keel run --reset still works but prints a deprecation notice. Use keel db reset going forward.

Auto-seeding on Fresh Databases

keel run now automatically applies your seed data when it detects an empty database — for example, on a first run or after a keel db reset. Previously, seeding only happened when using --reset.

If you want to skip auto-seeding, use the new --no-seed flag:

keel run --no-seed

Fixes and Improvements

• Flows: fixed steps appearing stuck in a running state after their flow run was cancelled or failed. Failed runs now record the failure reason instead of showing no error.
• Flows: improved performance for flows with many steps by reducing redundant state reads.
• Seeding: keel seed snapshot now writes to seed/snapshot.sql so snapshots are correctly applied on the next seed.

For a full list of changes, check out our GitHub releases page (opens in a new tab).

For any issues or feedback, please contact us at help@keel.so.

Thank you for using Keel!