v2.10.4

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