Skip to content

dagu

v2.10.4 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 17d Automation & Workflows
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agentic-workflow cron data-pipeline devops durable-execution durable-workflows
+14 more
human-in-the-loop job-scheduler mcp-server multiplayer-agent on-premise private-runners self-hosted self-service selfservice-portal task-automation task-scheduler workflow-engine workflow-orchestration workflow-scheduler

Affected surfaces

rce_ssrf

Summary

AI summary

Added explicit eval support for dynamic precondition evaluation and fixed a regression where valid preconditions were incorrectly treated as unmet.

Changes in this release

Feature Medium

Adds explicit `eval` support for precondition dynamic evaluation.

Adds explicit `eval` support for precondition dynamic evaluation.

Source: llm_adapter@2026-07-16

Confidence: high

 —
Bugfix Medium

Fixes regression where valid preconditions were incorrectly treated as unmet.

Fixes regression where valid preconditions were incorrectly treated as unmet.

Source: llm_adapter@2026-07-16

Confidence: low

 —
Bugfix Low

Stabilizes Windows cancellation CI coverage.

Stabilizes Windows cancellation CI coverage.

Source: llm_adapter@2026-07-16

Confidence: high

 —
Bugfix Low

Preserves retry status metadata across DAG run status updates.

Preserves retry status metadata across DAG run status updates.

Source: llm_adapter@2026-07-16

Confidence: high

 —
Full changelog

This release adds explicit eval support for preconditions and fixes a precondition regression reported in recent 2.x releases.

Preconditions now have a clearer split between value comparison and dynamic evaluation:

# Compare a resolved value
preconditions:
  - condition: "${env.ENVIRONMENT}"
    expected: "production"

# Compare dynamically evaluated command output
preconditions:
  - eval: "$(date +%u)"
    expected: "re:[1-5]" # weekdays only

# Check command exit status
preconditions:
  - condition: "test -f /data/ready.flag"

Added

  • Added conformance coverage for DAG-level and step-level precondition behavior. (#2369) @yohamta0
  • Added eval as an explicit dynamic value source for preconditions with expected. (#2373) @yohamta0

Fixed

  • Fixed precondition evaluation so valid preconditions are not incorrectly treated as unmet. (#2369) @yohamta0
  • Stabilized Windows cancellation CI coverage. (#2370) @yohamta0
  • Preserved retry status metadata across DAG run status updates. (#2374) @yohamta0

Contributors

Thanks to our contributors for this release:

| Contribution | Contributor |
| --- | --- |
| Reported that preconditions were always unmet since 2.8.3 (#2367) | @jeremydelattre59 |

View diff on GitHub

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

Share on X Share on Bluesky

Track dagu

Get notified when new releases ship.

Sign up free

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.

All releases →

Related context

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]