@releaseway/npm-actions-fixture 0.0.12-native.0 → 0.0.13-native.0

package/.releaseway/native.json

@@ -1,7 +1,7 @@
 {
   "repository": "releaseway/npm-actions-fixture",
-  "version": "0.0.12-native.0",
-  "tag": "native-v0.0.12-native.0",
+  "version": "0.0.13-native.0",
+  "tag": "native-v0.0.13-native.0",
   "targets": {
     "linux-x64-gnu": {
       "asset": "npm-actions-native-fixture_linux_x64.tar.gz",

package/README.md

@@ -50,7 +50,7 @@ The defaults use `0.0.5-fixture.0` with `already-published` to exercise version
 - Workflow filename: `direct.yml`
 - Allowed action: enable `Allow npm publish`
 
-The inputs default to `fixture-version=0.0.11-native.0` and `expected-state=already-published`. For this scenario the workflow skips Release creation and source-commit comparison, invokes npm-actions to verify the version is already public, then installs and executes the published CLI. It may run from a later source commit than the original Release. It does not republish the historical package or test a newly generated runtime.
+The inputs default to `fixture-version=0.0.12-native.0` and `expected-state=already-published`. For this scenario the workflow skips Release creation and source-commit comparison, invokes npm-actions to verify the version is already public, then installs and executes the published CLI. It may run from a later source commit than the original Release. It does not republish the historical package or test a newly generated runtime.
 
 To publish a new native fixture, select a fresh `0.0.N-native.M` version and `expected-state=published`. Repository release immutability must be enabled. Product steps build the deterministic Linux x64 asset. `releaseway/actions/prepare` binds the same-commit `native-v<version>` tag and `releaseway/actions` publishes or resumes its immutable prerelease with verified asset digests, before npm-actions publishes to `next`. The action prepares only an unpublished candidate and confirms its exact SHA-512 in the live registry.
 
@@ -60,6 +60,19 @@ The fixture asset is `native/fixture.sh`, packed into `npm-actions-native-fixtur
 
 Cross-platform installed-wrapper behavior is covered in the npm-actions repository by the runtime/install matrix on Linux x64/arm64, macOS x64/arm64, and Windows x64/arm64. This real-registry native fixture targets Linux x64 to exercise GitHub Release provenance, npm OIDC publication, installation, first-run download, and cache reuse.
 
+## Native command aliases
+
+For an alias-capable candidate, dispatch `direct.yml` with its full `action-ref`,
+a fresh native version, `expected-state=published`, and `command-aliases=true`.
+Preparation maps both `npm-actions-native-fixture` and `rw-npm-fixture` to the same
+generated launcher. Every Node 22/24/26 consumer executes both names, then repeats
+them against one read-only cache. Successful evidence records the alias names.
+
+The alias option defaults to `false` during candidate adoption, so historical
+packages and the existing stable action remain usable. Set it to `false` for an
+older published fixture without aliases. Staged non-native fixtures do not use this
+option. A historical lookup still cannot certify new candidate packaging.
+
 ## Candidate acceptance
 
 Supply the candidate's full 40-character `action-ref`, a fresh version and fresh

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@releaseway/npm-actions-fixture",
-  "version": "0.0.12-native.0",
+  "version": "0.0.13-native.0",
   "description": "Integration fixture for releaseway/npm-actions. Not for production use.",
   "type": "module",
   "exports": "./index.js",
@@ -15,6 +15,7 @@
     "access": "public"
   },
   "bin": {
-    "npm-actions-native-fixture": "bin/npm-actions-native-fixture"
+    "npm-actions-native-fixture": "bin/npm-actions-native-fixture",
+    "rw-npm-fixture": "bin/npm-actions-native-fixture"
   }
 }