This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+14 more
Summary
AI summaryAdded dagu validate --show-unresolved to inspect unresolved references at run time.
Full changelog
v2.11.1 is a focused correctness and safety release for workflow validation, harness-based workflows, and local sub-DAG execution.
Added
- Added
dagu validate --show-unresolvedfor inspecting references that are expected to receive values at run time. (#2450) @yohamta0
Changed
- Validation notices and the Web UI now separate “Needs a fix” defects from references resolved during a run. (#2450) @yohamta0
- Removed redundant
artifacts.enableddeclarations from bundled examples that already enable artifact storage through their usage.
Fixed
- Prepared declared tools for local sub-DAGs and official actions, restoring their tool binaries on
PATH. (#2452) @yohamta0 - Rejected legacy prompt-shaped
command:steps under a DAG-levelharness:block with an explicit migration error. (#2448) @yohamta0 - Clarified that run-scoped context values are populated during execution instead of implying they are invalid in the field where they appear. (#2449) @yohamta0
- Corrected validation scope and classification for step environments,
foreachreferences, and step working directories. (#2450) @yohamta0
Full Changelog: https://github.com/dagucloud/dagu/compare/v2.11.0...v2.11.1
Breaking Changes
- Legacy prompt-shaped `command:` steps under a DAG-level `harness:` block are now rejected with an explicit migration error.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About dagu
A local-first workflow engine built the way it should be: declarative, file-based, self-contained, air-gapped ready. One binary that scales from laptop to distributed cluster. Your Workflow Operator handles creating and debugging workflows.
Related context
Related tools
Earlier breaking changes
- v2.10.6 Built-in authentication token TTLs are now limited to 8760h (365 days); larger values are rejected at startup.
Beta — feedback welcome: [email protected]