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