akm-cli 0.9.16 → 0.9.17-alpha.10

package/dist/tasks/backends/exec-utils.js

@@ -51,11 +51,8 @@ export function spawnCommand(args) {
 /**
  * Throw a `ConfigError` (code `INVALID_CONFIG_FILE`) when `result` doesn't
  * satisfy `isOk` (default: `status === 0`); otherwise return `result`
- * unchanged. Factors out the "run a native scheduler command, throw a
- * formatted error on a bad exit" idiom repeated across the cron/launchd/
- * schtasks backends — NOT the accumulate-into-`rollbackErrors`-and-continue
- * idiom used during rollback, which stays inline (throwing there would
- * change control flow: rollback needs to keep trying its remaining steps).
+ * unchanged: the "run a native scheduler command, throw a formatted error on
+ * a bad exit" idiom shared by the cron/launchd/schtasks backends.
  */
 export function throwIfNotOk(result, options) {
     const ok = options.isOk ? options.isOk(result) : result.status === 0;