1.15.0

Downstream planning impacts

2026-10-27 · #118 · closes #117

Approving an apply now shows what it does to the Modules downstream of it.

When a plan changes an output another Module reads, Snap CD asks that Module to plan against the new value and reports what it finds, before the approval decision. A value the plan cannot work out yet is passed on as unknown, so each Module's own providers decide whether it forces a replacement. Chains are answered hop by hop.

The approval screen shows each downstream Module's prediction and its logs, and summarises the wave above them. A prediction whose inputs have since moved is marked stale, and you can ask for another without losing the first.

Runner logs are now stored in chunks, which keeps writing a log batch the same cost however large the log has grown.