Firefly v1.0.8

Release date: August 25, 2026

v1.0.8 focuses on release consistency, a closed verification loop, and production observability foundations. It leaves the published v1.0.7 tag unchanged and aligns defaults on a new release commit.

Published release

The v1.0.8 source tag and GitHub Release are published; Maven Central artifacts are pushed by the tag-driven publishing workflow. See the source tag, GitHub Release, and Central Portal.

Release consistency

• Gradle, .env.example, Dockerfiles, Docker Compose, README, and deployment examples use 1.0.8 consistently.
• JAR manifests include Implementation-Version, allowing plugins to report the actual build version in production.
• verifyReleaseVersion checks container defaults and documentation examples before publication.

Compatibility verification

• The CI Java job runs check and verifyPluginCompatibilityMatrix, not only unit tests.
• Maven Central publication performs the same compatibility and release-version checks.
• The rolling matrix includes a v1.0.8 node and compares the tracing plugin's runtimeCompatibility() declaration with the JSON contract.

Trace boundaries

• OpenTelemetry service.version prefers the host build version.
• Persisted and transported carriers allow only traceparent, tracestate, and baggage.
• Values are limited to 4096 characters and the complete carrier to 8192 characters, preventing sensitive or oversized fields from entering Outbox snapshots.
• Tests cover carrier filtering, size limits, and the service-version resource.

Compatibility

• No database schema migration.
• No Netty/Executor protocol change.
• No Admin API request or response format change.
• v1.0.7 can roll forward to v1.0.8 directly.

Verification

• Plugin compatibility matrix validation passes.
• Targeted scheduler-core, tracing-opentelemetry, JDBC, and Netty tests pass.
• GitHub Actions runs the complete CI after the PR merge; the publishing workflow uses the v1.0.8 tag for Maven Central release.