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