Release 1.3.0

Date of Release: 12 Aug 2026

Added the --overall-timeout-seconds argument, which bounds the run as a whole rather than each file. --timeout-seconds limits the work done on each file. --overall-timeout-seconds limits the whole process, so it also covers a run that stops making progress while waiting on a worker. When it fires, Conform writes a message to standard error, stops any workers it started and exits with a non-zero code. It defaults to --timeout-seconds plus 120 seconds in the memory modes (engine_memory and conform_only_memory), which process a single file, and is disabled in the directory modes, where the total amount of work is unbounded. Set it to 0 to disable it. For more details, see: User Guide: Multiprocessing.

Fixed an issue where a perpetual license, which has no expiry date, was rejected as invalid.
Fixed an issue where a failure could produce no output at all. Some errors were reported while output was still redirected, so the process exited with a non-zero code and no message explaining why.
Fixed intermittent failures and hangs in conform_only_memory on Windows, caused by a worker that exited part-way through returning its result.
Fixed an issue where a run stopped by --overall-timeout-seconds could leave worker processes running after it exited.

Release 1.3.0​