@releaseway/npm-actions-fixture 0.0.9-native.0 → 0.0.10-native.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "repository": "releaseway/npm-actions-fixture",
3
- "version": "0.0.9-native.0",
4
- "tag": "native-v0.0.9-native.0",
3
+ "version": "0.0.10-native.0",
4
+ "tag": "native-v0.0.10-native.0",
5
5
  "targets": {
6
6
  "linux-x64-gnu": {
7
7
  "asset": "npm-actions-native-fixture_linux_x64.tar.gz",
package/README.md CHANGED
@@ -4,7 +4,7 @@ Permanent integration fixture for releaseway/npm-actions.
4
4
 
5
5
  This package exercises real npm registry and GitHub Release behavior: registry-first version selection, Trusted Publishing OIDC, staged submissions, and native installation and execution. It is not intended for application dependencies or production use.
6
6
 
7
- The committed package remains an ordinary non-native fixture. Workflows rewrite checkout-local metadata without committing it. Both accept a full `action-ref` SHA, default to the published `releaseway/npm-actions v0.4.0` commit, verify the checked-out SHA and run `./npm-action`.
7
+ The committed package remains an ordinary non-native fixture. Fixture-specific native bin metadata and the legacy package-json version scenario are prepared locally; tag-derived scenarios preserve the source version. Publication channels are declared as stable `latest` and prerelease `next` in Releaseway policy, without rewriting `publishConfig.tag`. Both workflows accept a full `action-ref` SHA, verify the checked-out SHA and run `./npm-action`.
8
8
 
9
9
  ## Result contract
10
10
 
@@ -40,9 +40,9 @@ The defaults use `0.0.5-fixture.0` with `already-published` to exercise version
40
40
  - Workflow filename: `direct.yml`
41
41
  - Allowed action: enable `Allow npm publish`
42
42
 
43
- The inputs default to `fixture-version=0.0.6-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.
43
+ The inputs default to `fixture-version=0.0.9-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.
44
44
 
45
- 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. The workflow creates or reuses a same-commit `native-v<version>` Release, uploads the Linux x64 asset, and waits for immutability and a SHA-256 asset digest before invoking npm-actions. The action prepares only an unpublished candidate and confirms its exact SHA-512 in the live registry.
45
+ 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.
46
46
 
47
47
  Both native scenarios install the exact version with `--ignore-scripts` on Node 22, 24 and 26, each with a separate empty native cache. They execute the CLI, make its populated cache read-only, execute again and compare file snapshots. Fresh `published` runs also compare installed package-lock SHA-512 with the action report's frozen plan. Historical lookup remains a separate result.
48
48
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@releaseway/npm-actions-fixture",
3
- "version": "0.0.9-native.0",
3
+ "version": "0.0.10-native.0",
4
4
  "description": "Integration fixture for releaseway/npm-actions. Not for production use.",
5
5
  "type": "module",
6
6
  "exports": "./index.js",
@@ -12,8 +12,7 @@
12
12
  "url": "git+https://github.com/releaseway/npm-actions-fixture.git"
13
13
  },
14
14
  "publishConfig": {
15
- "access": "public",
16
- "tag": "native"
15
+ "access": "public"
17
16
  },
18
17
  "bin": {
19
18
  "npm-actions-native-fixture": "bin/npm-actions-native-fixture"