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