1.8.1
What's Changed
Migration publishing now uses a current timestamp
chronicle:install previously delegated migration publishing to vendor:publish, which copied files verbatim — leaving them without a date prefix. Migrations without a timestamp are valid but inconsistent with the rest of a Laravel project's database/migrations directory.
Starting in 1.8.1, the install command stamps each published file at publish time:
database/migrations/
2026_05_25_120000_create_chronicle_checkpoints_table.php
2026_05_25_120001_create_chronicle_entries_table.php
This matches the behavior of php artisan make:migration and integrates cleanly with migrate:status, rollback ordering, and IDE migration tooling.
Re-running chronicle:install --force republishes with a fresh timestamp. Running without --force is safe — files whose base name already exists in database/migrations are skipped.
Migrations consolidated into two files
The nine incremental migration files (one per column group added across the 1.x lifetime) have been replaced by two clean files:
create_chronicle_checkpoints_tablecreate_chronicle_entries_table
Fresh install now run two migrations instead of nine. The schema is identical — this is a packaging improvement only. Existing installations are not affected.
Full Changelog: 1.8.0...1.8.1