Release 0.7.0
Summary
Release 0.7.0 delivered the architectural changes that powered our 1.x series: threaded job execution, worker channels, and a hardened licensing flow.
Released: 14 Oct 2024
Highlights
- Jobs now run as threads by default, aligning worker throughput with the new runtime envelope.
- Worker channels graduated from prototype to first-class configuration, enabling fan-in/fan-out patterns between jobs.
- Licensing moved to the modern scheme: a valid key is required after upgrading the server, with UI updates for machine ID, status, and error handling.
- Object store inputs switched to streaming reads with resume support to avoid out-of-memory failures on large objects.
Fixes and improvements
- WebSocket cleanup prevents dangling connections during long UI sessions.
- Batch timeouts respect the configured limits, and
/api/jobs/runnow conveys cancellation reasons (including timeout) back to the UI. - DSL enhancements restore
rawaction functionality, add discard-until filters, expand extract output options, and align meta variable expansion (${meta_var|stat}).
Breaking changes
- After upgrading to 0.7.0 the server requires a valid license before executing jobs. Ensure keys are provisioned ahead of rollout.
- Job specification storage moved to the new runtime schema. Verify custom tooling that reads the staging database before upgrading.
Known issues
- The visual editor’s key-value action still lacks advanced options; use the raw editor when you need conditional values.
- If you maintain tooling that reads the staging database directly, review changes between 0.6.x and 0.7.x before rolling the server upgrade.
Looking ahead
- Variable expansion unification and the remaining runtime envelope work followed shortly after in 0.8.x as we headed toward 1.0.