CHANGELOG.org

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