@vzn/vx-reapi 0.0.651 → 0.0.652

package/README.md

@@ -427,7 +427,7 @@ reapi({
 A cache-only server (bazel-remote advertises `exec_enabled: false`) makes the
 plugin **decline the executor with a warning** rather than submit work that
 will never be answered. Only cacheable tasks are eligible — a task with no
-`cache` block has no described inputs, so a worker would run it against an
+`cache: true` has no described inputs, so a worker would run it against an
 empty input root. A cacheable task's root holds its declared input files.
 
 Verified end-to-end against a live NativeLink scheduler + worker: input tree
@@ -452,14 +452,13 @@ the packages a build needs. The answer is the design doc's §7.4 recipe,
 install: {
   exec: { command: 'bun install --frozen-lockfile', remote: 'only' },
   inputs: { files: ['package.json', 'bun.lock'] },
-  cache: {
-    outputs: { files: ['node_modules/**'] },
-  },
+  outputs: { files: ['node_modules/**'] },
+  cache: true,
 },
 build: {
   dependsOn: ['install'],
   exec: { command: 'tsc -p .' },
-  inputs: { files: ['src/**'] }, cache: { outputs: { files: ['dist/**'] } },
+  inputs: { files: ['src/**'] }, outputs: { files: ['dist/**'] }, cache: true,
 },
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vzn/vx-reapi",
-  "version": "0.0.651",
+  "version": "0.0.652",
   "license": "MIT",
   "description": "Bazel Remote Execution API plugin for vx — remote cache (ActionCache + CAS) against NativeLink, BuildBuddy, Buildbarn or bazel-remote.",
   "keywords": [
@@ -39,7 +39,7 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@vzn/vx": "^0.0.651"
+    "@vzn/vx": "^0.0.652"
   },
   "repository": {
     "type": "git",

package/src/executor.ts

@@ -533,7 +533,7 @@ export interface ReapiExecutorOptions {
 
 /**
  * A task is remote-eligible only if vx can DESCRIBE its inputs — that is the
- * miss path of a cacheable task. A task with no `cache` block ships nothing,
+ * miss path of a cacheable task. A task without `cache: true` ships nothing,
  * so a worker would run it against an empty input root and produce garbage:
  * decline it and let a later executor (the local one) take it.
  */
@@ -709,7 +709,7 @@ export function reapiExecutor(client: ReapiClient, opts: ReapiExecutorOptions =
 
       const projectRel = toPosix(path.relative(req.workspaceRoot, req.cwd))
       // REAPI `output_paths` are relative to `working_directory`, so a
-      // ROOT-anchored output (`cache.outputs.workspaceFiles`) declared by a
+      // ROOT-anchored output (`outputs.workspaceFiles`) declared by a
       // NESTED project can only be spelled with `..` — `packages/vx/../..
       // /node_modules`. The spec allows `..` in SYMLINK targets but servers
       // are entitled to refuse it in output paths, and NativeLink does