@sjawhar/pi-legion 19.29.5 → 19.29.6

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/dist/legion.js CHANGED
@@ -29763,7 +29763,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
29763
29763
  // package.json
29764
29764
  var package_default = {
29765
29765
  name: "@sjawhar/pi-legion",
29766
- version: "19.29.5",
29766
+ version: "19.29.6",
29767
29767
  license: "Apache-2.0",
29768
29768
  type: "module",
29769
29769
  omp: {
@@ -146,7 +146,7 @@ the three `-alone` ones among them - runs on a pull request labelled `full-ci`,
146
146
  queue and nightly, and the `alone` job that holds the wall-clock rows is gated on it
147
147
  (`if: inputs.lane == 'full'` under `alone:` in `.github/workflows/dispatch-browser.yaml`), so no
148
148
  unlabelled pull request runs a wall-clock row at all. One spec needs
149
- the same stack as all of them: a Postgres with pgvector. On a digest
149
+ the same stack as all the specs: a Postgres with pgvector. On a digest
150
150
  carrying `legion-testpg`, use the pod's own server
151
151
  (`skill://legion-worker/references/tools.md#the-database-your-tests-use`) and
152
152
  unpack nothing. On a digest without it, the way
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "19.29.5",
3
+ "version": "19.29.6",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {