@runveric/cli 0.3.0 → 0.4.0

package/README.md

@@ -4,7 +4,7 @@
 production runner image — without pushing anything or signing in.**
 
 ```sh
-npx @runveric/cli@0.3.0 init --id yourteam/restart-web-tier
+npx @runveric/cli@0.4.0 init --id yourteam/restart-web-tier
 ```
 
 ---
@@ -32,14 +32,14 @@ script outside the platform. Nothing in the product offered that. This does.
 
 ## Requirements
 
-- **Node.js 20 or newer** — for `init`, `check` and `publish`.
+- **Node.js 22 or newer** — for `init`, `check` and `publish`.
 - **Docker** — for `test` only.
 - An **Runveric account** — for `publish` only.
 
 ## Install
 
 ```sh
-npx @runveric/cli@0.3.0 <command>     # no install
+npx @runveric/cli@0.4.0 <command>     # no install
 npm install -g @runveric/cli          # or install the `runveric` bin
 ```
 
@@ -62,7 +62,7 @@ Pin the version your Runveric deployment shows you on its Author page rather tha
 Scaffold a PowerShell action, look at what you got, validate it, and run it locally:
 
 ```sh
-$ npx @runveric/cli@0.3.0 init restart-web-tier \
+$ npx @runveric/cli@0.4.0 init restart-web-tier \
     --id acme/restart-web-tier \
     --interpreter powershell \
     --yes
@@ -172,21 +172,21 @@ publish and verify with these commands:
 
 ```sh
 # one action's manifest, verbatim — stdout: <key>=<repository>@<digest>
-npx @runveric/cli@0.3.0 catalog publish-action --manifest catalog.yaml \
+npx @runveric/cli@0.4.0 catalog publish-action --manifest catalog.yaml \
     --to ghcr.io/<org>/action-azure-vm-stop
 
 # an ENGINE action: its manifest and the image its workflow pushed, by digest, to the same package
-npx @runveric/cli@0.3.0 catalog publish-action --manifest catalog.yaml \
+npx @runveric/cli@0.4.0 catalog publish-action --manifest catalog.yaml \
     --to ghcr.io/<org>/action-azure-publicip-delete-unattached \
     --image ghcr.io/<org>/action-azure-publicip-delete-unattached@sha256:<digest>
 
 # a release naming each action artifact by digest — stdout: <repository>@<digest>
-npx @runveric/cli@0.3.0 catalog publish-release --from release.yaml --to ghcr.io/<org>/catalog
+npx @runveric/cli@0.4.0 catalog publish-release --from release.yaml --to ghcr.io/<org>/catalog
 
 # what the release workflow may sign: each engine action's image, judged by the server's rule
 # — stdout: one <repository>@<digest> per image that passed
-npx @runveric/cli@0.3.0 catalog verify-image --from release.yaml
-npx @runveric/cli@0.3.0 catalog verify-image <repository>@<digest> --key <action key> --commit <sha>
+npx @runveric/cli@0.4.0 catalog verify-image --from release.yaml
+npx @runveric/cli@0.4.0 catalog verify-image <repository>@<digest> --key <action key> --commit <sha>
 ```
 
 An action's package must be named after its key (`azure.vm.stop` → `action-azure-vm-stop`); the

package/dist/runveric.mjs

@@ -4307,7 +4307,7 @@ var require_action_image = __commonJS({
     var action_signing_1 = require_action_signing();
     var oci_media_types_1 = require_oci_media_types();
     exports.ACTION_RUNTIME_REPOSITORY = "ghcr.io/runveric/action-runtime";
-    exports.ACTION_RUNTIME_IMAGE = `${exports.ACTION_RUNTIME_REPOSITORY}@sha256:0774c0768c6d1b11e7224ce5bca925549e369fed75eeb412531c1dce10bc8a8a`;
+    exports.ACTION_RUNTIME_IMAGE = `${exports.ACTION_RUNTIME_REPOSITORY}@sha256:55126390dc54a79668e8475757f6de6dabc8c052242079d48d888eca4fdd5963`;
     exports.MAX_IMAGE_MANIFEST_BYTES = 64 * 1024;
     var isRecord = /* @__PURE__ */ __name((value) => typeof value === "object" && value !== null && !Array.isArray(value), "isRecord");
     function imageConfigDescriptor2(manifest) {
@@ -8692,7 +8692,7 @@ var require_dist2 = __commonJS({
 });
 
 // package.json
-var version = "0.3.0";
+var version = "0.4.0";
 
 // src/report.ts
 var useColour = process.stdout.isTTY === true && !process.env.NO_COLOR;