v0.8.1

cronicle v0.8.1

A bug-fix release: cronicle exec now reports failures instead of always exiting successfully.

Fixed

• cronicle exec exits non-zero when a schedule fails. When running whole schedules (without --task), errors from a schedule's task DAG were logged but dropped, so exec exited 0 even when tasks failed. (--task runs already exited non-zero on failure.) Failures now propagate to the exit code. Every schedule, and every day in a --time/--end range, still runs, and cleanup still happens. All failures are collected and reported together at the end.
• Unknown schedule or task names are rejected. cronicle exec --schedule <name> or --task <name> with a name that doesn't exist in the config used to do nothing and exit 0. It now fails with unknown schedule "<name>" or unknown task "<name>" in selected schedules.

Upgrade note

Scripts, CI jobs, or wrappers that call cronicle exec may now see a non-zero exit code where they previously saw success. That is the intended fix, but check any automation that relied on the old behavior.

Changes

• Return failures from foreground schedule execution (#170)

Full changelog: v0.8.0...v0.8.1