v1.11.0 — defprod-stamp skips fail/cancel with no in-progress stage

Changed

• defprod-stamp --fail and --cancel now skip any change that has no stage work in progress. They print skipped: no in-progress stage (<stage> is <state>) and send nothing, where previously they sent a call the server could only reject. This removes the burst of rejections a --range produces when a build fails twice in a row and the range baseline stays put.

Compatibility

• No new flags; exit status is unchanged (stamping still exits 0).
• A server whose getChange does not report the stage state still receives the call, exactly as before.
• Probe for support with defprod-stamp --help | grep skips-not-in-progress-fail-cancel.

Upgrade: npm install -g @defprod/scripts or npx @defprod/scripts defprod-stamp.