Upgrade to 1.1

Additive release. Existing schema_version: 1.0 definitions remain valid. Pair all three packages at ^1.1.

This guide covers upgrading from 1.0.x to 1.1.0 for Core, Filament Standard, and optional DBFlow Pro.

Compatibility

Requirement 1.1
PHP 8.3+
Laravel 13.x
Filament (UI packages) 5.6+
Production database MySQL 8.0+ (SQLite for local/tests)
Composer constraints dbflowlabs/core:^1.1, dbflowlabs/filament:^1.1, optional dbflowlabs/filament-pro:^1.1

Install

composer require dbflowlabs/core:^1.1 dbflowlabs/filament:^1.1
php artisan migrate

With Pro:

If you customized config/dbflow-filament-pro.php, back it up before publishing. The --force flag replaces the existing file; merge your host-specific values back afterward.

composer require dbflowlabs/filament-pro:^1.1
php artisan vendor:publish --tag=dbflow-filament-pro-config --force
php artisan filament:assets

Publish Core config only when you need new v1.1 sections (delegation, sla, actions, webhook, reassignment):

php artisan vendor:publish --tag=dbflow-config

Scheduler and queue

If you adopt SLA, reliable actions, or outbound webhooks, register scheduler entries and run a queue worker:

Schedule::command('dbflow:sla-dispatch')->everyMinute();
Schedule::command('dbflow:sla-recover')->everyFiveMinutes();
Schedule::command('dbflow:actions-dispatch')->everyMinute();
Schedule::command('dbflow:actions-recover')->everyFiveMinutes();
Schedule::command('dbflow:process-timeouts')->everyMinute(); // legacy approval timeouts only
php artisan queue:work --tries=1
php artisan dbflow:diagnostics

Legacy approval timeouts (timeout.due_in without v1.1 SLA) continue to use dbflow:process-timeouts. Tasks on the v1.1 SLA path are excluded from that command.

What changed for hosts

Area Host impact
Migrations Additive tables/columns only (delegations, SLA events, action executions/attempts, assignment provenance, task SLA fields)
Public API New methods: DBFlow::createDelegation(), revokeDelegation(), migratePendingTasksToDelegate() — existing 1.0 methods unchanged
Definitions Optional schema_version 1.1 fields for SLA, reliable actions, webhooks, provenance metadata
Filament Standard Read-only Delegations and Action Executions pages; provenance and SLA visibility
Pro Canvas inspectors, delegation management, action recovery, operational summary widget

Checklist

  • Pin ^1.1 for Core (and Filament / Pro if used)
  • Run migrations on staging
  • Merge new config/dbflow.php sections you will use
  • Register SLA / action scheduler commands when enabling those features
  • Confirm a queue worker is running (dbflow:diagnostics)
  • Update Filament permission_checker_class for new abilities — see Permissions
  • Keep v1.0 definitions as-is until you intentionally adopt schema_version 1.1 fields

Related

Something wrong? Open an issue on GitHub