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