@runfile/cli 0.42.0 → 0.44.0

package/README.md

@@ -614,6 +614,15 @@ Wrap any commands in a `when:` block to run them only after a failure, or always
 ]
 ```
 
+**Ctrl+C runs your cleanup too.** Pressing Ctrl+C stops the running command and skips everything still pending,
+but `when: failure` and `when: always` blocks still execute before Runfile exits (with code `130`) — so a
+container, a lock file, or a dev server started earlier gets torn down instead of leaked. The interrupt is not
+suppressible by `ignoreErrors` (that forgives a failed command, not a user asking to stop), it stops `for` loops
+from starting further iterations, and it reaches every target on the stack: an interrupted `@target` dependency
+runs its own cleanup, then its caller runs the caller's. Cleanup blocks are exempt from the abort, so their own
+steps — including a `@teardown` they delegate to — run in full. Press Ctrl+C **again** to quit immediately if a
+cleanup block is itself slow or stuck.
+
 #### Single-shell mode with `sameShell`
 
 By default each step runs in its own shell process, so `cd`, exported variables, and other shell state don't carry
@@ -684,6 +693,7 @@ provenance so a client can bucket local vs. included vs. global targets itself:
     {
       "filePath": "/abs/path/Runfile.json",
       "kind": "local",              // "local" | "included" | "global"
+      "onlyInDirectories": ["~/w"], // only on globals restricted to certain dirs
       "targets": [
         {
           "name": "api:build",      // full canonical invocation name
@@ -696,6 +706,11 @@ provenance so a client can bucket local vs. included vs. global targets itself:
 }
 ```
 
+`onlyInDirectories` appears only on a `global` source that declared
+[`globals.onlyInDirectories`](.github/DOCS.md#onlyindirectories) — meaning it merged in only because the
+current directory is inside one of those paths. Such a source is registered machine-wide but scoped in
+practice, so clients are expected to treat it as project-local rather than truly global.
+
 Skip a target from the generated configs by setting `metadata.excludeFromGenerateCommand: true`. The
 `metadata` block on `globals` and on each target is **fully open** — any property of any JSON type
 (strings, numbers, booleans, arrays, deeply-nested objects) is accepted and round-trips untouched, so

package/package.json

@@ -13,5 +13,5 @@
 	"license": "MIT",
 	"name": "@runfile/cli",
 	"repository": "https://github.com/JoaaoVerona/runfile",
-	"version": "0.42.0"
+	"version": "0.44.0"
 }