CHANGELOG.org
612 lines · 32443 bytes
1#+title: gitbay changelog
2
3Versioning follows semver from v0.1.0. Database migrations run
4automatically on daemon start; upgrade notes appear per release when
5anything beyond "replace the binary and restart" is needed.
6
7* v1.9.0 — 2026-09-03
8
9The runner is no longer an admin, the web no longer reaches around the
10registry, and the CLI stops paying a handshake per command.
11
12- =keys add --scope runner= confines a key to =runner next/log/done= and
13 read-only git; the runner commands accept that scope or an admin. The
14 systemd drop-in sandboxes the runner process. gitbay.org's runner now
15 polls as a non-admin =ci= account scoped to one repository. #92
16- The web's repo create, issue create and edit, MR edit and both comment
17 forms dispatch the command the CLI runs, so the repository quota, the
18 archived-repository refusal, notifications, the body format and the
19 audit entry hold from a browser. #93
20- The CLI shares one SSH connection per instance (=ControlMaster=, five
21 minutes idle): a command costs a round trip instead of a handshake,
22 0.4 s instead of 4 s from a distant laptop. =no_multiplex = true= on
23 an instance opts out. #94
24- A disabled account is refused on every surface, and disabling revokes
25 its API tokens along with its sessions. #95
26- CODEOWNERS gates whenever the file exists on the target branch, not
27 only under =require-approvals=. #99
28- The HTTP listeners have header and idle timeouts, and SIGTERM drains
29 in-flight requests and SSH sessions before exit. #104 #105
30- =git archive= runs under a two-minute deadline and a 512 MiB cap. #124
31- Every git invocation ends option parsing before the ref, so a ref
32 shaped like an option is a bad revision and never a flag. #135
33- The admin noun is gated in the dispatcher as well as in each handler;
34 registry tests cover that and =ReadsStdin=. #127
35- An e2e test runs every =ReadOnly= command against a populated instance
36 and fails on any row it changes. #97
37- =http.trusted_proxies= attributes proxied API requests to the last
38 untrusted =X-Forwarded-For= hop for rate limiting; =email add= is
39 capped at five codes an hour per account. #136
40- A merge request head is built in the target repository, at
41 =refs/merge-requests/<n>/head=, so a fork's merge request has
42 =ci/<job>= statuses for =require-checks= to gate on. A head from
43 another repository is built without the target's secrets. #98
44- Triggers refuse deleting a user or organization that still owns
45 repositories, whatever path the delete takes. #136
46- The stylesheet's fonts are served again, and directory crumbs on blob
47 and blame pages link to the tree. #102 #103
48- The Threat-Model wiki page covers the runner. #138
49
50Replace the binary and restart, reinstall the CLI, and =make
51deploy-runner=: the runner fetches merge request refs before checkout.
52Migrations 0032 and 0033 run on start. The daemon host needs git 2.24
53or newer for =--end-of-options=.
54Operators running =gitbay-runner=: give it a non-admin account with a
55key added by =keys add --scope runner=, remove the admin key it held,
56and =make deploy-runner= to install the sandboxed unit drop-in; an
57admin key keeps working meanwhile.
58
59* v1.8.1 — 2026-09-03
60
61Markdown and org files render when opened.
62
63- A =.md=, =.markdown= or =.org= file renders on its page the way a
64 README does on the directory page, through the same renderer with
65 relative links resolved against the file's directory. =source= in the
66 action bar, or =?view=source=, shows the text as before. Every other
67 file is unchanged. #88
68- The e2e harness waits for the HTTP and git listeners as well as SSH
69 before a test starts; a test whose first act was an HTTP request could
70 be refused, which failed two otherwise green runs. #91
71
72Replace the binary and restart. No migration.
73
74* v1.8.0 — 2026-09-03
75
76The tracker's lists narrow, labels have colours you set, and the CLI's
77help is the server's.
78
79- =issue list= takes =--label=, =--assignee=, =--author= and
80 =--milestone= (a title, or =none= for issues with no milestone);
81 =mr list= takes =--author= and =--milestone=. The store narrows in
82 SQL, and the web lists take the same names as query parameters and
83 show each active filter with a link that drops it and keeps the rest.
84 Both lists had taken =--state= and nothing else, so the web's
85 filtering could never match the CLI's. #84
86- =label list= shows a repository's labels with their colour and how
87 many issues carry each; =label set <label> [--color rrggbb|'']=
88 creates a label or sets its colour; =label remove= takes it off every
89 issue. The colour column had existed since labels did and nothing
90 wrote it. The hash is optional because over bare ssh a bare =#= starts
91 a comment for the tokenizer. =issue label --add= still creates a
92 colourless label on the fly. #85
93- =gitbay help= with a prefix or =--json= runs the server's help, the
94 only place flags are written down and whose JSON is the contract;
95 bare =gitbay help= is still the local tree. Cobra's built-in help had
96 owned the word, so =gitbay help --json= failed on an unknown flag. #86
97
98Replace the binary and restart, and reinstall the CLI for the help
99change. No migration.
100
101* v1.7.0 — 2026-09-02
102
103What an open instance needs before it is open: a cap on what one
104account can take, a way out of a browser session you no longer hold,
105and accounts that never verified do not stay forever.
106
107- =limits.max_repos_per_user= caps the repositories an account owns
108 directly; =repo create=, =fork= and =import= refuse past it with the
109 numbers. =limits.max_bytes_per_user= caps their disk: a push may be no
110 larger than what the owner has left, riding the same
111 =receive.maxInputSize= as the pack cap, and is refused outright when
112 nothing is left. Organizations are not capped. Migration 0031 adds
113 per-account overrides, set with =admin user limits <name> [--repos
114 n|default] [--bytes n|default]= and shown by =admin user show=. Both
115 default to 0, unlimited, so nothing changes until set. #82
116- =registration.pending_expiry=, a duration, removes self-registered
117 accounts still unverified after that long, hourly and once at start,
118 audited as =pending.expired=. Empty keeps them, as before. #82
119- =web sessions list= shows each unexpired browser session by a short id
120 with its creation and expiry; =web sessions revoke <id>= ends one and
121 =--all= ends every one. SSH-only, matching the token commands, and
122 scoped to the caller. #83
123- A step runs in its own process group and a cancel or timeout kills the
124 group. On a host whose =/bin/sh= is dash, killing the shell alone left
125 its child holding the log pipe, so a cancelled build held the runner
126 until the child finished on its own, minutes for a test suite. The
127 wait after a kill is capped at ten seconds besides.
128- A commit with a build still queued or running is not queued again
129 when a fast-forward lands it; the v1.6.0 skip counted only a finished
130 success. #90
131
132- =golang.org/x/crypto= v0.56.0: GO-2026-6354 and GO-2026-6355 in its
133 =ssh= package, both reached through =ssh.NewServerConn= in the
134 embedded SSH server; one is a denial of service on a deadlocked
135 undecided channel.
136
137Replace both binaries and restart: =make deploy= for the daemon
138(migration 0031 adds two columns to =users= on start), then
139=make deploy-runner= for the process-group kill.
140
141* v1.6.1 — 2026-09-02
142
143A cancel reaches a build in its clone.
144
145- The runner honoured a cancel only in its step loop; a build cancelled
146 during its clone or checkout ran git to completion first, which on a
147 loaded host was long enough for the v1.6.0 test to fail on the CI
148 host while passing locally. One =runStep= now drives the clone, the
149 checkout and each step with the cancel signal and the deadline, and
150 checks the signal before starting at all. The runner logs how its log
151 session ended when that was not a cancel.
152
153Replace the runner: =make deploy-runner=. The daemon is unchanged from
154v1.6.0.
155
156* v1.6.0 — 2026-09-02
157
158The v1.4.0 admin surface answered questions about accounts. This one
159answers questions about the machinery: which runner is alive, what is
160stuck, whether last night's backup exists, and it lets an operator stop
161a build instead of waiting it out.
162
163- A build a runner claimed and never reported is failed by the
164 scheduler's minute tick, with no runner involved. It used to happen
165 only when some runner polled again, so a dead sole runner left its
166 builds running forever. =GITBAY_STALE_BUILD_DEADLINE= shortens the
167 deadline for tests. #75
168- Runners are visible. Migration 0030 adds =runner_seen=: one row per
169 runner account with its last poll, the =-repos= scope it asked for,
170 and the build it holds. =admin runners= lists them, over SSH and on
171 the host. #76
172- =GET /healthz=: whether the database answers and which commit serves,
173 no auth, no repository data, 503 when the database does not answer.
174 =healthz= joins the reserved names. #77
175- The host monitor's hourly reading carries the age of the newest full
176 backup and database snapshot, alerting at 25 and 2 hours, and the
177 daemon's own =/healthz= answer read through =site_url=. Both ride the
178 journald line and the webhook body. #78
179- =admin stats= reports =lfs_bytes=. =admin gc --lfs= scans every
180 repository's objects for LFS pointers and removes stored objects none
181 names, keeping anything younger than a day since git lfs uploads
182 before it pushes. #79
183- =admin backup --verify <archive>= reads an archive back: SQLite's
184 integrity check on the snapshot, and the repositories it names against
185 the archive's. A database-only archive says so. Damage or a missing
186 repository exits non-zero. #80
187- A commit that already passed a job on another branch is not built
188 again when a fast-forward lands it. Merging the six-layer v1.6.0 stack
189 had queued eighteen jobs for commits that had each just gone green.
190 Failed or abandoned builds still re-queue. #90
191- =build cancel <owner/name> <n>= withdraws a queued build or ends a
192 running one. For a running build the server closes the runner's log
193 session, the runner kills the step within seconds, and its late report
194 changes nothing. The commit status goes back to the passed result from
195 another build of the same commit when one exists, else reads
196 =cancelled=. Needs write access.
197- Deploys copy with =rsync --partial=, so a transfer the host's load
198 stalled resumes, and =make deploy-runner= installs a systemd drop-in
199 (=Nice=10=, =CPUWeight=30=, =IOWeight=30=) so a build never starves the
200 host's sshd again.
201
202Replace both binaries and restart: =make deploy= for the daemon, then
203=make deploy-runner= for the runner, which carries its half of running-
204build cancellation and installs the drop-in. Migration 0030 adds the
205=runner_seen= table on start. The monitor change ships in
206=deploy/cloud-init.yaml=; an existing host takes it by hand.
207
208* v1.5.0 — 2026-09-02
209
210Merge requests stack.
211
212- A merge request whose target is the source branch of another open
213 merge request in the same repository is stacked on it. Nothing is
214 stored and no flag exists; the forge reads the stack from the
215 branches. =mr create= says =stacked on !A= when it applies, =mr show=
216 carries =stacked_on= and =stacked=, =mr list= rows carry =stacked_on=,
217 and the page says both directions in the header. #87
218- When the lower merge request merges, everything stacked on it is
219 retargeted onto what it merged into, with a system comment naming the
220 merge and its reviews kept: after a fast-forward or merge commit the
221 diff against the new target is the diff they were of. A squash or
222 rebase merge under a stack is refused, naming the stack, since it
223 would rewrite the commits the stack builds on.
224- The first stack merged on gitbay.org was the six merge requests of
225 v1.6.0, bottom-up, with no =mr retarget= typed. The wiki's
226 Stacked-MRs page walks through it.
227
228Replace the binary and restart. No migration.
229
230* v1.4.0 — 2026-09-01
231
232Until now the instance had one operator surface: root on the host. Every
233question about the instance itself — who is on it, what is stuck, what a
234spam repository is doing — needed a shell on port 2222. This release
235gives an instance admin the same answers over SSH, and one page on the
236web.
237
238- =admin user list= pages accounts by username with
239 =--state active|pending|disabled|admin=, each row carrying its state
240 and =last_seen=, the newest use of any of its SSH keys or API tokens.
241 =admin user show <name>= adds the keys with their last use, each
242 address with how it was verified, PGP keys, org roles, owned
243 repository count, API token names and live browser sessions. Both are
244 SSH-only and refused to non-admins, like =audit=. #69
245- =admin user promote|demote=. The only way to admin was
246 =admin user create --admin=; an existing account could not be raised
247 and an admin could not step down. Demoting the last admin is refused
248 inside the transaction that counts them. The host-local twin is the
249 recovery path when no admin key is reachable. #70
250- Repository overrides for moderation: =admin repo list= with size and
251 last push, and =admin repo archive|unarchive|visibility|delete=. Policy
252 still knows nothing about instance admin — a private repository
253 answers not-found to an admin as before — so each override skips the
254 access check explicitly and writes its own =admin repo.<action>= audit
255 row. #71
256- =gitbayd admin= dispatches into the registry. User create, disable,
257 enable and delete, email verify, invite and stats were reimplemented on
258 the host; they now live in the registry, SSH-only and admin-gated, and
259 the host binary runs them as the host — an admin context with no
260 account behind it, so its audit rows say =source: host= where a
261 session says the key fingerprint. Invite and stats gain an SSH twin by
262 the same move. =backup=, =gc= and the backfills stay host-local. #72
263- =audit= filters: =--actor <user>= or =--actor -= for actorless rows,
264 =--action <prefix>=, and =--since= as a duration (=30m=, =24h=, =7d=)
265 or a date. =gitbayd admin audit= takes the same flags and =--json=. #73
266- =dashboard= carries a =queues= block for admins: per worker —
267 webhooks, mail, mirrors, builds, dependency checks — the pending,
268 retrying and dead-lettered counts, the oldest pending age, and the
269 retrying or failed rows themselves, capped at twenty each. The mail
270 queue was readable nowhere before. =/admin= renders the block by
271 dispatching =dashboard=; non-admins get a 404 and no rail link. #74
272- =gitbayd admin config show= prints the configuration in effect as
273 TOML, defaults filled in and =smtp_pass= redacted, so a support
274 question starts from what runs rather than what was written. #81
275- Build badges are served as PNG at =badge/build.png= as well as SVG,
276 for places that will not render SVG.
277- Host monitoring writes its reading to journald on every run and exits
278 non-zero on an alert, so an unset webhook no longer looks like a
279 healthy host; it reads the ACME cache where it actually lives and
280 reports the soonest expiry. govulncheck runs as its own CI job. The
281 database is snapshotted hourly by =gitbay-db-backup.timer=, keeping 48,
282 alongside the nightly full archive; archives inherit the database's
283 mode rather than the umask default. #28
284- A runner whose log stream drops no longer fails the build it was
285 recording. #67
286- =go.yaml.in/yaml/v3= and =golang.org/x/net= bumped. #60
287
288Replace the binary and restart. No migration. The =gitbay-db-backup=
289timer and the monitor changes ship in =deploy/cloud-init.yaml= for new
290hosts; an existing host takes them from there by hand.
291
292* v1.3.0 — 2026-08-31
293
294A runner took every repository's work, which decided where you could run
295one.
296
297- =runner next= takes optional =owner/name= arguments and =gitbay-runner=
298 takes =-repos=, so a runner claims builds only for the repositories it
299 names. Naming none is the old behaviour, so an existing runner is
300 unaffected. This is what makes a runner outside the server practical: one
301 on a machine that should build a single project no longer picks up a
302 build belonging to someone else, which with open registration need not be
303 anyone the operator knows. The scoping is what the runner asks for rather
304 than an ACL the server holds over it — a runner account is admin by
305 necessity, so the boundary is the operator choosing how to start it. #66
306
307Replace the binary and restart. Runners want the new binary too, though an
308old one keeps working unscoped.
309
310* v1.2.1 — 2026-08-31
311
312Merging landed commits without running anything.
313
314- A merge moves the target ref with a direct ref update, so it never
315 reached post-receive and none of the ref-update work fired: no =push=
316 event for webhooks to subscribe to, and no builds. Pushing a commit to a
317 branch ran the whole =.gitbay/ci.yml=; merging the identical commit ran
318 nothing. Both now happen in the merge path, with the build queueing
319 shared between it and post-receive rather than living in one of them.
320 #65
321
322Replace the binary and restart.
323
324* v1.2.0 — 2026-08-31
325
326A merge request said what its state was and almost nothing about when it
327got there. It now keeps time.
328
329- Reviews and checks carry the moment they last said something, on the
330 merge request page and in =mr show=. A =ci/<job>= check also reports how
331 long its build ran, so the timing of a run is readable without opening
332 it. Checks posted through =status set= have no build and report only the
333 time. !137
334- A merged or closed merge request names who resolved it and when. The
335 header stated "X wants to merge" whatever the state; it now says "X
336 merged A into main on <date>", or "closed this without merging", and
337 drops the claim entirely for a row that carries no stamp rather than
338 inventing a time.
339- =mr show= gains =merged_at=/=merged_by= and =closed_at=/=closed_by=, a
340 =created_at= per review, and =updated_at= plus =duration= per check, in
341 both JSON and text. Additive: nothing existing changed shape.
342- The iOS client renders all of it as of krz/gitbay-ios!37.
343
344Replace the binary and restart. Migration 0029 adds four columns to
345=merge_requests= and backfills the merge stamp for merge requests already
346merged, reading the =mr.merged= events. A merge with no such event to read
347— an import, or a row older than its events — keeps no stamp, and every
348surface says nothing about when it happened rather than guessing.
349
350* v1.1.0 — 2026-08-31
351
352Every release until now answered questions. This one notices something
353on its own: that a repository's dependencies have moved, and says so
354without being asked.
355
356- Dependency update checks, opt-in per repository. A daemon worker reads
357 the manifests on the default branch, asks the ecosystem's registry what
358 the current release is, and maintains one issue per repository — opened
359 when something falls behind, rewritten when the set changes, closed once
360 nothing is behind. No package manager runs, so it needs no CI runner and
361 no configuration beyond turning it on. #58
362 - =go.mod= against proxy.golang.org, =package.json= with
363 =package-lock.json= against npm, =Cargo.toml= with =Cargo.lock=
364 against crates.io, =requirements.txt= and =pyproject.toml= against
365 PyPI. A lockfile wins where both exist. A requirement naming a set
366 rather than a release — a range, a wildcard, a git or path source — is
367 skipped, since a range that already admits the newest release is not
368 news.
369 - =repo deps enable|disable|status=, a toggle on the repository settings
370 page, and the same three over the JSON API.
371 - Off by default, because checking a private repository tells a public
372 registry what it depends on. That is the owner's disclosure to make.
373 =[deps] check_interval_hours= sets the cadence, default 24.
374 - The issue is authored by a =gitbay-bot= account, so the existing
375 notification mail reaches the repository's owner rather than excluding
376 them as the actor. Its table is padded to its columns, which a
377 renderer ignores and a mail client needs. #61
378- =help= takes a prefix — =help mr= narrows the registry to one noun — and
379 every command now documents its arguments, so the server answers "what
380 are the flags" instead of being guessed at. #57
381- Web: settings rows end in one column of controls, checkboxes drawn at
382 the height of the inputs and buttons they sit beside #59; an added line
383 keeps its leading dash in the diff; a contributor's several verified
384 addresses collapse to one row #56.
385
386Replace the binary and restart. Migration 0028 adds two tables and, when
387the name is free, the =gitbay-bot= account. An instance already using that
388name for a user or an org keeps what it has: the account is not created,
389and dependency checks report that as the reason they cannot open an issue
390rather than the migration failing and the daemon not starting. #64
391
392* v1.0.1 — 2026-08-30
393
394Two CI fixes found by running orgo's release pipeline on this instance.
395
396- A runner killed between claiming a build and reporting it left the build
397 =running= forever, and the commit's =ci/<job>= status pending with it.
398 =runner next= now fails builds past a 90-minute deadline — longer than the
399 runner's own =-timeout= — and resolves their commit status. #53
400- =gitbay keys add= and =gitbay repo deploy-key add= take stdin as a bare
401 =< key.pub=, but only forwarded it when =--file -= appeared in the
402 arguments, so both sent an empty body and rejected input the SSH API
403 accepts. #55
404
405Replace the binary and restart.
406
407* v1.0.0 — 2026-08-26
408
409The web finishes the job #35 set it: reading, reviewing and responding,
410with the CLI still the complete interface. Every capability exists over
411SSH, every web write dispatches the same control command, and anything
412whose input is a credential stays on the command line. The [[https://gitbay.org/krz/gitbay/wiki/Parity][Parity]] page in
413the wiki is the maintained matrix and says which rows are deliberately
414CLI-only.
415
416- Diff view: one foldable section per file with line-number gutters,
417 per-file stats, rename and binary handling, and syntax highlighting
418 run per hunk per side so multi-line constructs lex as real code.
419 Commit and merge request pages share it; review threads anchor
420 inline.
421- Repository facts on the code page: commit, branch and tag counts,
422 detected license, latest release, build status, a language census by
423 tracked bytes, and contributors resolved to accounts by verified
424 email. All derived from git at render time.
425- Account settings on the web: SSH keys with scope, OpenPGP keys, and
426 email addresses. Public keys are the only credential-shaped input the
427 web accepts — they are not secret, and a new user needs one
428 registered before the CLI is reachable to them. Token minting and
429 account export stay SSH-only.
430- Organizations are run from their page: membership and roles, teams,
431 team members, and team repository grants, for org admins.
432- Commit log shows each commit's combined check status and gains a path
433 filter, so per-file history is reachable without editing the URL.
434- Issue references from commit messages read "referenced in commit
435 <sha> by <author>", linking the author when their email is verified
436 here.
437- The rail's focus ring uses the shell's own mark: the light scheme's
438 accent was a dark blue ring on a black rail.
439
440No migrations. No new config.
441
442Upgrading from v0.5.0 is replace-the-binary-and-restart.
443
444* v0.5.0 — 2026-08-26
445
446A design pass and a parity pass. The web stops being a read-only
447mirror of the CLI without becoming the place you are expected to work.
448
449- New design: a black shell with a persistent left rail carrying
450 cross-repo state (pinned repos, review queue), the repo header
451 rendered identically on every tab so navigation never moves, sharp
452 lines, self-hosted IBM Plex, and code blocks that read against both
453 color schemes. Tree listings sort directories first and carry each
454 file's last commit; diffs, inputs and controls were reworked to
455 match.
456- Web parity with the CLI, dispatched through the same command
457 registry the CLI and JSON API use — every web write is the
458 equivalent =gitbay= command with =--source web=:
459 - merge requests: review, resolve threads, merge, close, and open a
460 new MR from the browser
461 - issues: state, labels, assignees, milestones
462 - repositories: settings, branch protection, visibility
463 - releases: create and edit; builds: trigger a job
464 Commands marked SSH-only still refuse over the web: build secrets,
465 mirror tokens, domain claims, token minting, deletion and transfer.
466- A dashboard that answers "what needs me": review queue, assigned
467 issues, pinned repos, and an activity feed. Author names resolve to
468 accounts and link to profiles wherever commits appear.
469- Build status badges at =/{owner}/{repo}/badge/build.svg= for public
470 repos.
471- =[web] title= sets the instance's display name, separate from the
472 hostname commands are pasted with.
473- =make build/test/deploy= targets.
474- Fixes: the mobile tab strip scrolls sideways only, long commit
475 subjects no longer overflow on narrow screens, the shell fills the
476 viewport with the line-length cap moved onto prose, and the account
477 cell lines up with the page footer.
478
479No migrations. New config: =[web] title=.
480
481* v0.4.0 — 2026-08-25
482
483- Git LFS: standard clients work over both transports.
484 =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
485 included; download needs read, upload write), minting stateless
486 repo- and operation-scoped tokens for the batch API and basic
487 transfers. Anonymous HTTPS downloads for public repos; uploads
488 verified against size and sha256 before landing. Storage is
489 content-addressed under =[lfs] root= behind a small interface an
490 S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
491 objects (512MB default).
492- Build failures mail the repo's notify targets with the log tail and
493 build link — failed scheduled jobs reach an inbox.
494- =release edit= updates a release's title and notes (absent flags
495 keep their field); omaha-style CI note rebuilds work again.
496- Syntax highlighting follows the color scheme: class-based chroma
497 with light and dark palettes, the light-pinned code background is
498 gone, and markdown fences and org src blocks highlight too. The UGC
499 sanitizer admits only chroma's token-code classes.
500
501No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
502
503* v0.3.0 — 2026-08-25
504
505- CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=
506 over SSH (admin-only runner protocol; statuses feed =require-checks=).
507 Per-repo secrets set over stdin and injected into build environments;
508 cron schedules (server-local time) and tag-glob triggers, mutually
509 exclusive per job; =build list/show/log/trigger= and a builds tab.
510- Pages: public repos' =pages= branches served on =<owner>.<domain>=
511 (=[pages] domain=), custom domains with DNS TXT ownership challenges
512 and 7-day expiry for pending claims, per-subdomain on-demand ACME.
513- Wikis (=.wiki= companion repos, access mirrors the parent) and teams
514 within orgs (members-role scoping, per-repo team grants).
515- Activity graphs on user and org pages, backfillable
516 (=admin backfill-activity=); commits attributed by verified author
517 email, deduped by sha.
518- MR pages list the commits the MR carries; =mr show= gains a commits
519 section.
520- Per-file history: =?path== on the web log, =--path= on =repo log=,
521 history link on blob pages.
522- Mirror status surfaced in =repo show= and the repo header
523 (admin-only), with sync errors visible; tag-only pushes now schedule
524 mirror syncs.
525- Rendering: GFM tables/strikethrough/autolinks/task lists, blob image
526 previews, raw serves images with real content types (README images
527 render under nosniff), 0BSD license recognition, repo website links,
528 compact dashboard pins.
529- =admin user delete= for accounts that anchor nothing, with named
530 blockers otherwise.
531- Fixes: wiki pages no longer overflow on mobile (iOS font-inflation
532 trigger), GHSA-free deps, secret values pipe correctly through the
533 CLI.
534
535Migrations 0020-0025 apply on start. New config: =[pages] domain=.
536The runner is a new binary (=gitbay-runner=); see the wiki's Admin
537guide for setup. Stress-tested against an import of git.git (82k
538commits): see the wiki's Performance page.
539
540* v0.2.0 — 2026-08-24
541
542- Deploy keys: repo-bound CI keys (=repo deploy-key=), ro/rw, rename- and
543 transfer-proof.
544- Commit statuses (=status set/list=), combined state on MR pages, and a
545 =require-checks= merge gate.
546- Email notifications for issue and MR activity (participants with
547 verified addresses; never the actor).
548- Inline review threads on MR diffs (=mr diff-comment/threads/resolve=),
549 stale on force-push, =require-resolved= merge gate.
550- Required approvals with CODEOWNERS (=require-approvals=; latest review
551 wins, author excluded) and a =require-resolved= gate; merge gate order
552 is checks → approvals → CODEOWNERS → resolved threads → signatures.
553- Web design revamp: token-based stylesheet (light+dark), wordmark and
554 favicon, aligned layout grid, card-based listings, designed 404,
555 mobile pass.
556- Cross-references and mentions: =#N=, =!N=, =owner/name#N=, =@user=
557 autolink in issue/MR text, viewer-aware for private repos.
558- Archived repositories (read-only with badge) and repo topics.
559- Blame view with signature-aware attribution and 1000-line pages.
560- Repository search (name/description/topic) and per-repo code search
561 (=repo grep=, web search tab); blob line anchors.
562- Homepage: dashboard for logged-in users (pinned repos via =repo pin=,
563 open MRs and issues involving you), landing page for visitors, full
564 public listing at =/explore=; MR diffs collapsed by default.
565- Milestones (=milestone create/list/close=, =issue/mr milestone=) with
566 web progress; issue templates from =.gitbay/issue-template*.md=
567 (CLI =$EDITOR= prefill and web form).
568- Issue actions from commit messages landing on the default branch:
569 =closes/fixes/resolves #N= closes, bare =#N= leaves a reference
570 comment; once per issue+commit.
571- Vanity Go imports: =[go_import]= config serves go-import meta tags, so
572 =go install gitbay.org/gitbay/cmd/...@latest= works.
573- Release script: =deploy/release.sh <tag>= builds reproducible
574 linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
575- Repository maintenance: =admin gc= (repack/prune, per-repo sizes),
576 =admin stats= (counts + disk usage), weekly =gitbay-gc.timer=.
577- Releases: tag-anchored notes and binary assets (=release= commands,
578 assets over SSH stdin/stdout, web releases tab with downloads).
579- GitHub history import: =repo import-issues= brings issues and PRs
580 (as merged/closed MRs) with comments, labels, and state, attributed
581 inline and resumable.
582- Push and pull mirroring (=repo mirror=): background sync, read-only
583 pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
584- Web signup at =/register= for open and invite instances.
585- Audit log (=audit=, =gitbayd admin audit=): every mutating command
586 with source key fingerprint, registrations, force-pushes, auth
587 failures. Hardening: per-IP auth-failure throttling
588 (=ssh_auth_rate=), =max_pack_bytes= enforced, =admin user
589 disable/enable=.
590- Account migration: =gitbay migrate --from <host>= (bundle
591 export/replay + client-side git mirror); =gitbay auth export= as a
592 user-level backup.
593- Editable issues and MRs (=issue edit=, =mr edit=, web forms).
594- Commit references appear as system messages with linked shas.
595- Design: top nav, repo listing rows (topics, license, last updated),
596 file table headers, README relative-link resolution, branch
597 dropdown, web pinning, org owner picker, label filters, linked
598 usernames and commit parents, =/privacy= page, blue accent.
599
600Upgrade notes: migrations 0006–0019 apply on start. No config changes
601required; =[go_import]=, =[mirrors]=, =web.privacy_notice=, and
602=web.mode = "accounts"= are opt-in.
603
604* v0.1.0 — 2026-08-24
605
606First tagged release: the complete CLI-first forge. SSH control plane
607(bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues,
608merge requests (ff/merge/squash/rebase with signature policy), OpenPGP
609and SSHSIG verification with retroactive re-verification, orgs, repo
610import, web UI (view-only or accounts mode), registration with invites
611and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups,
612ACME TLS, systemd deployment.