@monoai/nscloud-nx-cache-action 0.1.2 → 0.1.4

package/README.md

@@ -78,7 +78,7 @@ The first npm publication requires the [publisher setup](docs/operations.md#npm-
 Once a version is published, install it in your workspace:
 
 ```sh
-pnpm add --save-dev @monoai/nscloud-nx-cache-action@0.1.2
+pnpm add --save-dev @monoai/nscloud-nx-cache-action@0.1.4
 NX_ARCHIVE_DIRECTORY="$HOME/.cache/nx-namespace" \
   pnpm exec nscloud-nx-cache-action pnpm exec nx run-many -t build
 ```

package/docs/operations.md

@@ -148,6 +148,8 @@ also packs and publishes that version to npm after the audit, tests, reproducibl
 build and release-asset checks pass. The manual draft flow prepares the package
 without publishing it. A retry verifies the existing npm tarball integrity and
 skips publication only when the bytes match; lookup failures and conflicts fail.
+After publishing, it waits up to five minutes for the new version to become readable
+before verifying its integrity.
 
 Configure the package's npm trusted publisher for GitHub owner `monoai-labs`,
 repository `nscloud-nx-cache-action`, workflow `release.yml`, with direct

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@monoai/nscloud-nx-cache-action",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "CLI tools for Nx HTTP caching across local development, Namespace runners and hosted builds, with local archives, shared Artifact Storage and short-lived build credentials.",
   "license": "MIT",
   "type": "module",