Firefly v1.1.5
Release date: September 30, 2026
v1.1.5 completes the production workflow for backfill and execution replay. It connects the public models, job snapshots, and failed-target semantics delivered in 1.1.3/1.1.4 to JDBC, Admin HTTP, and the standalone management console, giving operators a safe way to preview, stage, recover, and replay historical executions.
Delivered
- Backfill operations, fire times, cursors, canary state, and next-allowed dispatch time are now persisted in JDBC. H2, MySQL, and PostgreSQL create the new tables through additive v18 feature migrations.
- API nodes compete for backfill operations through leases and fencing tokens. After a node exits or restarts, another worker resumes at the durable cursor without redispatching executions that already exist.
- The Admin API exposes backfill preview, creation, listing, details, pause, resume, cancel, and canary promotion while preserving batch-size, per-second rate, and maximum-execution bounds.
- The Admin UI adds a Backfills page that previews fire-time count, estimated duration, and canary size before submission, then tracks dispatched, failed, and remaining progress.
- Execution replay reads the immutable job snapshot from the original Outbox record and compares it with current parameters, calendar, and dependency inputs. Changed definitions are shown to the operator and require explicit confirmation.
- Replay can target only failed, timed-out, or missing broadcast/shard targets while continuing to use the existing execution-and-Outbox idempotency and reliable-delivery boundary.
Compatibility and integration boundary
This release preserves the Plugin API level, Executor Protocol range, and core database schema compatibility range. Backfill tables are created through repeatable additive feature migrations. In a multi-API-node deployment, every node may run a worker; database leases and fencing decide which node advances each operation, so no separate backfill service is required.
Version information
- Maven Central:
io.github.fishered:firefly-bom:1.1.5 - Spring Boot Starter:
io.github.fishered:firefly-spring-boot-starter:1.1.5 - Container default tag:
1.1.5 - Source tag
- GitHub Release
- Maven Central
Verification
The release gates cover the complete Gradle suite, plugin compatibility and publication artifacts, Admin UI static checks and Playwright E2E, PostgreSQL/MySQL real-database tests, and the Spring Boot 3.3.5, 3.4.12, 3.5.8, and 4.0.0 compatibility matrix. Maven Central publication was performed by GitHub Actions.