[IvanHCenalmor]

Fixes #41, fixes #42, fixes #43. Design note: .tools/docs/migration_0_1_24.md.

Problems (all three found with StarDist2D 1.0.0)

• Download page links are broken when the release tag starts with "v" #41: a release tagged v1.0.0 wrote download links to /releases/download/1.0.0/...; the release folder is v1.0.0, so every download button returned 404.
• Release builds Intel Mac installers even when the app cannot run there #42: every release built the four installers, also for Intel Macs, where TensorFlow 2.17+ (StarDist2D) cannot install. The release page and the download page offered them.
• Installed app opens notebooks in the wrong Python when the user has a personal "python3" kernel #43: Jupyter prefers a user-level python3 kernelspec (ipykernel install --user) over the app's own, so the notebook ran in another Python: No module named '<app>'.

Changes

• release_constructor.yml: both "Determine release version" steps also export the tag as typed (RELEASE_TAG). A new platforms job runs release_platforms.py; the build job takes its matrix from it (fromJSON(needs.platforms.outputs.matrix)).

• .tools/python/release_platforms.py (new):

  • reads distribution.platforms of labconstrictor-app.yaml and writes the matrix;
  • without the key or the file, all four builds, in the old order, so nothing changes for existing apps;
  • fails with the reason on invalid YAML, a non-list, or a list with none of the four (windows-arm64 / linux-arm64 have no build).

• bump_version.py:

  • the download links point to the tag (--tag, default $RELEASE_TAG, else the version), and the installer names keep the bare version;
  • a tag that is neither X.Y.Z nor vX.Y.Z is refused;
  • a system that is not built gets a note instead of its button.

  The tag comes from the environment, so the workflow and this script do not depend on each other: an unchanged (customised) bump_version.py keeps working, with the old links.

• launch_jupyter.py: run_jupyter() sets JUPYTER_PREFER_ENV_PATH=1 before importing JupyterLab. It is set, not defaulted, so a user's 0 cannot bring the bug back.

• Migration v0_1_23_to_v0_1_24.py:

  • surgical and idempotent: it never raises for a customised file, keeps line endings and deletes nothing;
  • it creates release_platforms.py and changes known exact blocks only;
  • the build matrix is switched only when it is exactly the template's four builds, and a matrix trimmed by hand (Playground) is left alone with a SKIPPED line.

• Docs: migration_0_1_24.md, the release guide (a v tag works), the app manifest guide (platforms decides the builds), and both troubleshooting pages.

• Tests:

  • tests/test_template_sync_0_1_24.py (34 tests);
  • tests/_v0_1_24.py undoes the 0.1.24 blocks, so the frozen resources of the 0.1.13 / 0.1.18 / 0.1.20 migrations are still compared with the live files.

Verified

• With CI's versions (ruff 0.15.20, mypy 1.20.2), ruff and mypy pass.
• The new tests pass. The full suite on Windows has the same failures as main (bash and path-separator tests that pass on Linux), and none are new.
• Copies of NucleiSky, Playground, Guess the Condition, LabConstrictor_Demo, LabChronicle, CellTracksColab, StarDist2D, CellPatcher and VLab4Mic were synced from their own template version to 0.1.24, then bump_version.py was run with a vX.Y.Z tag:
  • every link points to the v tag;
  • StarDist2D builds 3 systems and its page shows the Intel Mac notes, while the others build all 4;
  • CellPatcher's customised bump_version.py is updated and keeps its pre-release check;
  • the Playground's hand-trimmed matrix is reported SKIPPED and left as it is.

Not verified

• No real release ran with the new workflow: the platforms job and the fromJSON matrix are checked by reading them and parsing the YAML in tests.
• That jupyter_core then lists the app's kernel first was checked by hand on the StarDist2D Linux install (Installed app opens notebooks in the wrong Python when the user has a personal "python3" kernel #43), not by these tests. The tests check that the launcher sets the variable before JupyterLab starts.

🤖 Generated with Claude Code