F9.5 — Prove external installability
| State | Closed |
| Parent | E9 |
| Iteration | Release 1 |
| Closed Date | 2026-09-28 |
| Predecessors | F9.6: this runs after the tags exist |
Stories: 1 Closed
| Story | State | Depends on |
|---|---|---|
| S9.5.1 — Verify remote tags and clean installs | Closed (2026-09-28) | — |
A tag is only a release if a consumer outside this repository can install it. CI
cannot show that: every job runs uv sync --all-packages --all-extras --locked,
which resolves internal dependencies from the workspace, not from their pins.
This check runs in CI after tagging, as its own job.
S9.5.1 — Verify remote tags and clean installs
State: Closed (2026-09-28)
Acceptance: a CI job that runs on a push to main after the package jobs
checks, for each package tagged in that run, that the tag exists on the remote
and that a fresh virtual environment installs the package from its Git direct
URL and imports it, with no workspace source override. For release-1, the
release page records the tags and the job's result.
The external-install job in .github/workflows/main.yml does this, using the
same tag-discovery mechanism as the docs job
(git tag --points-at "$GITHUB_SHA", since tags pushed with GITHUB_TOKEN
start no workflow of their own). Verified via workflow_dispatch runs against
release-1's seven tags before merge.
set -euo pipefail
# PACKAGES holds release-1's "<package> <tag>" pairs, one per line.
tmp=$(mktemp -d)
while read -r pkg tag; do
git ls-remote --exit-code --tags origin "refs/tags/$tag" >/dev/null
uv venv -q "$tmp/$pkg"
VIRTUAL_ENV="$tmp/$pkg" uv pip install -q \
"$pkg @ git+https://github.com/rn-forge/pykit@$tag#subdirectory=packages/$pkg"
"$tmp/$pkg/bin/python" -c "import rn_forge.${pkg#rn-forge-}"
done <<<"$PACKAGES"