docs: install-heph defaults to the v1.0.0 release tag (v1 is out)
All checks were successful
Build / validate (pull_request) Successful in 5m5s

Replace the pre-release 'install from feature/v1-prototype' instructions with
`--tag v1.0.0` as the default, and document `--branch main` as the track-
unreleased-work alternative.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-06-04 09:47:23 -07:00
commit 521e5d62df

View file

@ -1,6 +1,6 @@
---
title: Install heph (and isolate dev)
modified: 2026-06-02
modified: 2026-06-04
tags:
- how-to
---
@ -14,18 +14,19 @@ linux/arm64, linux/amd64).
## 1. Install the binaries from the forge
Build and install `heph` + `hephd` to `~/.cargo/bin` (on `PATH`) from a forge
ref. Until v1 is tagged, install from the branch:
Build and install `heph` + `hephd` to `~/.cargo/bin` (on `PATH`) from the latest
release tag:
```bash
cargo install --locked \
--git ssh://forgejo@forge.ops.eblu.me:2222/eblume/hephaestus.git \
--branch feature/v1-prototype \
--tag v1.0.0 \
heph hephd
```
Re-run with `--tag vX.Y.Z` once a release is cut. This needs forge SSH access
(an unlocked 1Password / ssh-agent key).
Bump `--tag` to upgrade to a newer release; to track unreleased work instead,
swap `--tag vX.Y.Z` for `--branch main`. This needs forge SSH access (an
unlocked 1Password / ssh-agent key).
`heph --version` / `hephd --version` report `X.Y.Z (<git-sha>)` for a tagged
install and `0.0.0 (<git-sha>)` for a branch/dev install — the release version