Unify installers on tagged releases

This commit is contained in:
Advait Paliwal
2026-03-26 18:17:48 -07:00
parent 4c62e78ca5
commit 404c8b5469
12 changed files with 112 additions and 231 deletions

View File

@@ -19,8 +19,6 @@ The installer detects your OS and architecture automatically. On macOS it suppor
If you previously installed Feynman via `npm`, `pnpm`, or `bun` and still see local Node.js errors after a curl install, your shell is probably still resolving the older global binary first. Run `which -a feynman`, then `hash -r`, or launch the standalone shim directly with `~/.local/bin/feynman`.
By default, the one-line installer tracks the rolling `edge` channel from `main`.
On **Windows**, open PowerShell as Administrator and run:
```powershell
@@ -59,22 +57,20 @@ Or install them repo-locally:
These installers download only the `skills/` tree from the Feynman repository. They do not install the Feynman terminal, bundled Node runtime, auth storage, or Pi packages.
## Stable or pinned releases
## Pinned releases
If you want the latest tagged release instead of the rolling `edge` channel:
The one-line installer already targets the latest tagged release. To pin an exact version, pass it explicitly:
```bash
curl -fsSL https://feynman.is/install | bash -s -- stable
curl -fsSL https://feynman.is/install | bash -s -- 0.2.14
```
On Windows:
```powershell
& ([scriptblock]::Create((irm https://feynman.is/install.ps1))) -Version stable
& ([scriptblock]::Create((irm https://feynman.is/install.ps1))) -Version 0.2.14
```
You can also pin an exact version by replacing `stable` with a version such as `0.2.14`.
## pnpm
If you already have Node.js `20.19.0` or newer installed, you can install Feynman globally via `pnpm`: