Artifact 83ce57d9b7b66960163af84c0d043a41232204383524e2511d1d082eb3f5f7d0:
- File CHANGELOG.md — part of check-in [9e0b1422e9] at 2026-10-03 15:53:08 on branch release-0.2.0 — Changelog for 0.2.0, the first release the forge cuts itself (user: zeitgeist, size: 4331) [annotate] [blame] [check-ins using] [more...]
Changelog
What changed on the forge, newest first. Each entry names the build it shipped in; the footer of every page names the build you are on.
0.2.0 (2026-10-03)
The first release cut by the forge itself: tagged, built by its own CI and published as a release you can download and check.
Releases and unversioned files
- Releases. A repository's Releases tab lists what it has published,
each release on its own page with its notes, files, sizes and
checksums; a
version-X.Y.Ztag builds and publishes one through CI. - Unversioned files. fossil's
uvworks against quarry: publish withfossil uv addandsync -u, orzit uv push; the UV tab lists them and serves downloads straight from the repository's own storage. - Mirrors bring their upstream's unversioned files along.
- Archive downloads (tar.gz and zip) are built once and kept, then served directly from storage instead of rebuilt on every click.
CI
- Workflows you write.
ci/*.ymlfiles in GitHub Actions' shape run when theiron:says, including on a schedule and on a tag. - Landings test the merge, as a pull request does, and a verdict tested against an older trunk is shown as stale and must be re-run before it can land.
- Environments and secrets. Secrets only reviewed code can reach, set by name and never shown again; each environment says, in plain words, what a job's credential there may do and who may start one.
- Run tokens. Each job gets its own short-lived credential, scoped to its run and repository and to what its workflow declares; no shared release account.
- Runners you download and run yourself, scoped to your repository, with every attempt's log kept and runs that say what happened.
Accounts and access
- Tokens. Named, expiring push credentials you can list and revoke one by one from your account page.
- Invites and resets. An old invite link can no longer change a claimed account's password; site admins send reset links and never see or set a password; a deleted account stays deleted.
- Private repositories answer exactly like missing ones to anyone who cannot read them, and site administrators stop at a repository's door.
- Anonymous sync pulls as stock fossil does, and an anonymous write is refused however it is sent.
Landings and tickets
- Landings have numbers, written
!Nwherever one is named;Closes #Ncloses the ticket when a landing lands, and accept leads the decision box. - Tickets show their number and state wherever they are named, open a preview card on hover, and are quicker to file, with templates by type.
Everywhere else
- Email looks like quarry: a card with the repository or team it came from, the rendered message, and quarry's logo.
- Markdown reads better: framed tables, alerts, a heading scale, and pikchr diagrams with their source, copy and an editor link.
- The timeline draws merged branches as merged on every page, and the home page leads with your repositories and teams.
- Steadier underneath: CI results are never lost, rebuilds queue, the forge stops in order, and an outside probe emails when it is down.
0.1.0-beta.1 — 2026-09-03
The first build the private beta is invited to.
- Invites. Admins invite people by name and email from Fleet → People; the invite arrives by email and the link sets a password and signs you in. Sign in from any device afterwards.
- Your sessions. See every device signed in as you and sign one out, from the account menu.
- Report a problem. The bug icon in the header opens a ticket on the forge's own tracker, already filled in with the build and the page you were on.
- Chat per repository, with presence, unread counts that update in place, and a desk layout on wide screens.
- Landings show a pressed state while the store merges, and an armed "land when green" is a visible status that fires on its own once the checks pass.
- Forum threads show one post per edit, with a history page for every version.
- CI page names who committed straight to a protected branch, lets an admin acknowledge findings, and pages its runs.
- Repository tabs hide what a repository cannot use: mirrors carry no landings, CI or chat.