Firefly v1.1.1

Release date: August 30, 2026

v1.1.1 focuses on production foundations and operability. Core scheduling semantics, business-calendar and batch-processing models are now wired through persistence and runtime boundaries, and the Admin UI provides a practical calendar editor.

Features in this version

• The Admin business-calendar editor supports multi-month views, multi-select, Ctrl/Command additive selection, Shift ranges, drag selection, and bulk application of workday, holiday, or default day types.
• Added core SPI/models for calendars, blackout windows, job dependencies, event inboxes, bounded backfills, and batch repositories while retaining Outbox, root-execution, retry, and fencing semantics.
• JDBC additive migrations add calendar metadata, date rules, and import-batch tables without overwriting existing task data.
• Netty execution results are persisted asynchronously with idempotency by root execution/shard/attempt, stale-attempt fencing, rate-limited progress updates, and Prometheus metrics.
• Release defaults, Docker examples, the compatibility matrix, and Maven Central publishing flow are aligned to 1.1.1.

Official holiday provider status

This release ships the HolidayProvider SPI, dataset validator, and classpath-provider production interfaces. It does not bundle unaudited official annual data or present static examples as a legal-holiday source of truth. A jurisdiction integration should provide audited yearly datasets with SHA-256 checksums and use import batches for preview, validation, and publication.

Database scripts

Download the incremental scripts for your database dialect:

• PostgreSQL scripts
• MySQL scripts
• H2 scripts

Back up the production database first, then apply the files in filename order for the selected dialect. Additive schema initialization remains supported.

Version information

• Maven Central: io.github.fishered:firefly-bom:1.1.1
• Container default tag: 1.1.1

Verification

Run verifyReleaseVersion, verifyMavenCentralPublication, and the Admin UI npm run check before publishing. Full Gradle tests require a build host capable of loading Gradle native services.