A CLI-first git forge.

cli forge git self-hosted

https://gitbay.org

Commit b4684c088d

b4684c088d2b99f0f42c4e95231c4c0edc122323

parent: 4e8f979415

Verified · cmc ci/build: success

cmc <hello@cleberg.net> · 2026-08-25T21:13:42Z

changelog: v0.4.0
CHANGELOG.org +22
@@ -4,6 +4,28 @@ Versioning follows semver from v0.1.0. Database migrations run
44 automatically on daemon start; upgrade notes appear per release when
55 anything beyond "replace the binary and restart" is needed.
66
7* v0.4.0 — 2026-08-25
8
9 Git LFS: standard clients work over both transports.
10 =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
11 included; download needs read, upload write), minting stateless
12 repo- and operation-scoped tokens for the batch API and basic
13 transfers. Anonymous HTTPS downloads for public repos; uploads
14 verified against size and sha256 before landing. Storage is
15 content-addressed under =[lfs] root= behind a small interface an
16 S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
17 objects (512MB default).
18 Build failures mail the repo's notify targets with the log tail and
19 build link — failed scheduled jobs reach an inbox.
20 =release edit= updates a release's title and notes (absent flags
21 keep their field); omaha-style CI note rebuilds work again.
22 Syntax highlighting follows the color scheme: class-based chroma
23 with light and dark palettes, the light-pinned code background is
24 gone, and markdown fences and org src blocks highlight too. The UGC
25 sanitizer admits only chroma's token-code classes.
26
27No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
28
729 * v0.3.0 — 2026-08-25
830
931 - CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=