@mutmutco/pi-plugin 4.1.7 → 4.1.9

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/pi-plugin",
3
- "version": "4.1.7",
3
+ "version": "4.1.9",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
@@ -13,7 +13,7 @@ name: gate
13
13
  # GATE_CMD — the check command ({{GATE_CMD}})
14
14
  # GATE_INSTALL_CMD — the dependency-install command ({{GATE_INSTALL_CMD}})
15
15
  # GATE_WORKDIR — app working directory when not the repo root ({{GATE_WORKDIR}})
16
- # GATE_CACHE_DEP_PATH— npm lockfile path for the setup-node cache ({{GATE_CACHE_DEP_PATH}})
16
+ # GATE_CACHE_DEP_PATH— npm lockfile path for runner-checkout heal ({{GATE_CACHE_DEP_PATH}})
17
17
  # GATE_PY_VERSION — Python version for setup-python ({{GATE_PY_VERSION}})
18
18
  # GATE_MAX_SECONDS — run-with-budget wall-clock ceiling in seconds ({{GATE_MAX_SECONDS}}); 300 default,
19
19
  # tighten per repo (org project set --var gate={"maxSeconds":N}) once measured (#3178)
@@ -65,9 +65,9 @@ jobs:
65
65
  # #5427: per-job npm cache under $RUNNER_TEMP — never the shared ~/.npm. Twelve mmi-live lanes
66
66
  # share the gha-runner home; npm hardlinks from that cache into node_modules, so one job's
67
67
  # `npm ci` can make another job's vitest/dist/workers/forks.js vanish mid-suite (Cannot find
68
- # module). Job-local cache ⇒ no cross-job hardlinks. Must land BEFORE setup-node (`cache: npm`
69
- # follows `npm config get cache`). Job-level `env:` cannot use the `runner` context — write
70
- # via GITHUB_ENV from the shell `$RUNNER_TEMP` instead.
68
+ # module). Job-local cache ⇒ no cross-job hardlinks. Must land BEFORE setup-node (which reads
69
+ # `npm config get cache` for any explicit cache restore). Job-level `env:` cannot use the
70
+ # `runner` context — write via GITHUB_ENV from the shell `$RUNNER_TEMP` instead.
71
71
  - name: Isolate npm cache (per-job)
72
72
  shell: bash
73
73
  run: echo "NPM_CONFIG_CACHE=$RUNNER_TEMP/npm-cache" >> "$GITHUB_ENV"
@@ -93,12 +93,14 @@ jobs:
93
93
  done < "$offenders"
94
94
  exit 1
95
95
  fi
96
+ # #5660: self-hosted gates opt OUT of setup-node automatic npm cache restore unless a bounded
97
+ # cache policy is declared on runner-node-toolchain (cache + cache-restore-max-mb). Per-job
98
+ # NPM_CONFIG_CACHE above is the org default; unbounded Actions cache blobs can exhaust mmi-live
99
+ # disks mid-extract before the real check runs (Jerv-Hub SQLCipher gate, ~4.3GB restore).
96
100
  - if: ${{ '{{GATE_RUNTIME}}' == 'node' }}
97
101
  uses: mutmutco/MMI-Hub/.github/actions/runner-node-toolchain@{{GATE_RUNNER_SHA}}
98
102
  with:
99
103
  node-version: 24
100
- cache: npm
101
- cache-dependency-path: {{GATE_CACHE_DEP_PATH}}
102
104
  - if: ${{ '{{GATE_RUNTIME}}' == 'python' }}
103
105
  uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
104
106
  with: { python-version: '{{GATE_PY_VERSION}}' }