Skip to content

v0.10.2 — one canonical install URL, recorded everywhere

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Jul 08:10
v0.10.2
55a66b9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The domain is live, so the repo now says so — in one voice, everywhere.

The real bug: the installer's own URL was a 404

install.sh's header told readers to fetch raw.githubusercontent.com/.../main/install.sh. There is no root install.sh — it lives at main/site/install.sh. So anyone who opened the script before piping it to their shell (the security-conscious move) hit a dead URL. The header now names the canonical https://topk1.com/forge/install.sh, with the raw-GitHub path documented as a working mirror.

One story, not two

The installer's Next steps led with forge setup — the path v0.10.1 deliberately demoted. It now mirrors the first-run welcome exactly:

Next
  forge                  see what this machine can run
  forge models use phi-2 a quick starter — pulled + ready in ~2 min
  forge run "<a task>"   then put it to work

  (or  forge setup  to pick a model ladder yourself)

The README's Set up section gets the same treatment — it leads with the real first-run output instead of forge setup.

Install

curl -fsSL https://topk1.com/forge/install.sh | sh

README.md is the PyPI long_description, so the new instructions ship to the PyPI page too; Homepage now points at https://topk1.com/forge/.

Verified against the live domain: /forge, /forge/, and /forge/install.sh all 200; install.sh serves application/x-sh (not the rewritten HTML); the full one-liner runs clean end-to-end. 716 tests pass.

Full changelog: v0.10.1...v0.10.2

Assets 2
Loading