Firefly v1.1.3

Release date: September 3, 2026

v1.1.3 extends Firefly around business-time windows, data readiness, and recoverable execution. It continues to reuse the existing execution, Dispatch Outbox, CAS, and fencing boundaries without introducing a full DAG engine.

Delivered

• Added the DataReadyCondition / DataReadyConditionEvaluator SPI for composing multiple readiness checks with WAITING, BLOCKED, and fail-closed behavior for unknown conditions. The Server now discovers conditions through the classpath ServiceLoader.
• Added event aggregation and debouncing with an aggregation key, debounce window, maximum delay, latest payload, event count, and idempotent event inbox handling.
• Added a resumable backfill coordinator with bounded previews, batches, pause/resume/cancel, canary release, failed-time filtering, rate limiting, and cursor progress.
• Added execution replay plans with dry runs, job/calendar/dependency/parameter difference checks, failed-target selection, and root-execution correlation.
• Added resource-aware executor selection and SLA budget models covering CPU, memory, tags, tenant concurrency, and queue/start/complete phase assessment.
• Added business result summaries and scheduling input revisions for counts, checkpoints, result locations, SHA-256 summaries, and explainable input-version differences.

Integration boundary

This release publishes the public models, SPIs, core services, and in-memory coordinators. Data-readiness conditions are wired into the Server runtime. Event aggregation state, backfill cursors, replay endpoints, and resource snapshots are not yet connected to JDBC persistence or Admin HTTP/UI; future wiring must preserve the existing execution/Outbox, CAS, and fencing mechanisms.

Version information

• Maven Central: io.github.fishered:firefly-bom:1.1.3
• Spring Boot Starter: io.github.fishered:firefly-spring-boot-starter:1.1.3
• Container default tag: 1.1.3
• Source tag
• GitHub Release
• Maven Central

Verification

Before publication, the project passed check, the full Java test suite, verifyPluginCompatibilityMatrix, and verifyMavenCentralPublication. Maven Central publication was completed by GitHub Actions.