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