One-line install: curl -fsSL …/releases/latest/download/install.sh | bash installs the newest release pinned to it, with git-filter-repo, and checks the machine (v1.0.1) #564

Goal: installing openRepoShape is one command on any machine, and the installed command stays on the release it installed.

Decision. Brett Heap, 2026-10-14:

• At 22:50:40Z: "we need it to be more simple to install. i will wait for the tag, but we need a very simple install. … now and after, we need a simple install process".
• At 22:54:54Z, asked when it ships: "v1.0.1 soon (Recommended)". So v1.0.1 is v1.0.0 plus only this change. It is released from a release/v1.0 branch cut at the v1.0.0 tag, and then carried forward to main as a v1.1.0 PR. Publishing to PyPI stays Publish openRepoShape to TestPyPI and PyPI as openreposhape, so one pipx install puts the tools and git-filter-repo on any machine (design first) #563 (v1.1.0).

What is wrong today

• Installing takes several steps, and the result is not pinned.
  • The installed openRepoShape reads OPENREPOSHAPE_REF at every run and defaults to main (openRepoShape:31). Its scaffold and doctor runs fetch the standard at that ref (openRepoShape:381-389 and 672-674).
  • From v1.0.0 on, main carries v1.1.0 work, so a plain install drifts off the release within hours.
  • Staying on a release today means exporting OPENREPOSHAPE_REF in a shell profile.
• git-filter-repo is a separate install on every machine. adopt-project.py refuses filter-repo-missing without it.

The change

1. install.sh at the repository root, attached to every release, so this one line always installs the newest release:
   curl -fsSL https://github.com/opensoft/openRepoShape/releases/latest/download/install.sh | bash
   It does four things:

   • It finds the newest release from the releases/latest redirect on github.com, with no gh needed, or takes the one named: … | bash -s -- v1.0.1.
   • It fetches that release's openRepoShape and runs its --install, pinned to the release.
   • It handles git-filter-repo: if it is already on PATH, it says so. If not and pipx is on PATH, it installs git-filter-repo==2.47.0 with pipx and says so. Otherwise it prints the one command for this machine.
   • It ends with openRepoShape --preflight.

   Running the same line again upgrades to the newest release.

2. The launcher's --install records the ref it installed at, and the installed command uses it. It must reach every place that today honours only an exported OPENREPOSHAPE_REF: the doctor's clone (openRepoShape:381-389) and setup.sh's --shape-ref (openRepoShape:674). OPENREPOSHAPE_REF still overrides it for one run, and --version prints it.

3. README's install section leads with the one line. The gh api … | bash -s -- --install form stays as the manual way.

Constraints

• It runs on macOS's bash 3.2, Linux, and Git Bash on Windows.
• It needs no gh auth login, because the repository is public.
• It installs only git-filter-repo, says every step, and never uses sudo.
• Printed commands stay POSIX-only (Printed commands are POSIX-only: quote the bare paste lines in bump-leg.py and update-shape.py, and say in the docs that pasted commands are for a POSIX shell #532).
• The tests run on Linux, macOS and Windows.

Release steps

1. A PR into release/v1.0, an independent review, and the three-OS run on its head.
2. The tag v1.0.1 and a GitHub Release with install.sh attached.
3. The same change carried into main.
4. The workBenches image re-vendored at v1.0.1 (ruling 33).

Filed by lane openRepoShape-3 on Brett Heap's word above.