ci: pin a guidata development ref for unreleased dataset items

Sigima develop imports guidata's unreleased HistogramRangeItem.

Assisted-by: Claude Opus 5.5

Author: PierreRaybaut

.env.template

@@ -27,3 +27,5 @@ PYTHONPATH=.;..\Sigima;..\guidata
 # Vite at it with an absolute /@fs/ URL (use forward slashes). This local value
 # overrides both fields in sigima-dependency.json for browser runtimes only:
 # VITE_SIGIMA_INSTALL_SPEC=/@fs/C:/path/to/Sigima/dist/sigima-X.Y.Z-py3-none-any.whl
+# The same override exists for guidata (guidata-dependency.json):
+# VITE_GUIDATA_INSTALL_SPEC=/@fs/C:/path/to/guidata/dist/guidata-X.Y.Z-py3-none-any.whl

.github/workflows/perf.yml

@@ -59,7 +59,7 @@ jobs:
       - name: Install npm dependencies
         run: npm ci
 
-      - name: Prepare configured Sigima dependency
+      - name: Prepare configured Sigima and guidata dependencies
         run: >-
           python scripts/sigima_dependency.py prepare-pyodide
           --wheel-dir .wheels

.github/workflows/release.yml

@@ -19,7 +19,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Require a published Sigima dependency
+      - name: Require published Sigima and guidata dependencies
         run: node scripts/check-sigima-release.mjs
 
       - name: Check tag matches package.json and SDK versions
@@ -61,6 +61,7 @@ jobs:
           cache-dependency-path: |
             requirements-dev.txt
             sigima-dependency.json
+            guidata-dependency.json
 
       - name: Install Python dependencies
         run: |
@@ -91,6 +92,7 @@ jobs:
       - name: Run Playwright tests
         env:
           VITE_SIGIMA_INSTALL_SPEC: ""
+          VITE_GUIDATA_INSTALL_SPEC: ""
         run: npm run test:e2e
 
       - name: Upload Playwright report

.github/workflows/tests.yml

@@ -30,6 +30,7 @@ jobs:
           cache-dependency-path: |
             requirements-dev.txt
             sigima-dependency.json
+            guidata-dependency.json
 
       - name: Install Python dependencies
         run: |
@@ -103,7 +104,7 @@ jobs:
       - name: Install npm dependencies
         run: npm ci
 
-      - name: Prepare configured Sigima dependency
+      - name: Prepare configured Sigima and guidata dependencies
         run: >-
           python scripts/sigima_dependency.py prepare-pyodide
           --wheel-dir .wheels

CONTRIBUTING.md

@@ -109,6 +109,8 @@ and Pyodide without `PYTHONPATH` or `VITE_SIGIMA_INSTALL_SPEC`, then set
 `developmentRef` to `null`. See [doc/releasing.md](doc/releasing.md) for the
 release checklist.
 
+Use [guidata-dependency.json](guidata-dependency.json) in the same way when Sigima or DataLab-Web needs a merged but unpublished guidata change. Its `publishedRequirement` may be an exact pin or a lower bound (`guidata>=X.Y.Z`); a non-null `developmentRef` blocks releases until a guidata version providing the change is published and required.
+
 ## Branching model
 
 DataLab-Web follows the same two-branch model as the sibling repositories (DataLab, Sigima): day-to-day work lands on **`develop`**, and **`main`** is the release branch — `develop` is merged into `main` only when cutting a real release. CI ([tests.yml](.github/workflows/tests.yml)) runs the cheap regression suite on both branches and on pull requests targeting either. The multi-minute performance benchmarks are **not** part of that run; they are opt-in and driven by a separate on-demand workflow (see the **Performance benchmarks** section of [doc/testing-strategy.md](doc/testing-strategy.md)).

README.md

@@ -110,6 +110,8 @@ the target Sigima version is published and qualified without a local override,
 set the field to `null`; the generalized snapshot mechanism remains available
 for the next coordinated change.
 
+[`guidata-dependency.json`](guidata-dependency.json) applies the same mechanism to guidata when Sigima or DataLab-Web needs unreleased guidata changes. Its `publishedRequirement` may be an exact pin or a lower bound (`guidata>=X.Y.Z`). The install command above and the CI wheel preparation handle both manifests, and `VITE_GUIDATA_INSTALL_SPEC` is the matching local browser override.
+
 ## Documentation
 
 | Topic                                              | Guide                                              |

doc/releasing.md

@@ -35,7 +35,9 @@ the release browser tests never build or export a development wheel.
 `release:pack` uses `build:release`, whose release mode ignores even an
 accidental `VITE_SIGIMA_INSTALL_SPEC` from the developer's ignored `.env`.
 
-> **What `git push --tags` triggers** — the [`Release tarballs`](../.github/workflows/release.yml) workflow runs, in order: Sigima release guard and version coherence check (tag ↔ both `package.json` files) → `pytest tests/python` (3.11 + 3.12) and Playwright E2E against the published Sigima pin (in parallel) → lint + Vitest + build + pack the two `.tgz` → publish a GitHub Release with the tarballs and auto-generated notes → deploy `dist/` to GitHub Pages. Any failing gate aborts the release **and** the deploy.
+The guard applies the same rule to [`guidata-dependency.json`](../guidata-dependency.json): a non-null guidata `developmentRef` blocks the release until a guidata version providing the required changes is published and `publishedRequirement` requires it (for example `guidata>=X.Y.Z`). Release builds also ignore `VITE_GUIDATA_INSTALL_SPEC`.
+
+> **What `git push --tags` triggers** — the [`Release tarballs`](../.github/workflows/release.yml) workflow runs, in order: Sigima and guidata release guard and version coherence check (tag ↔ both `package.json` files) → `pytest tests/python` (3.11 + 3.12) and Playwright E2E against the published Sigima pin (in parallel) → lint + Vitest + build + pack the two `.tgz` → publish a GitHub Release with the tarballs and auto-generated notes → deploy `dist/` to GitHub Pages. Any failing gate aborts the release **and** the deploy.
 
 ## Distribution: app bundle + SDK tarballs
 

doc/testing-strategy.md

@@ -58,6 +58,8 @@ the sibling checkout, and its `PYTHONPATH` may prioritize sibling Python
 sources, but neither alters the versioned CI selection. Remove those local
 overrides when qualifying the exact manifest-selected dependency.
 
+The resolver applies the same rules to [guidata-dependency.json](../guidata-dependency.json), installing its `developmentRef` in CPython and exporting the matching browser wheel through `VITE_GUIDATA_INSTALL_SPEC`.
+
 When qualifying a published Sigima version for release, use a clean environment
 without `..\Sigima` in `PYTHONPATH` and without `VITE_SIGIMA_INSTALL_SPEC`.
 This ensures both pytest and Playwright exercise the exact PyPI version rather

guidata-dependency.json

@@ -0,0 +1,4 @@
+{
+  "publishedRequirement": "guidata>=3.15.0",
+  "developmentRef": "7203944df510bac341df643a97ff17850ff3fe92"
+}

requirements-dev.txt

@@ -19,8 +19,9 @@ pylint>=3.0
 # ``pre-commit install`` once after cloning. See CONTRIBUTING.md.
 pre-commit>=3.7
 
-# Sigima (= computation engine) is selected through sigima-dependency.json.
-# Use scripts/sigima_dependency.py to install the configured revision together
+# Sigima (= computation engine) and guidata are selected through
+# sigima-dependency.json and guidata-dependency.json. Use
+# scripts/sigima_dependency.py to install the configured revisions together
 # with these mandatory dependencies.
 guidata>=3.15.0
 numpy>=1.22