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