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.41.0 — 2026-10-01
   8
   9Terminal output that reads at a glance (#312–#315): colour by meaning,
  10coloured diffs, lists that show what needs you, and label swatches and
  11hyperlinks where the terminal has them. Piped and =--json= output are
  12unchanged apart from the items noted below.
  13
  14*Upgrade note.* The CLI from this release sends =truecolor= and =links=
  15in =--term= when the terminal supports them; an instance older than
  16v1.41.0 turns those into plain output. Upgrade the instance first, or
  17set =GITBAY_TERM=basic= until it is.
  18
  19- =[web] apple_app_ids= serves =/.well-known/apple-app-site-association=
  20  as JSON, so links to this instance open in the listed iOS apps
  21  (=TEAMID.bundle.id=). The file names owners, repositories and the
  22  repository pages the gitbay iOS app has screens for; settings, forms,
  23  downloads, raw files, feeds and the API stay in the browser. Empty,
  24  the default, leaves the path a 404. (#310)
  25- The web shows an issue's Close/Reopen and a merge request's Close and
  26  draft controls to its author as well as to writers, matching the
  27  commands: an author without write access could do it over SSH but had
  28  no button. (#311)
  29- Terminal output reads at a glance (#312): colour by meaning across
  30  every list and view (=private= red, signature states, references in
  31  cyan, yellow only for what waits on you), future times as =in 5h=,
  32  sizes and durations humanized, no unnamed trailing column or trailing
  33  whitespace, a mostly blank title column held to a third of the width,
  34  section headings in one style with empty dashboard sections left out,
  35  and errors after a red =error:= with =did you mean= for a mistyped
  36  flag and the usage wrapped. Piped and =--json= output are unchanged,
  37  except that =profile show='s section labels are plural (=links:=,
  38  =orgs:=, =members:=, =repos:=) and an unknown flag's message names the
  39  nearest flag. The server ignores =--term= options it does not know.
  40- Diffs at a terminal are coloured (=repo commit=, =repo diff=, =mr diff=,
  41  =mr range-diff=) and made safe like other user text. =repo commit= is a
  42  view with the signature state, signer, checks and a link; piped, it no
  43  longer prints the subject twice. =build log= at a terminal drops the
  44  tools' own colour codes, makes the rest safe, and marks step lines,
  45  the failed step in red. (#313)
  46- At a terminal, lists and views say what to do next (#314). =mr list=
  47  adds checks, review state (the merge gates' rule; =review requested=
  48  in yellow when it is yours) and age; =issue list= adds labels,
  49  assignee (yellow when it is you), comments and age, each from one
  50  query per page. =dashboard= opens with what needs you and shows eight
  51  lines of activity; =feed= splits who, what and where so outcomes carry
  52  their colours. =repo show= adds the clone URL, open counts, the latest
  53  release and the default branch's checks; =repo log= shows the author's
  54  name, age and signature; =repo refs= lists tags newest version first
  55  (piped too) and the default branch first; =repo tree= leads with the
  56  name; =release list= drops the tag from titles and adds the date;
  57  =build show= lists steps with their outcome, the open merge request
  58  and the log command; =milestone list= marks overdue and shows
  59  progress; =audit= data reads as key=value; =whoami= shows instance,
  60  key and scope; =auth keys list= marks this session's key; issue, merge
  61  request and release creation print the page's URL. A column empty on
  62  every row is left out.
  63- The CLI tells the server what the terminal can show (#315):
  64  =truecolor= when =COLORTERM= is =truecolor= or =24bit=, for a dot in
  65  each label's own colour in =label list=, and =links= in iTerm2,
  66  WezTerm, Ghostty, VS Code, kitty and VTE terminals, or with
  67  =GITBAY_LINKS=1= (=0= turns it off), for references that open their
  68  page (OSC 8). Checks read =✓ 3/3=, =✗ 1 failed=, =• 2 pending=.
  69
  70* v1.40.1 — 2026-09-29
  71
  72A concurrency limit for pushes, and =repo download= under the pack
  73limit (#308).
  74
  75*Upgrade note.* Pushes now queue past two at once instance-wide and one
  76per account or deploy key; a push idle for a minute after its pack
  77starts, or not at pre-receive within fifteen minutes, is cut. Raise the
  78=[limits] push_*= settings on an instance with heavier push traffic.
  79
  80- Pushes have a concurrency limit of their own, separate from the pack
  81  budget: =[limits] push_concurrency= (2), =push_per_principal= (1),
  82  =push_queue= (16) and =push_queue_wait= ("60s"), read like the
  83  =pack_*= settings. One principal may have up to half of =push_queue=
  84  waiting, so parallel pushes from one account queue. A deploy key
  85  counts apart from the account that registered it. The slot is held until receive-pack and its
  86  post-receive hook have finished; a busy push exits 1 with "the server
  87  is busy: it is at its limit of concurrent pushes…", and the daemon
  88  logs a =push limit= warning at most once a minute. (#308)
  89- A push holding a slot is killed when its pre-receive has not started
  90  =[limits] push_receive_timeout= ("15m") after it took the slot, or,
  91  once its pack has begun or pre-receive has started, when nothing has
  92  moved either way for =push_idle= ("60s").
  93  receive-pack runs with =receive.keepAlive= set from =push_idle=, so
  94  long hooks do not trip it. (#308)
  95- =repo download= over SSH and the API takes a slot from the pack
  96  limit, released once =git archive= exits; busy is exit 1 with the
  97  clone message, and 503 with =Retry-After: 60= on both API
  98  endpoints. (#308)
  99
 100* v1.40.0 — 2026-09-29
 101
 102DKIM verification for reply mail, and ids that are not reused after a
 103delete (#306, #307).
 104
 105*Upgrade note.* Migration 0074 rebuilds the users, orgs, repos,
 106ssh_keys, api_tokens, webhook_deliveries and push_queue tables in one
 107transaction; take a backup first (=gitbayd admin backup=). Migration
 1080075 removes grants, deploy keys and profile about rows that name a
 109deleted account, organization or repository, and the daemon logs the
 110counts with the "schema migrated" line. To authenticate reply mail
 111without the mail host's Authentication-Results, set
 112=[mail.inbound] require_dkim = true=.
 113
 114- =[mail.inbound] require_dkim= makes gitbayd verify a reply's DKIM
 115  signature itself: one of the first five signatures must verify
 116  (rsa-sha256 with a key of 1024 bits or more, or ed25519-sha256), have
 117  a =d== in relaxed alignment with the From domain, and cover From, the
 118  To or Cc holding the reply address, Content-Type, and Message-ID when
 119  present; an unsigned Content-Transfer-Encoding must be 7bit, 8bit or
 120  binary. The reply address is then
 121  read only from To or Cc. =l==, rsa-sha1, an expired =x== and a =t==
 122  in the future are refused; a temporary DNS failure retries on the
 123  next poll; keys are cached for fifteen minutes; a passing signature
 124  is recorded so a copy posts once. Off by default; either it or
 125  =trusted_authserv_id= passing is enough. The start-up warning and
 126  =admin mail inbound check= now warn only when neither is set, and the
 127  check reports both settings. (#307)
 128- A reply whose header has a field name outside RFC 5322 =ftext=
 129  (=From : x=), no single From, or a repeated To, Cc, Message-ID,
 130  Content-Type or Content-Transfer-Encoding is refused. (#307)
 131- Ids of accounts, organizations, repositories, SSH keys, API tokens,
 132  webhook deliveries, queued pushes and builds are no longer handed out
 133  again after a delete. Before, the next row took the id of the newest
 134  deleted one, with anything that still named it: a deleted account's
 135  repository grants, a deleted repository's deploy keys, signed LFS and
 136  reply-by-mail tokens, a runner's claimed build. The migration rebuilds
 137  those tables and starts each sequence above every id still named
 138  (#306).
 139- Deleting an account or organization removes its repository grants
 140  and its parked profile about text, and deleting a repository removes
 141  its deploy keys. On upgrade, rows of these kinds left by earlier
 142  deletes are removed, and the "schema migrated" log line gives how many
 143  (#306).
 144
 145* v1.39.0 — 2026-09-29
 146
 147Suggested changes, split diffs, reactions, saved
 148queries, TeX math, code navigation, reply by mail, and web pages for
 149the repository rows Parity listed as no.
 150
 151*Upgrade note.* Migrations 0068–0073 run on start. Existing
 152repositories have no symbol index until their next push to the default
 153branch; =gitbay admin symbols reindex <owner/name>= builds one. Reply by mail is off until
 154=[mail.inbound]= is configured; set =trusted_authserv_id= for any
 155instance reachable from the internet (Admin wiki). On the web, =repo
 156delete= and =repo rename= now need a recent sign-in, like transfer.
 157
 158- The releases page uploads and removes release assets (the file is
 159  streamed to =release asset add=; removal asks for the name). The
 160  repository milestones page creates, closes and reopens milestones, and
 161  the org labels and milestones pages give org admins set, remove,
 162  create, close and reopen (#296).
 163- The repository settings page gains access grants and effective access,
 164  webhooks (add, remove, deliveries, redeliver; the secret is a form
 165  field passed on stdin and never shown again), rename, transfer and
 166  delete with typed confirmation. =/new= gains an import form for
 167  =repo import= (#296).
 168- Reply to notification mail to comment. With =[mail.inbound]=
 169  configured (an IMAP mailbox over TLS or STARTTLS, polled; password
 170  from =password_file=) and =notifications settings reply on= (per
 171  account, off by default; also on the account page), issue and merge
 172  request mail carries =Reply-To: reply+<token>@<domain>=. The token
 173  names the recipient, repository and thread, expires after thirty
 174  days, and is an HMAC under a key derived from the secret key file. A
 175  reply is posted as =issue comment= or =mr comment= by that account
 176  when it comes from one of the account's verified addresses and the
 177  account may still comment; quoted text and signatures are removed,
 178  HTML-only mail and automatic replies are refused, and a
 179  =Message-ID= posts once. Refusals mail nothing back and are audited
 180  as =refused mail reply= with the reason. =admin mail inbound check=
 181  tests the mailbox read-only. =trusted_authserv_id= makes a reply
 182  also need the mail host's DMARC pass or aligned DKIM pass in its
 183  topmost =Authentication-Results= header; unset, the daemon warns.
 184  A reply is refused when its account or repository was created after
 185  the token (a reused id). A migration adds =users.notify_reply=,
 186  =notifications.reply_to= and =mail_replies=. (#295)
 187- =web diff set unified|split= and a Diff layout control on the account
 188  page choose how the merge request, commit and compare pages draw a
 189  diff; =?layout=split|unified= overrides it per request. The split
 190  layout puts old and new side by side, each column's line numbers
 191  comment on their own side, and a narrow window stacks the rows as a
 192  unified diff. Migration 0068 adds =users.diff_layout=. (#290)
 193- Suggested changes in review threads: a fenced =suggestion= block in
 194  an =mr diff-comment= body proposes replacement lines for the
 195  anchored range, and =--start-line= anchors a thread to a range.
 196  =mr threads= and the page show it as a diff, marked outdated once
 197  the lines change at the head or the file is renamed or deleted;
 198  the JSON carries it as =suggestion=. =mr apply-suggestion= and the
 199  page's button commit it to the source branch as the applier, under
 200  the branch's push policy and write rules; a queued merge sees it as
 201  a push. The thread is resolved when the applier could resolve it by
 202  hand, and otherwise stays open with the output saying so. On a
 203  repository requiring signed commits the CLI commits and signs it in
 204  the clone instead. =repo commit-file= and applying a suggestion
 205  refuse once the owner's storage quota is used up, as a push does.
 206  Migration 0069 (#288).
 207- Reactions on issues, merge requests and their comments: =issue react=
 208  and =mr react= with a fixed set of eight, counts and your own in
 209  =show=, comment ids in =show=, and buttons on the web pages (#291).
 210- Saved queries: =query save|list|show|run|remove|pin|unpin= keep a
 211  named query over issues and merge requests across every repository
 212  the caller can read (=repo:=, =owner:=, =is:=, =label:=, =no:=,
 213  =milestone:=, =assignee:=, =author:=, free text). =issue list --query=
 214  and =mr list --query= run one, =--q= takes one written out, both paged
 215  with ={items, next}=. =dashboard= gains =queries= for pinned ones; the
 216  web shows them on the dashboard and at =/<you>/-/queries=. An account
 217  keeps at most 50 saved queries, 10 pinned (#292).
 218- TeX math renders server-side as MathML in markdown (=$…$=, =$$…$$=)
 219  and org (=$…$=, =\(…\)=, =\[…\]=, LaTeX environments) wherever
 220  markup renders, through a subset converter in =internal/texmath=.
 221  Its output is cleaned by a policy admitting exactly the elements and
 222  attributes it emits; MathML written as raw HTML is still stripped.
 223  Anything outside the subset, and math past 1000 expressions or
 224  256 KiB of TeX in one document, shows as source (#294).
 225- Code navigation. A push or merge to the default branch queues a symbol
 226  index of its tree, built by a background worker and keyed by the tree
 227  id, so an unchanged tree is not indexed again. =repo symbols
 228  <owner/name> <query>= finds definitions by name or prefix, and the
 229  blob view links names to their definitions, with a results page at
 230  =/{owner}/{repo}/symbols= and a per-file symbol list. Go is parsed;
 231  Swift, Rust, Python, JavaScript/TypeScript, C headers, shell, org and
 232  Markdown are matched by line. =admin symbols reindex= forces a
 233  rebuild. Migration: =symbol_indexes=, =symbols= and
 234  =symbol_requests=. (#293)
 235
 236* v1.38.0 — 2026-09-29
 237
 238Merge when ready, build egress by trust class, and restore-drill
 239tooling.
 240
 241*Upgrade note.* The runner's host needs the builds table: run =make
 242deploy-runner= (or install =deploy/gitbay-runner-builds.nft= and the
 243drop-in by hand), scoped to a scratch repository first, and run
 244=deploy/runner-auth-flood-test.sh= before pointing it back at real
 245repositories. A runner started with =-untrusted= or a loopback
 246=-remote= refuses to start without build cgroups. Runners off the
 247daemon's host and =-isolation none= are unaffected.
 248
 249- Marking notifications read from the web dispatches =notifications
 250  read=, so it counts against the write budget and is audited (#261).
 251- =gitbay <cli path> --help= for commands the CLI regroups (=auth keys
 252  add=, =auth email list=, =repo topics list=) prints EXAMPLES under the
 253  CLI's path instead of the registered one (#304).
 254- =gitbayd admin backup --verify= also checks every release asset the
 255  database names against its recorded size and sha256, and every
 256  archived LFS object against its name (#259).
 257- =gitbayd admin restore-drill <archive> --into <dir>= extracts a full
 258  archive into an empty directory, runs the =--verify= checks on the
 259  extracted copy, and prints the newest issue, comment and push it
 260  recovered and the elapsed time. The Admin wiki's Restore drill
 261  section lists what to restore, what to check and where to record it
 262  (#259).
 263- The runner starts each podman build under =builds/trusted= or
 264  =builds/untrusted= in its service cgroup, and a second nftables
 265  table (=deploy/gitbay-runner-builds.nft=) matches build traffic by
 266  that cgroup: no build reaches the host's loopback beyond DNS, or a
 267  private range; a trusted build keeps the internet and the forge's public 22,
 268  80 and 443; an untrusted build gets TCP 80 and 443 and DNS, and not
 269  the forge. The runner's drop-in creates the cgroups and loads the
 270  table on every start, and the start fails without it. A runner
 271  with =-untrusted= or a loopback =-remote= refuses to start without
 272  build cgroups, which the table needs to match anything. =make
 273  deploy-runner= installs it. =deploy/runner-auth-flood-test.sh= runs
 274  the scratch-repository test: a build failing SSH logins must not
 275  lock the runner out. Run it before pointing the runner back at real
 276  repositories; the Admin page has the steps and the rollback. (#260)
 277- =mr merge <n> --when-ready= queues a merge until the gates pass,
 278  merging as the queuing user with their rights checked then; tried on
 279  a status, a review, a resolved thread, =mr ready= and a push to the
 280  source branch. A refusal the queuer can fix, such as a branch behind
 281  a =require_signed_commits= target, keeps it queued with the reason
 282  on =mr show= and the page. The queue is bound to the key or token it
 283  was made with: removing, revoking, expiring or narrowing it
 284  dequeues, as do losing write access, a push or retarget by someone
 285  who cannot write to the target, deleting the source branch, and
 286  closing. An expiring credential cannot queue. =--cancel= dequeues.
 287  =mr show=, =mr list= and the dashboard carry =queued=. Migration
 288  0067 (#289).
 289
 290* v1.37.0 — 2026-09-29
 291
 292Findings from the 2026-09-27 architecture review.
 293
 294- =webhook add= reads the signing secret from stdin with =--secret -=;
 295  a value on the command line is refused, since argv shows in process
 296  listings and shell history. A script that passed the value must pipe
 297  it: =printf %s "$SECRET" | gitbay webhook add <repo> <url> --secret -=.
 298  The iOS app's webhook add breaks until it sends the secret on stdin
 299  (krz/gitbay-ios#21) (#284).
 300- =repo import --from= takes http and https URLs only; =git://= is
 301  refused, since its connection cannot be held to a checked address.
 302  The host is resolved and checked like a mirror's, git connects only
 303  to the checked addresses with redirects off, and the system and
 304  global gitconfig are ignored. A source that redirects (a renamed
 305  repository) fails; import from the URL it redirects to. Needs git
 306  2.37 or later on the server (#298).
 307- =repo import-issues= resolves and checks the API host and the git
 308  host once and connects only to the checked addresses: the API client
 309  dials them with no proxy from the environment and follows no
 310  redirect, and the pull-head fetch runs git pinned, with redirects
 311  off and without the system and global gitconfig. =--api-base= refuses
 312  credentials, a query or a fragment. An API that redirects (a renamed
 313  repository) fails; import under the new name (#301).
 314- =repo mirror add= refuses a host written numerically (=127.1=,
 315  =2130706433=, =0x7f.1=) when the mirror is added, rather than at its
 316  first sync (#298).
 317- A browser session creates credentials and grants access — keys, PGP
 318  keys, tokens, verified addresses, org and repository roles, transfers,
 319  repository visibility, webhooks, secrets, mirrors, and the admin
 320  promote/enable and repository-visibility actions — only within 15
 321  minutes of signing in. An
 322  older session gets the form back with a "Sign in again" link, and the
 323  login returns to it. SSH and API tokens are unaffected (#297).
 324- The builds page's status badge section gives an org-mode snippet
 325  beside the Markdown one, for a README.org (#299).
 326- API tokens on the settings page: create with a scope and optional
 327  expiry, shown once; list; revoke with the name typed back; the
 328  registered page's next steps as a numbered list (#264).
 329- A wiki link to an existing non-page file (an .svg, .txt, .pdf) now
 330  resolves to the raw route instead of 404ing against the page route
 331  (#283).
 332- The new-issue form takes labels, milestone and assignee in one step
 333  for writers; a Discussion heading sits before comment threads; the
 334  build page's live note says the page updates itself; and the rail
 335  and the phone More menu render from one list (#271).
 336- The new-issue form keeps milestone and assignee through preview and
 337  a refused create, the way it already kept title, body and labels;
 338  a refused create re-renders the form with the draft and the
 339  refusal instead of an error page (#271).
 340- The merge request range-diff page renders a bad =from=/=to== query
 341  parameter inline instead of 404ing; only an unknown merge request
 342  404s (#271).
 343- Empty states on the web state the fact instead of a CLI command, and
 344  drop "yet" on a finished item; the merge request list offers a New
 345  merge request link, a fork link, or a sign-in prompt depending on
 346  what the visitor can do; and the search page's scope caption is
 347  always visible, not only before a first search (#270).
 348- Issues, milestones, org milestones and releases drop the CLI command
 349  from their empty states too, matching the rest of the register: a
 350  link to the web form that does the thing when one exists, otherwise
 351  just the fact (#270).
 352- The merge request list and compare page offer New merge request to a
 353  reader who owns a writable fork of the repository, not only to a
 354  writer (#270).
 355
 356Credentials and sessions: revocation, delegation, expiry and an idle
 357timeout (#256, #257, #276, #277).
 358
 359*Upgrade note.* =token create= makes a =read= token unless given
 360=--scope full=. A script that mints a token and then writes with it
 361must add =--scope full=. Existing tokens keep their scope.
 362
 363*Upgrade note.* Upgrade the instance before the CLI: an older server
 364refuses the CLI's leading =--path== argument as an unknown command,
 365for the eighteen commands whose CLI path differs from the registry's
 366(the =gitbay auth ...= commands and =repo topics list=).
 367
 368*Upgrade note.* gitbayd needs =server.secret_key_file= (default
 369=/etc/gitbay/secret.key=) and refuses to start without it. Before
 370replacing the binary, run =gitbayd admin secrets init= as root and
 371=chown gitbay:gitbay /etc/gitbay/secret.key= (=deploy/install.sh= does
 372both when the file is missing). The first start seals the stored
 373secrets. Back the key file up separately: =admin backup= archives do
 374not carry it (see the Admin wiki, "Secret key"). Downgrading to an
 375earlier release after values are sealed is not supported: an older
 376gitbayd reads a sealed value's =gbs1:...= prefix as the literal
 377secret.
 378
 379*Upgrade note.* Archives now carry a directory entry for every
 380directory, so a bare repository whose refs are all packed restores as
 381a repository. An archive written before this release lacks those
 382entries; if extracting one leaves a repository's =refs/= directory
 383missing, =gitbayd admin backup --verify <archive>= names it, and
 384=mkdir -p <root>/repos/<owner>/<name>.git/refs= fixes it.
 385
 386*Upgrade note.* =repo import= now refuses a =git://= source and a
 387=--from= URL carrying a query or fragment. Mirrors and imports whose
 388host is written numerically (=127.1=, =2130706433=, =0x7f.1=) rather
 389than as a dotted address are refused too; rewrite the URL before
 390upgrading (#298).
 391
 392- A token with a =--ttl= is refused on every command that creates a
 393  credential: tokens, keys, deploy keys, runner keys, login links,
 394  invites, accounts and verified addresses (#257).
 395- Tokens and SSH keys record the token they were created through.
 396  =token revoke <name>= lists what it created; =--created= revokes
 397  those too (#257).
 398- Removing an SSH key, a deploy key, or disabling an account closes the
 399  connections the key opened, a push in flight included (#256).
 400- =keys add= and =repo deploy-key add= take =--ttl=; an expired key is
 401  refused at authentication, and an open connection on it closes within
 402  15 seconds. An expiring key cannot create credentials, like an
 403  expiring token. =keys list= and =repo deploy-key list= gain =USED= and
 404  =EXPIRES= columns, after the label (#277).
 405- =token list= at a terminal shows a future expiry as a time, not
 406  "just now" (#286).
 407- Browser sessions end after twelve hours without a request, and after
 408  seven days as before. Sessions open at upgrade get a fresh twelve
 409  hours. =web sessions list= shows when each was last used (#276).
 410- =web login= over SSH refuses a sixth link in an hour, the same bound
 411  the login page's mailed links have (#278).
 412- The HTTPS listener refuses TLS below 1.2, in both certificate modes
 413  (#281).
 414- Mail to a non-local relay requires TLS by default; a relay that does
 415  not offer STARTTLS gets no mail unless =mail.require_tls = false=
 416  restores the old behaviour. =mail.tls = "implicit"= speaks TLS from
 417  the first byte, for relays on port 465 (#280).
 418- Mirror sync resolves the host, checks the addresses and connects git
 419  only to them, with redirects off; a URL that now resolves to private
 420  space, or is not http or https, fails the sync with the reason on
 421  =repo mirror list=. A mirror of a renamed repository that redirects
 422  fails until its URL is updated. Sync ignores the system and global
 423  gitconfig. Needs git 2.37 or later: with an older git no mirror
 424  syncs, and each records why (#279).
 425- Webhook and mirror targets in 100.64.0.0/10 or on a multicast
 426  address are refused, as private addresses are (#279).
 427- The hook socket is mode 0600 and, on Linux, refuses a peer with
 428  another uid; each receive-pack gets its own token from sshd, stored
 429  hashed (migration 0063), and the hook must present it before the
 430  daemon acts. *Operators:* deploy with no push in flight, since a
 431  receive-pack started by the old daemon has no token and its
 432  post-receive will be refused by the new one (#282).
 433- Audit rows are hash-chained, each carrying the SHA-256 of the one
 434  before it (migration 0064), and the daemon logs a copy of every row it
 435  writes to its journal. =gitbayd admin audit verify= prints the row
 436  count and the last id and hash, and exits 1 naming the first row that
 437  was edited or whose predecessor was removed. The chain is unkeyed:
 438  someone who can write the database can recompute the later hashes,
 439  and verify catches an edit only when they were not recomputed.
 440  Comparing verify's last id and hash with the journal is the check for
 441  any change, including removing the newest rows (#275).
 442- Refused mutating commands (exit 3 or 4) are audited as =refused
 443  <command>=, and refused pushes as =refused git-receive-pack=, keeping
 444  flag names and the target but no values; ten a minute per account and
 445  600 across the instance, counted per process, past which one
 446  =refused.throttled= row stands for the rest of the minute. Under
 447  =ssh.mode = "system"= each =gitbayd shell= connection counts
 448  separately (#275).
 449- Pushes refused in pre-receive (a branch or tag rule, a release
 450  anchor, an unsigned commit) are audited as =refused push= with the
 451  repository and ref names, and hook socket requests failing the peer
 452  or push-token check as =refused hook=, under the same caps (#275).
 453- Audit retention deletes by id, up to the newest row older than the
 454  retention, so a clock step back cannot leave a gap in the chain (#275).
 455- =dashboard= and =feed= print activity as sentences
 456  (=cmc opened issue krz/gitbay#12=) instead of raw event payloads,
 457  and a labelled event names its labels there and on the web feed. An
 458  issue assigned to you appears only under "assigned to you": the
 459  =open_issues= field of =dashboard --json= no longer includes issues
 460  assigned to the caller. =notifications list= names =--all= when only
 461  read items remain (#265).
 462- Help and usage print the command the way the caller typed it —
 463  =usage: gitbay auth keys remove <fingerprint>=, not the registry's
 464  own path. =auth --help= lists the email and API token commands
 465  alongside keys and PGP. A bad-flag error prints the same prefixed
 466  usage line a wrong-argument refusal does. Outside the CLI a usage
 467  refusal reads =usage: ssh git@<host> ...= on every surface,
 468  including the error text of the web UI and the JSON API (#267).
 469- An unregistered SSH key is refused with its own fingerprint and the
 470  real host, and both the web and ssh paths to register (#268).
 471- =issue create= takes =--label= (repeatable), =--milestone= and
 472  =--assignee= (repeatable), setting them in the same call instead of
 473  a separate one per field (#268).
 474- =mr show= pluralizes multi-row section headings with counts: =commits (7):=,
 475  =checks (2):=, =reviews (3):= (#268).
 476- =repo readme <owner/name> [--ref <ref>]= prints a repository's README,
 477  picked the same way the web page picks one (#268).
 478- =repo show='s mirror table truncates =LAST SYNC= to the second, like
 479  every other timestamp in a view (#268).
 480- A =-- foreign_keys: off= migration's =foreign_key_check= now runs
 481  inside the migration's own transaction, before commit, so a
 482  violation rolls the migration back instead of leaving the bad
 483  schema and =user_version= already persisted; the web pin and watch
 484  buttons dispatch through =repo pin=/=unpin= and =repo
 485  watch=/=mute=/=unwatch= instead of writing the store directly, so a
 486  refusal reaches the viewer as a message instead of being dropped,
 487  and the watch button now cycles three states — default, watching,
 488  muted — instead of two; the response that consumes a login link's
 489  =?token== sends =Cache-Control: no-store=, so no intermediary keeps
 490  a copy of the single-use URL; and wiki documentation fixes:
 491  API.org clarifies token commands work on the API, Parity.org
 492  documents batched review and web watch/pin dispatch, Threat-Model.org
 493  documents the login-link URL exception (#261).
 494- The account settings page quotes the CLI and SSH command forms that
 495  actually resolve; a test runs every command a web page quotes against
 496  the CLI and control registries so a renamed command fails CI instead
 497  of shipping a dead instruction (#263).
 498- The web merge request page lists all revisions with a "compare to
 499  previous" link on each revision after the first, so a reviewer whose
 500  approval a force-push staled can see what changed without leaving the
 501  browser (#269).
 502- CI secrets, webhook secrets, mirror tokens and push device tokens are
 503  stored sealed with AES-256-GCM (#273). =gitbayd admin secrets
 504  init|rotate|check=.
 505- Untrusted builds (merge requests from forks) get a fresh HOME
 506  removed after the build and no secrets; trusted builds keep a
 507  per-repository home under =<workdir>/trusted-home=. Deploy gitbayd
 508  before the runner; the old shared homes under the runner's workdir
 509  can be deleted. (#255)
 510- =status set= refuses =ci/= contexts, which belong to the instance's
 511  builds. Build results are reused only from trusted builds on the
 512  same image. =repo settings require-contexts= names status contexts
 513  that must report green; setting any turns require-checks on, and one
 514  not yet reported counts as pending. (#258)
 515- A runner polling over loopback gives its podman builds =GITBAY_SSH=
 516  at =169.254.1.2=, pasta's address for the host, with the port when
 517  it is not 22, since under pasta the container holds the host's
 518  public address. An nftables table limits what the runner's user
 519  reaches on the host to =127.0.0.1:22=, DNS on loopback, and public
 520  22, 80 and 443. The runner unit now requires the egress unit: run
 521  =deploy/runner-podman-setup.sh= (it installs nftables) before =make
 522  deploy-runner=. Deploy gitbayd, then the runner, after validating on
 523  a scratch repository per the CI page. (#260)
 524- =build show= names a failed build's step and duration; =build log
 525  --step <n>|failed --tail <lines>= reads one step's output or the
 526  last lines of the stored log. Deploy gitbayd before the runner: an
 527  older server refuses the runner's =--step= and =--reason= (exit 2),
 528  and its failed builds stay running until the reaper fails them.
 529  (#266)
 530- =gitbayd admin backup= encrypts archives to =[backup] age_recipients=
 531  when set (#274); =--verify= takes =--identity <file>=. Archive names
 532  gain =.age=; the shipped backup scripts and monitor match both.
 533- A full backup holds =<root>/backup.lock= from its database snapshot
 534  to its last repository; =repo delete=, =repo rename=, =repo
 535  transfer=, =admin repo delete= and =org rename= refuse with "a
 536  backup is running" while it runs. =--verify= now also runs =git
 537  fsck --connectivity-only= on each archived repository and names any
 538  that fail. (#259)
 539- A full backup archives each repository's HEAD, =refs/= and
 540  =packed-refs= before its objects, so a push during the backup cannot
 541  leave an archived ref naming objects the archive lacks. The exception
 542  is git's own automatic gc after a push repacking during the walk: the
 543  archive can then miss objects, and =--verify= reports it. (#259)
 544- =gitbayd admin gc= and =admin mr prune= refuse with "a backup is
 545  running" during a full backup. A pack or loose object that git's
 546  automatic gc removes while the backup walks is skipped instead of
 547  failing the run; =--verify= reports it if a ref needed it. (#259)
 548- =gitbayd admin backup= and =--verify= no longer need the secret key
 549  file: sealed values are copied as they are. A missing database is
 550  refused instead of created. (#259)
 551- =gitbayd admin backup= refuses an =--out= inside =server.root=, and
 552  removes the snapshot directories and temporary archives a killed run
 553  left beside its archive once they are a day old. (#259)
 554- =gitbayd admin backup --verify= runs fsck with =--git-dir=, so a
 555  directory that is not a repository fails instead of git checking an
 556  enclosing one, and does not extract =objects/info/alternates= or a
 557  repository's =commondir=, so neither can point fsck at another
 558  repository on the host. (#259)
 559- =gitbayd admin secrets init= and =rotate= hold an flock on =<key
 560  file>.lock=, so two runs at once serialize. (#273)
 561- Git pack generation (clones, fetches, =git archive --remote=) over
 562  SSH, smart HTTP and git:// now shares one concurrency budget:
 563  =limits.pack_concurrency= (3), =pack_per_principal= (2), =pack_queue=
 564  (32) and =pack_queue_wait= (60s). Past the queue an SSH client sees
 565  "the server is busy…" and exits 1, HTTP gets 503 with
 566  =Retry-After: 30=, and git:// gets an =ERR= line. *Operators:* the
 567  defaults are tuned for a four-core host; set the three counts to -1
 568  to turn the limit off. A running clone is killed when no write to
 569  its client completes for two minutes: a client reading below about
 570  550 B/s, or an HTTP request body that takes over two minutes with
 571  nothing written back, is cut. Ref listings, pushes and =repo
 572  download= are unaffected. Under =ssh.mode = "system"= SSH clones are not counted,
 573  since each session is its own process (#262).
 574- Anonymous clones are counted per IPv4 address or IPv6 /64, and
 575  together hold at most =pack_concurrency= − 1 slots: an account can
 576  take the last slot when it is free, and anonymous clients cannot hold
 577  it (#262).
 578- A request turned away by the pack limit logs a warning naming the
 579  transport and whether the client was signed in, never its address,
 580  at most once a minute per transport (#262).
 581- Web archive downloads (=/{owner}/{repo}/archive/{ref}.tar.gz=) take
 582  a pack slot, answer 503 with =Retry-After: 30= when none is free, and
 583  are killed when the client leaves or stops reading (#262).
 584- LFS transfer tokens name the SSH key that obtained them, deploy keys
 585  included, and every LFS request checks that the key is still
 586  registered, unexpired and on an enabled account: removing a key or
 587  disabling an account ends its tokens at once instead of within the
 588  hour (#285). *Operators:* tokens minted before the upgrade are
 589  refused. git-lfs asks =git-lfs-authenticate= for a token each time
 590  it runs, so only a transfer running across the restart fails, with
 591  "repository not found"; running the command again fixes it. A
 592  download from a public repository that presents a token issued
 593  before the upgrade is refused the same way, not served anonymously,
 594  and needs the same rerun.
 595- Every LFS request also repeats the repository check for the token's
 596  key: a collaborator whose access is revoked or reduced, or a reader
 597  of a public repository made private, loses the token's use with the
 598  access, and an upload token stops working once its repository is
 599  archived (#285).
 600- LFS transfer tokens carry a hash of their key's fingerprint beside
 601  its id, and a token whose key id now belongs to another key is
 602  refused, since SQLite gives a new key the id of the last deleted one.
 603  The token format changed: tokens minted before the upgrade are
 604  refused, and a transfer running across the restart needs running
 605  again (#303).
 606
 607* v1.36.0 — 2026-09-23
 608
 609Terminal output for the CLI (#254).
 610
 611*Upgrade note.* Upgrade the instance before the CLI: an older server
 612refuses the CLI's leading =--term= argument as an unknown command.
 613Against an older instance, set =GITBAY_TERM=off= and the CLI sends no
 614terminal size.
 615
 616- At a terminal, lists print under a header, fitted to the width, with
 617  states in colour and relative ages; the next page is a command on
 618  stderr. Piped output keeps the same tab-separated rows, with
 619  timestamps as RFC3339 to the second; =repo log= rows are
 620  tab-separated (were fixed-width) and =repo settings show= keys print
 621  as fields (=require mr=, not =require_mr:=).
 622- =show= commands print a title line, aligned fields, the body
 623  rendered from markdown or org, events one per line and comments
 624  under a rule, through a pager when longer than the screen.
 625- Help describes every flag, with defaults and examples, and
 626  =gitbay --help= groups the commands under WORK, REPOSITORIES, YOU
 627  and INSTANCE. =help --json= adds =flags= and =examples=.
 628- =release list= takes =--limit= and =--cursor=, and leaves the title
 629  empty when it repeats the tag. =mr revisions='s one-revision note
 630  moved to stderr. =notifications device add= prints =registered
 631  device <n>=. =dashboard= prints =none= under an empty section.
 632
 633The CLI sends =--term=<cols>[,color]= as the first argument on the
 634SSH command line, since OpenSSH's multiplexed sessions do not forward
 635a session's =SetEnv=; the server reads it only there, and ignores it
 636over HTTP. Stock ssh opts in with =ssh git@gitbay.org -- --term=120,color
 637issue list krz/gitbay= (the =--= keeps ssh from reading it as its own
 638option) or =-o SetEnv=GITBAY_TERM=120,color=. Operators running
 639the system-sshd forced command add =AcceptEnv GITBAY_TERM= to
 640=sshd_config= for the =SetEnv= form; the =--term= argument needs no
 641sshd configuration.
 642
 643* v1.35.1 — 2026-09-23
 644
 645The landing page's recording (#253).
 646
 647- The landing page plays a recording of signup to release from a
 648  terminal on gitbay.org, muted with controls, in place of the merged
 649  merge request picture. The quickstart block drops its comment. The
 650  tapes and the render script are in =docs/demo/=.
 651- =/static/img/= serves gif, webm and mp4 with their own types and
 652  answers Range requests, which Safari needs to play video.
 653- The Quickstart wiki page shows the recording as a gif.
 654- The footer's iOS link goes to the App Store listing.
 655
 656* v1.35.0 — 2026-09-23
 657
 658Following a running build (#250, #251), and the web interface
 659guidelines review (#249).
 660
 661- =build log <owner/name> <n> --follow= prints the stored log, then
 662  output as the runner sends it, then =build <n> <status>= on stderr
 663  once the build ends; the exit code is 0 whatever the outcome. The
 664  build page does the same without JavaScript while a build is queued
 665  or running: the log streams into the page and ends with "build
 666  finished: <status>". =?follow=0= and HEAD render it once.
 667- A follow ends when its reader leaves: a closed SSH channel (Ctrl-C
 668  over the CLI's shared connection included) or a closed page. A
 669  follow of a build still queued after ten minutes ends and says so,
 670  since nothing reaps a queued build. An account holds eight follows
 671  at once; signed-out viewers share one account's eight.
 672- A follow re-checks read access every two seconds by repository id,
 673  reloading the account: a repository made private or an account
 674  disabled ends it as not found; a rename does not.
 675- A restart ends open follows before the drain, with "gitbay is
 676  restarting; follow the build again in a moment" on every surface,
 677  instead of holding the drain for 30 s. Other requests, git transport
 678  included, drain as before.
 679- Over the JSON API the command answers when the build ends, with the
 680  whole log.
 681- Typed-name confirmation on removing an org member, removing a team
 682  member, revoking a team's repository grant, and promoting an account
 683  to admin. The team forms are split so the confirm field sits beside
 684  the removal only.
 685- Registration's email field is an email input; email, username,
 686  one-time-code, SSH key and identifier fields carry =autocomplete=,
 687  =autocapitalize= and =spellcheck= as fits. The merge request close
 688  field accepts the =!12= its placeholder shows.
 689- The refs page's compare inputs are named by their visible labels;
 690  the line-comment link names its line. =theme-color= matches the rail.
 691- Behind a reverse proxy, turn response buffering off for the build
 692  page (=X-Accel-Buffering: no= covers nginx), or the live log arrives
 693  only when the build ends.
 694
 695* v1.34.1 — 2026-09-21
 696
 697Three findings from an external review of the web UI (#248).
 698
 699- Explore is a rail square at every width. It was =.railopt=, so it
 700  dropped below 34rem into the More menu, which exists only for a
 701  signed-in viewer: a signed-out phone had no route to the listing from
 702  any page. Six squares and the mark are 308px, inside a 320px phone.
 703- =/register= answers "no key yet?" in place, with the =ssh-keygen= and
 704  =cat= lines behind a disclosure, instead of linking out to the wiki
 705  over a half-filled form. The link also hardcoded =gitbay.org=.
 706- An empty =/search= says what to do next — fewer words, the same query
 707  across every kind, or the listing — rather than repeating the count
 708  line's "no matches".
 709
 710* v1.34.0 — 2026-09-21
 711
 712The profile's tabs, reworked.
 713
 714- The bar reads About, Repositories, Bookmarks, Snippets, and People
 715  for an organization's admins. =/{owner}= is About; the rest hang off
 716  =/-/=. A tab nobody may open is not offered and its URL is a 404.
 717- The activity graph moved inside About, with a log of the newest
 718  thirty events under it. The log counts what the graph over it counts:
 719  =UserPublicEvents= keys on the actor for a user, matching
 720  =ActivityByDay=, while an organization keeps =OwnerPublicEvents=. Both
 721  are public repositories only. =activity.atom= is still the feed that
 722  goes back further.
 723- Bookmarks are a tab on your own profile. =repo bookmarks= takes no
 724  owner and lists the caller's, so the tab is not offered on anyone
 725  else's and its URL is a 404 there. =/bookmarks= redirects to it.
 726- The snippet list renders inside the profile rather than on a page of
 727  its own, so it carries the header and the tab bar like every other
 728  section. A snippet itself is still its own page.
 729
 730Eleven web findings, mostly alignment and affordance (#247).
 731
 732- Logging out asks first. =GET /logout= is the confirmation page the
 733  rail's signout square and the More menu link to; the button on it
 734  posts to the same path, which is still what ends the session.
 735- Bookmarks and Snippets are gone from the rail and the More menu. Both
 736  land on the profile, where they are tabs, and every square left in
 737  the rail is an instance-level destination.
 738- A repository tree marks a directory with a folder glyph and a file
 739  with a file glyph. The trailing slash still says it in text and the
 740  glyphs are =aria-hidden=, so the cue no longer rests on the link
 741  colour alone. Per-filetype icons are deliberately not done.
 742- A =/search= hit carries its kind in a chip, in the words =search=
 743  prints, so the meta line no longer has to say "repository".
 744- A settings row lines its control up on the right: a checkbox, a
 745  number and a full-width text input all end on the same rule, with
 746  Save in its own column. The label column keeps a 14rem floor so a
 747  hint does not wrap a word to a line.
 748- The email rows on =/settings= put their buttons and confirm field on
 749  the right, so they line up however long an address is.
 750- =/admin/users= draws a disabled Promote on an account that is not
 751  active, rather than leaving the cell short, and the page is wide. At
 752  48rem the Actions cell clipped the second form's button, which left
 753  its confirm field looking like it belonged to the button before it —
 754  an active row read as though Promote wanted the name typed. The cell
 755  is now two fixed slots, each right-aligned, so the role button, the
 756  confirm field and the access button each hold one column whichever
 757  controls a row carries: an admin's row has a field on both forms, a
 758  disabled account's enable form has none. The field is 14rem, which
 759  fits "type <name> to confirm" for a name of ordinary length.
 760- The profile's inactive tabs draw their underline in =--line=, so the
 761  strip reads as a track the current tab is marked in.
 762- =.listhead= sheds its children's block margins, which is what kept a
 763  =p.meta= from sitting level with the heading beside it.
 764- =nav.tabs= has a bottom margin.
 765- The footer links the iOS client.
 766
 767The e2e suite runs in parallel (#246).
 768
 769- =startInstance= linked a byte-identical 35MB gitbayd for each of the
 770  207 tests, about 0.8s apiece: go's build cache covers the compile,
 771  not the link. Each binary is now built once per process, lazily, so
 772  a =-run= of one test links only what it needs.
 773- 202 of the 207 tests take =t.Parallel=; the five calling =t.Setenv=
 774  stay serial. =freePorts= allocates from an atomic counter instead of
 775  binding =:0= and closing it, which raced once tests overlapped —
 776  =waitForPort= only asks whether something is listening, so the loser
 777  talked to another test's server.
 778- Locally on 12 cores the suite goes from 637s to two or three minutes.
 779  The =-timeout= floor the harness enforced (#143) is gone with the
 780  reason for it; =make test= and =.gitbay/ci.yml= still pass their own
 781  as a ceiling for a real hang.
 782
 783* v1.33.0 — 2026-09-21
 784
 785Five findings from the outside review of the web UI (#241–#245).
 786
 787- A run row on the builds page led with a ten-character sha, so
 788  recognising a build meant opening the commit or already knowing the
 789  sha (#241). =build list= resolves each distinct commit's subject in
 790  one =git log= and returns it as =subject= on every build, so the CLI,
 791  the API and the web all name the commit. The row leads with the
 792  subject and the sha follows as metadata; a build whose commit is gone
 793  falls back to the sha.
 794- =build list= takes =--limit <n>= and =--cursor <c>=, the keyset
 795  cursor =issue list=, =mr list=, =repo list= and =feed= already have
 796  (#244). Without the flags it returns the newest fifty matching builds
 797  as before, so existing scripts are unchanged — the cursor is what
 798  reaches past that window. The page asks for thirty, offers "older"
 799  carrying every filter, and says its count is this page's when there
 800  is another. Before, filtering to a sparse status reached much further
 801  back within the same cap and appeared to raise the run count.
 802- The profile is sections rather than one stack (#242). =/{owner}= is
 803  the repository list; About, Activity and an organization's People are
 804  tabs beside it at =/{owner}/-/about=, =/-/activity= and =/-/people=.
 805  A tab with nothing on it is not offered and its URL is a 404. The
 806  About text and the year of activity squares used to sit above the
 807  repository list and push it below the fold. =profile show= is
 808  unchanged.
 809- Explore names its filter: the number of repositories, the active
 810  query and a link that clears it, the line the builds page already
 811  carried (#243). An empty filtered list says nothing matched rather
 812  than that the instance has no public repositories.
 813- The landing page's picture was !315, closed without merging, with an
 814  empty review panel and alt text promising reviewers that were not
 815  there (#245). It is !450: merged, two CI checks reporting success
 816  with how long each ran, and an approval. The picture is a figure with
 817  a caption saying what it shows.
 818
 819* v1.32.1 — 2026-09-20
 820
 821A push alert names the account it is for (#89).
 822
 823- The payload carried =path= and nothing else, so a device signed in to
 824  more than one account could not tell which instance a notice came
 825  from: two instances can hold the same =owner/name=. It now carries
 826  =instance=, the instance's =site_url=, and =user=, the recipient's
 827  username — together the account's identity.
 828- =DuePush= joins =users= for the recipient; no schema change.
 829- =notifications device add= now returns the row id, so a client that
 830  wants to deregister does not have to list devices and match its own
 831  token against the truncated display value.
 832- The alert carries =aps.badge=, the recipient's unread inbox count.
 833  =DuePush= counts it at send time, a subquery against =inbox=, so a
 834  cleared inbox is reflected even though the row was queued earlier.
 835
 836* v1.32.0 — 2026-09-20
 837
 838Push notifications to iOS devices (#89): activity reaches a registered
 839phone the way it already reaches the inbox and mail.
 840
 841- gitbayd talks to APNs directly over HTTP/2, authenticated by an
 842  ES256 JWT signed with an operator-supplied =.p8= provider key. New
 843  config section =[push]=: =enabled=, =key_file=, =key_id=, =team_id=,
 844  =topic= (the app's bundle identifier) and =environment=
 845  (=production= | =sandbox=), all validated at load when enabled — a
 846  misconfigured =[push]= refuses to start rather than filling a queue
 847  nobody is watching. An APNs key belongs to a bundle id: a self-hoster
 848  ships their own build under their own =topic= to use this; the App
 849  Store build talks to gitbay.org.
 850- Migration 0059: =push_devices= and =push_queue=, and
 851  =users.notify_push= (default on).
 852- =notifications device add= (token on stdin), =device list= (token
 853  shown truncated), =device remove <id>=, and =notifications settings
 854  push on|off=. A device is dropped automatically when Apple reports
 855  the token dead (410 Unregistered or BadDeviceToken). With =[push]
 856  enabled = false= nothing is queued and =device add= refuses, rather
 857  than registering a device nothing can deliver to.
 858- =[retention] push= caps the delivery queue, beside =mail=.
 859- =dashboard= reports the push queue for admins beside the other five,
 860  by device id: a =key_id= or =team_id= Apple did not issue passes
 861  config validation and then dead-letters every send.
 862- =issue assign= now files a notice, so assignment reaches the inbox,
 863  mail and push.
 864- Notification text is sent in full, private repositories included: a
 865  repository's name and item number reach Apple and can appear on a
 866  lock screen.
 867- Web: the notification settings page carries the push toggle and the
 868  device list, with removal behind confirmation. No web page offers a
 869  device-add form — only the app can mint an APNs token.
 870
 871* v1.31.1 — 2026-09-20
 872
 873The stylesheet URL carries the build's hash (#239).
 874
 875- =/static/style.css= was served with a day's cache lifetime at an
 876  unversioned URL, and =must-revalidate= only forces a check once that
 877  lifetime expires. For a day after a deploy a browser rendered the new
 878  markup against its old stylesheet; the ETag was never consulted.
 879- The layout stamps the served bytes' hash on the link. A deploy changes
 880  the URL, so a cached copy cannot answer it, and a request carrying the
 881  current hash names bytes that cannot change and is served without
 882  revalidating at all.
 883
 884* v1.31.0 — 2026-09-20
 885
 886The desktop layout (#226): the web UI uses a wide screen.
 887
 888- One centered container at 100rem; the repository header, main and
 889  footer align on it. Text keeps its measure.
 890- The repository header is two rows: name, description and buttons,
 891  then the tabs.
 892- Issue, merge request, build, explore, search and notification rows
 893  are one line above 64rem, and those pages render at the container
 894  width.
 895- The dashboard is three columns: pinned repositories with open issue,
 896  merge request and last-build counts; a tile per queue with the queue
 897  rows below; the activity feed.
 898- A file navigator beside blob, blame and edit pages lists the file's
 899  directory and marks the file.
 900- Side columns: state, labels and open milestones on the issue and
 901  merge request lists; status, jobs and branches on builds; topics on
 902  explore; kinds on search; sections on repository settings, account
 903  settings and admin. A label or milestone nothing is filed under is
 904  left out, so the merge request list offers the labels that have
 905  merge requests rather than every label the repository holds; the
 906  branch group caps at ten, and the branch field below it still takes
 907  any ref.
 908- Below 62rem the facet and section columns become a closed disclosure
 909  before their content, headed by the filters in force, and the
 910  navigator hides, since the tree page is the navigator on a phone.
 911  Below 80rem the dashboard's pinned repositories return to a chip row
 912  above the queues.
 913
 914Three accessibility defects the wider scan found, on pages the
 915sixteen-page one never covered (#226):
 916
 917- A label chip carries a tone per scheme. Chip text is 12px, which owes
 918  4.5:1 against the ground mixed from the colour itself, and no single
 919  colour clears that on both canvases; the stored hex still names the
 920  label, and the page picks the tone. A page stamped light or dark now
 921  sets =color-scheme= to match, so native controls follow the theme.
 922- Every =pre= scrolls sideways, so every one takes =tabindex="0"=: a
 923  keyboard reaches a blame view, a build log and a search match the way
 924  it already reached the pre blocks of rendered markup.
 925- A link that shares its line with other text is underlined — a path
 926  crumb, a heading that names an owner, an empty-state note. Link and
 927  muted text are 1.07:1 apart in dark.
 928
 929The profile about text is a file (#236).
 930
 931*Upgrade note.* Run =gitbayd admin migrate-profile-about= after
 932upgrading. Migration 0058 parks each owner's about text in a holding
 933table and drops the columns; that command writes it into a public
 934=<owner>/.gitbay=. Until it runs, profiles that had an about show none.
 935Nothing is lost in between — the table keeps the text.
 936
 937- The about text on a profile is =profile/README.md= or
 938  =profile/README.org= on the default branch of =<owner>/.gitbay=,
 939  read with that repository's own access. The extension picks the
 940  renderer; =.md=, =.org= and =.markdown= resolve in that order.
 941  =profile show= gains =about_path=, the file the text came from.
 942- =profile set= and =org profile= lose =--about=, =--about-format= and
 943  =--file=. The about is written by a push or =repo commit-file=, the
 944  way a wiki page is. The settings page points at the file and offers
 945  to create the repository that holds it.
 946- Repository names may start with a dot; owner names may not. A
 947  repository whose name starts with a dot stays out of =explore= and
 948  off the profile's repository list, and remains in =repo list= and at
 949  its own URL.
 950- =repo commit-file= writes the first commit of a repository that has
 951  never been pushed to. An unresolvable branch is still an error
 952  anywhere the repository already has refs.
 953
 954A web UI sweep.
 955
 956- The rail's squares are 44px at every width, and its glyphs are 20px
 957  on a phone. Below 34rem eleven squares no longer fit, so explore,
 958  bookmarks, snippets, new repository, settings, admin and log out
 959  move into a More menu and the strip keeps dashboard, search,
 960  notifications, More and your account.
 961- Snippets are on the rail. The link on a profile page stays.
 962- =/new= creates an organization as well as a repository; the form
 963  leaves the profile page.
 964- =repo fork= takes =--owner=, and the web's Fork button opens a form
 965  with an owner and a name. The owner is you or an organization you
 966  administer, checked as =repo create= checks it; an organization's
 967  fork is not counted against your repository quota. A name of your
 968  own is how you fork the same repository twice.
 969- The dashboard's pinned key reads above the list rather than under
 970  it, its build dot sits on the row's centre line, and a pinned chip
 971  on the second row has its bottom border back.
 972- The activity feed drops its state dot.
 973- The SSH key and account tables keep each row on one line and scroll
 974  sideways, rather than wrapping a fingerprint or a timestamp.
 975- =.pathbar= actions sit on the centre line with the ref and the
 976  crumbs.
 977
 978The SonarCloud dashboard is at zero (#238). Four of its 38 findings were
 979real; the rest are dismissed with their reasons recorded on the
 980dashboard.
 981
 982- A trailing-slash redirect cannot leave the site. =net/http= fills
 983  =URL.Scheme= and =URL.Host= from an absolute-form request line, which
 984  RFC 7230 requires a server to accept, so =GET http://evil.example/cmc/=
 985  answered =301 Location: http://evil.example/cmc=. A browser sends
 986  absolute form only to a proxy, so nothing reached this through one
 987  directly.
 988- The global search, repository search and register forms no longer
 989  carry =autofocus=, which moved focus past the heading, the result
 990  count and the search page's filters. The diff line-comment box keeps
 991  it: that form renders only after the reader asks for it on a line,
 992  and with no JavaScript nothing else carries focus across the reload.
 993
 994* v1.30.0 — 2026-09-19
 995
 996Every command runs on every surface, markup previews before it is
 997written, and the web findings from the forge comparison (#232, #233,
 998#234, #235).
 999
1000*Upgrade note.* Dropping =SSHOnly= widens what a full-scope API token
1001can do: it can now administer the instance and mint further tokens.
1002Review the tokens you have issued and re-mint as =--scope read= any
1003that only need to read.
1004
1005- *Every command now runs on every surface.* The registry's =SSHOnly=
1006  flag is gone, and with it the refusal that met build secrets, mirror
1007  credentials, API token minting, web sessions, deploy keys, the audit
1008  log and instance administration when they arrived over HTTP. What a
1009  caller may do is the account's rights narrowed by the scope of the
1010  key or token the request came with, decided in one place. A
1011  full-scope API token can now do anything its owner can, minting
1012  another token included; a read-scoped one still cannot write.
1013  Operators should review the tokens they have issued and re-mint as
1014  =--scope read= any that only need to read (#234).
1015- =/admin/users= lists every account with the state filter and cursor
1016  =admin user list= takes, and runs promote, demote, disable and enable
1017  per row. Demote and disable ask for the username to be typed (#234).
1018- =[registration] notify_admin= mails the instance's admins when an
1019  account becomes active: an invite redeemed, or an open-mode signup
1020  that verified its address. Off by default, requires =[mail]=, and
1021  queued like any other notice (#234).
1022- Every web form that takes markup has a Preview button beside its own
1023  submit: issue and merge request create, their edit and comment boxes,
1024  release create and edit, the profile about text, and the file editor
1025  on a path the forge renders. It renders the draft above the textarea
1026  and writes nothing (#235).
1027- Links inside running text are underlined: the meta lines on issues,
1028  merge requests and releases no longer tell a link apart by colour
1029  alone.
1030- File view line numbers are 24px targets and keep the focus ring;
1031  chroma's LineLink rule, which set =outline: none=, is dropped from the
1032  served palette.
1033- Every rendered =<pre>= and the landing page's quickstart block take
1034  keyboard focus, so a block that scrolls sideways can be reached.
1035- On one column the issue and merge request aside follows the thread
1036  instead of preceding it.
1037- The file tree at 320px keeps its last column inside the card.
1038- A path no route matches renders the 404 page instead of a plain-text
1039  body.
1040- An org image link with no description gets its file name as alt text,
1041  so a README badge is a named link.
1042- Release titles are h2.
1043- Text responses are gzipped for clients that accept it.
1044- =web theme set system|light|dark= and an Appearance section on the
1045  account page fix the colour scheme per account. Migration 0057 adds
1046  =users.theme=.
1047- A path that only misses because of a trailing slash redirects to the
1048  path without it: =/cmc/= reaches =/cmc=, =/cmc/-/snippets/= reaches
1049  =/cmc/-/snippets= (#233).
1050
1051* v1.29.0 — 2026-09-19
1052
1053The icon nav is a top bar at every width.
1054
1055- The 48px row of glyphs that narrow screens already used is now the
1056  only shell layout; the left column is gone. The row keeps the same
1057  order, labels and current-page mark, with settings, admin and the
1058  account cell at the far right.
1059- The landing picture is recaptured under the new shell.
1060
1061* v1.28.1 — 2026-09-19
1062
1063The newcomer route names its web path (#226).
1064
1065- After registering, the page and the verification mail say the code
1066  can be pasted under Settings after signing in with an emailed link,
1067  beside the terminal command.
1068- The SSH keys wiki page names this instance instead of a placeholder;
1069  the Quickstart leads with the browser route and Homebrew before
1070  =go install=.
1071
1072* v1.28.0 — 2026-09-19
1073
1074Labels on merge requests (#231), and a one-column dashboard. Migration
10750056 adds =mr_labels=; the daemon migrates on start.
1076
1077- =mr label <owner/name> <n> --add <l> --remove <l>= attaches and
1078  detaches labels the way =issue label= does, resolving an org's label
1079  first and creating a repository label on the fly; =mr list --label=
1080  filters; =mr show= carries them; the event is =mr.labeled=.
1081- The merge request page has a Labels group with the same form as an
1082  issue; list rows show label chips and =?label== filters the list.
1083- =label list= and the labels pages count merge requests beside issues;
1084  removing a label detaches it from every issue and merge request. An
1085  org label folding repository rows moves merge request rows too.
1086- The dashboard is one column: the activity feed is a section after
1087  the queues, since the icon rail leaves no wide column to balance.
1088
1089* v1.27.0 — 2026-09-19
1090
1091The follow-ups from the forge benchmark (#226) and two profile fixes.
1092
1093- On a wide repository overview the About block (counts, licence, latest
1094  release, build, contributors, languages) and the clone commands sit in
1095  a column beside the file table; under 62rem the order is unchanged
1096  (#228).
1097- The landing page's Explore and Create an account routes sit above the
1098  picture, and the picture is capped so the first screen carries a call
1099  to action (#229).
1100- Each row of the merge request list shows the combined check state of
1101  its head, linking to the diff, and a comment count (#230). Labels on
1102  merge requests do not exist yet (#231).
1103- The profile page lists repositories after the activity graph, and a
1104  table in rendered prose keeps its last row's bottom border (#225).
1105
1106* v1.26.0 — 2026-09-18
1107
1108A closed merge request can name the request that carried its change
1109(#223). Migration 0055 adds the column; the daemon migrates on start.
1110
1111- =mr close <owner/name> <n> --by <m>= records, at close time, that !m
1112  supersedes !n; =mr edit <n> --superseded-by <m>= sets it on a request
1113  already closed and =--superseded-by none= clears it. Both refuse a
1114  number that is not a request in the same repository, or the request
1115  itself. =mr show= carries the field.
1116- The web close form takes the number as an optional field. The closed
1117  request's title line says "in favour of !m"; the request it names
1118  says "supersedes !n". The state stays closed; nothing is inferred
1119  from prose.
1120- On a phone the dashboard's activity feed stacks after the queues; the
1121  aside-first rule is for checks and reviewers on a merge request
1122  (#222).
1123
1124* v1.25.0 — 2026-09-18
1125
1126The site rail is an icon column (#220).
1127
1128- At desktop the rail is a 3.5rem column of inline glyphs: dashboard,
1129  explore, search, notifications with the unread count as a badge,
1130  bookmarks, new repository, then settings and admin, then the account
1131  and sign-out. The search field leaves the rail; =/search= has its own.
1132- Under 52rem the rail is one 48px row that neither wraps nor scrolls.
1133- Every icon link carries an accessible name (=aria-label=, a title and
1134  visually hidden text) and hides its SVG from assistive tech; a test
1135  enforces it.
1136- Pinned repositories are a chip row under the dashboard heading; the
1137  review queue is the dashboard's section. Neither is in the rail.
1138
1139* v1.24.1 — 2026-09-18
1140
1141The dashboard feed and the phone-width rail strip (#222, #220).
1142
1143- Build events record their commit; the dashboard's activity feed folds
1144  a commit's jobs into one line per run with the combined state and a
1145  state dot. A status outside the known set is never shown as success.
1146- Feed times are relative, with the exact UTC time in a title, as the
1147  tree listings already do.
1148- Under 52rem the rail strip keeps the brand on its first row, shows
1149  pinned repositories as a compact labelled sub-row, and New repository
1150  is a =+= button at every width.
1151
1152* v1.24.0 — 2026-09-18
1153
1154The web follow-ups to the design foundation (#219, #220, #221, #222,
1155#224, #225), and a repository maintenance command.
1156
1157- =build list= takes =--ref=, =--status= and =--job=, pushed down to the
1158  store query; the builds page reads the same three as GET parameters
1159  with shareable links, and groups a commit's jobs into one run showing
1160  the combined state (#224).
1161- The merge request page's "Files changed" view is wide; the
1162  conversation and commits views stay at reading width (#219).
1163- The profile page lists repositories above the biography; the
1164  contribution grid carries month labels and a legend (#225).
1165- The dashboard shows populated queues first, collapses empty ones to a
1166  heading, and says what the two Open lists cover (#222, in part).
1167- Under 52rem the rail strip keeps one scrolling row and shows pinned
1168  repositories as a second row instead of hiding them (#220).
1169- Polish from the v1.23.0 review: caption spans instead of dangling
1170  labels, runner attach keeps a rejected key and reports success, the
1171  tree root of the default branch is the repository home so the header
1172  is identical within the code tab, the file editor is wide (#221).
1173- =admin mr prune <owner/name> <n>... --yes= drops the named merged or
1174  closed MRs' =refs/merge-requests/N/head= and runs =git gc --prune=now=
1175  on the repository, for commits a history rewrite left reachable only
1176  through them. Open and source-gone MRs are refused. Nothing drops a
1177  head ref on its own. =mr diff= and the MR page say when a head is gone
1178  (#227).
1179
1180* v1.23.0 — 2026-09-17
1181
1182The web design foundation (#218). Tokens measured in both schemes, one
1183control family, content widths per page, and the landing, repository
1184overview, merge request and settings pages recomposed. Set =[web]
1185title= to =gitbay= in lower case; the templates already are.
1186
1187- =style.css= rewritten on tokens defined on =:root= and again for dark;
1188  =TestTokenContrast= enforces the floors and
1189  =TestEveryTemplateClassHasARule= that every template class has a rule.
1190- Buttons are primary, secondary, quiet or destructive; one focus ring on
1191  everything; success and error flashes share one shape.
1192- Every page picks a width: wide for code, reading for lists and threads,
1193  bounded for forms.
1194- The repository header shows description and topics on the code tab
1195  only; the overview leads with the file table and puts clone commands
1196  and facts after the README; "Find file" is "Search code".
1197- A merge request states who merged or closed it under its title and
1198  explains an empty diff.
1199- Repository settings are bounded rows with a consequence beside each
1200  control, a saved flash, a rejected value kept, and topics as one field.
1201- Landing copy says what the product is and where to go; the register
1202  form says to paste the contents of the key file and links the SSH keys
1203  wiki page.
1204- The landing page shows the merge request page, light and dark,
1205  captured from gitbay.org (two embedded PNGs under =/static/img/=).
1206
1207* v1.22.1 — 2026-09-13
1208
1209One merge gate fix.
1210
1211- =require-checks= no longer refuses a merge request head that carries
1212  no statuses when nothing was going to report one: a repository with
1213  no =.gitbay/ci.yml=, or one whose jobs all wait on a schedule or a
1214  tag, had no mergeable merge request and no remedy but turning the
1215  setting off. A head whose config carries a job a push runs, and a
1216  head in a repository that has recorded a status before — which is
1217  what reporting from outside through =status set= looks like — is
1218  still refused (#216).
1219
1220* v1.22.0 — 2026-09-12
1221
1222The CLI output sweep (#183). The rules are on the wiki's Users page,
1223under "Output rules".
1224
1225- A bad invocation prints the command's registered usage, the one
1226  source of it; the hand-written copies are gone.
1227- The =gitbay= CLI pads list rows into aligned columns at a terminal
1228  and leaves the tabs alone when piped.
1229- An empty list prints nothing on stdout and =nothing to list= on
1230  stderr.
1231- Every refusal (exit 4) says what to do instead.
1232- =status list= and =repo topics= print rows.
1233- =admin runners remove=; =forget= stays as an alias until the next
1234  release.
1235- A missing positional argument prints the hint and the usage line
1236  (#215).
1237
1238* v1.21.0 — 2026-09-12
1239
1240The web UI/UX sweep (#182).
1241
1242- Destructive controls ask for the object's name typed beside the
1243  button: release delete, snippet delete and file remove, team delete,
1244  label remove, and SSH key, email and PGP key removal. Reversible
1245  controls keep a plain button.
1246- Login returns to the page that asked for it, and says so.
1247- One timestamp format everywhere, =2006-01-02 15:04 UTC=.
1248- Tags on the refs page and in the release form are in version order,
1249  newest first.
1250- The file editor explains up front when signed commits or
1251  merge-requests-only protection would refuse the commit, answers 404
1252  for a branch that does not exist, and says when a path is new.
1253- Merge refusals name the strategy rather than the flag; an issue
1254  closed by a commit reads "closed by <who> in commit <sha>".
1255- Repository settings: every Save names its field. Labels: the colour
1256  column appears only when it means something. Sidebars use one shape
1257  for empty. List rows show the state only under "all" and say "in
1258  <milestone>". Global search counts its results. A merged MR shows
1259  its merged head and a deleted source branch. The repository home
1260  shows the SSH clone URL beside HTTPS. The settings page names
1261  =auth token create=.
1262
1263* v1.20.1 — 2026-09-11
1264
1265One config check.
1266
1267- A negative =limits.max_snippets_per_user= is refused at config load,
1268  as =max_repos_per_user= and =max_bytes_per_user= already were; it
1269  used to pass validation and read as unlimited (#214).
1270
1271* v1.20.0 — 2026-09-11
1272
1273Snippets (#195): named text files a user owns outside any repository,
1274shared by URL and edited in place.
1275
1276- Migration 0054: =snippets= and =snippet_files=.
1277- =snippet create|show|list|edit|delete= and =snippet file
1278  set|get|remove=. Files are UTF-8 under =limits.max_snippet_bytes=
1279  (1MB), at most 64 per snippet; a snippet keeps at least one.
1280  =limits.max_snippets_per_user= (0, unlimited) caps how many an
1281  account may own, admins included. Visibility =public=, =unlisted=
1282  (default) or =private=; a private snippet is not found to everyone
1283  but its owner and admins.
1284- Web: =/<owner>/-/snippets= lists, each snippet page renders its
1285  files with a raw route per file, and the owner creates, edits and
1286  deletes from the page through the same commands. The owner page
1287  links to the list.
1288
1289* v1.19.0 — 2026-09-11
1290
1291Labels and milestones an org defines once for every repository under
1292it, and =Closes owner/name#N= acting across repositories (#203).
1293
1294** Org labels and milestones
1295
1296- Migration 0052: =labels= and =milestones= rows belong to a
1297  repository or to an org, exactly one, with a partial unique index
1298  per scope. Existing rows and their memberships keep their ids.
1299- A repository owned by an org sees the org's labels and milestones
1300  beside its own; =issue label --add=, =issue milestone= and =mr
1301  milestone= resolve the org's row first. A repository cannot create,
1302  recolour, remove, close or reopen a name its org holds; the refusal
1303  names the org command.
1304- =org label set|list|remove= and =org milestone
1305  create|list|close|reopen=, for org admins. Creating a name that
1306  repositories under the org already use folds them in: their issues
1307  and merge requests move to the org's row and the repository rows
1308  go. =repo transfer= into an org folds the same way. Counts on org
1309  rows span the repositories the caller can read.
1310- Web: read-only =/<org>/-/labels= and =/<org>/-/milestones=, linked
1311  from the org page; an "org" mark on repository label and milestone
1312  pages, whose forms act on repository rows only.
1313- =label list= and =milestone list= JSON carry =org: true= on an org
1314  row.
1315
1316** Cross-repository closes
1317
1318- =Closes owner/name#N= in a commit on the default branch, or in a
1319  merged merge request's title or body, closes that issue when the
1320  actor holds write on the target and the pushing key's scope allows
1321  it: a deploy key never acts outside its binding. An unknown or
1322  refused target does nothing and logs nothing; the text stays a
1323  plain autolink. An archived target is refused. Bare =owner/name#N=
1324  without a keyword stays display-only.
1325
1326** Store
1327
1328- A migration whose first line is =-- foreign_keys: off= runs on one
1329  pinned connection with foreign keys off, re-enabled afterwards and
1330  =foreign_key_check= required empty. Rebuilding a table other tables
1331  reference loses the children's rows otherwise, even under
1332  =legacy_alter_table=.
1333
1334** Behaviour changes
1335
1336- =milestone create= exits 1 on a duplicate title, as =org milestone
1337  create= does; it exited 2 before.
1338
1339Upgrade: replace the binary and restart; migration 0052 runs on
1340start and copies every label and milestone row once.
1341
1342* v1.18.1 — 2026-09-11
1343
1344A runner that cannot hang on a dead connection, SSH keys with names,
1345and dependency updates.
1346
1347** CI runner
1348
1349- Every ssh invocation carries =ConnectTimeout=10=,
1350  =ServerAliveInterval=15= and =ServerAliveCountMax=3=, placed after
1351  the identity and the operator's =-ssh-opts= so an operator's value
1352  wins. A claim whose TCP session had died under it blocked a laptop
1353  runner's poll loop for thirteen hours; it now fails within a minute
1354  and the loop resumes.
1355- The build comment in =deploy/Containerfile.ci= stages the file in
1356  the runner user's home before =podman build=: a login shell under
1357  =su= cannot read root's stdin and does not share root's =/tmp=.
1358
1359** Keys
1360
1361- SSH keys carry a label (migration 0051). =keys add --label= defaults
1362  to the authorized_keys comment; =keys label <fingerprint> [<text>]=
1363  renames or clears it. =keys list=, =admin user show=, =repo
1364  deploy-key list= and the settings page show it. Deploy, runner and
1365  admin-created keys take the comment as their label. Closes #208.
1366
1367** Web
1368
1369- Org autolinks stop before trailing punctuation: a bare URL closing a
1370  sentence or a parenthesis no longer takes the =.=, =,= or =)= into
1371  the href. Closes #209.
1372
1373** Dependencies
1374
1375- golang.org/x/crypto 0.57, x/image 0.46, x/net 0.59, x/term 0.46.
1376  Closes #205.
1377
1378* v1.18.0 — 2026-09-10
1379
1380What the first real job on a user's runner needed. A twice-daily
1381archive pull that had run on the server's host moved into a container
1382and then onto a laptop, and each hop found a gap.
1383
1384** CI runner
1385
1386- A secret with newlines — a private key — reaches the build. An env
1387  file has no escape for one, so such values are named on podman's
1388  command line with =--env NAME= and valued in the podman process's own
1389  environment; the value touches neither argv nor the file.
1390- =GITBAY_SSH= in every build's environment: the instance's ssh
1391  destination as the build reaches it. Under podman the host's own
1392  addresses belong to the container (pasta), so a loopback remote is
1393  rewritten to the address pasta exposes the host at. A job that
1394  publishes back to the instance uses the variable rather than
1395  guessing. Inside a container =ssh= expands =~= from the passwd entry,
1396  not =$HOME=; keep a build's ssh config in the workspace and pass =-F=.
1397- =-identity= drops the user's =~/.ssh/config= (=-F /dev/null=):
1398  =IdentitiesOnly= kept identities the config named, so a laptop runner
1399  authenticated as the user's own full-scope key and, on an admin's
1400  machine, could claim every repository's builds. A first-seen host key
1401  is accepted, since a service cannot answer a prompt.
1402- A schedule tick queues nothing while the job's last build is pending
1403  or running, matching the push path. A repository no runner served
1404  gained one row per tick forever. A finished build does not suppress
1405  the tick; a schedule re-runs an unchanged commit on purpose. #206
1406- =admin runners forget <fingerprint>= drops a key's heartbeat row; the
1407  key stays. =admin runners= rows are the repositories a key may claim.
1408- The bay1 unit names no =-repos=: the runner key's attachments are the
1409  boundary. =gitbay-ci:2= carries =python3-venv= and =sqlite3=, since
1410  it is also the default image for every repository the runner is
1411  attached to.
1412
1413** Decisions
1414
1415- Claim order stays oldest-first across everything a key may claim; a
1416  repository that must never wait on another gets a runner of its own.
1417  #207
1418- No per-account cap on queued builds and no schedule floor: with the
1419  tick dedupe a repository with no runner holds one row per scheduled
1420  job, and a busy schedule spends its owner's compute. #206
1421- Attaching a runner is =n/a= on iOS: the key lives on the machine that
1422  runs builds.
1423
1424** Documentation
1425
1426- Users: =GITBAY_SSH=, ssh's home inside a container, the =ci.yml= caps
1427  (ten jobs, fifty steps, 4096 bytes a step, 64 KiB a file) and where a
1428  broken config shows up. Admin, CI and Threat-Model follow the changes
1429  above.
1430
1431** Upgrading
1432
1433Replace the binaries and reinstall the CLI. No migration. A runner
1434started with =-identity= (every runner =gitbay-runner init= set up) now
1435ignores =~/.ssh/config=; a runner that relied on it for a =ProxyJump=
1436or an alias passes the equivalent in =-ssh-opts=. Homebrew:
1437=brew upgrade krz/tap/gitbay-runner=.
1438
1439* v1.17.0 — 2026-09-09
1440
1441CI without the operator's compute: a runner anyone installs and
1442attaches to their own repositories, and the server rule that makes
1443that safe. The rest of the #184 list besides.
1444
1445** CI
1446
1447- A runner key claims builds only for the repositories it is attached
1448  to. =repo runner add <owner/name> < key.pub= attaches one; a key the
1449  server has not seen lands on the caller's account with scope
1450  =runner=. =repo runner list= shows each attached key with its last
1451  poll and the build it holds; =repo runner remove <fingerprint>=
1452  detaches it. All three on the settings page. A runner-scoped key
1453  with nothing attached claims nothing, whoever owns it; a full-scope
1454  admin key still claims any repository. =runner log= and =runner
1455  done= refuse a build outside the key's attachments. #184
1456- Closed: any account could add a runner-scoped key, and =runner next=
1457  with no arguments handed it the oldest pending build on the
1458  instance, secrets included.
1459- =runner next --untrusted=: without it a merge request head from a
1460  fork is never claimed. The runner passes it when started with
1461  =-untrusted=; the bay1 unit does, because it isolates in podman.
1462- =gitbay-runner init= generates a key under =~/.config/gitbay-runner/=,
1463  writes =config.toml= beside it, and prints the public key with the
1464  command that attaches it. The runner reads that file when present
1465  and flags override it. =-identity=, defaulting to the generated key,
1466  makes ssh and git use the runner's own key and no other. Homebrew:
1467  =brew install krz/tap/gitbay-runner=, then =brew services start
1468  krz/tap/gitbay-runner=. Releases ship =gitbay-runner= binaries.
1469- =admin runners= heads its output with the queue: builds pending now,
1470  and over the last day the builds claimed, the wait to claim (average
1471  and worst) and the builds the reaper ended instead of a runner
1472  reporting them. Rows are per key, with the fingerprint and the
1473  repositories the key may claim. Migration 0049. #184
1474- Stop tests for the runner's drain: a signal mid-step, the drop-in's
1475  =KillMode= and =TimeoutStopSec=, and a transient systemd user unit
1476  where one exists. #179
1477- The CI wiki page carries every push shape against every job kind and
1478  what dedupe, path filters, schedules and the reaper make of it, with
1479  a test per row. #176, #177
1480
1481** Importing
1482
1483- =import-issues --api-base= reads Forgejo instances: paging by =limit=,
1484  oldest first, comments read once, attribution and pull heads taken
1485  from the API base rather than github.com. #191
1486
1487** Documentation
1488
1489- Users: "Your own runner". Admin, Threat-Model, CI, FAQ and Parity
1490  follow the attachment rule.
1491
1492** Upgrading
1493
1494Replace the binaries and reinstall the CLI. Migration 0050 (runner
1495attachments; the runner heartbeat table is rekeyed by key and
1496emptied), applied on start. One behaviour change: a runner polling
1497with a key of scope =runner= claims nothing until a repository admin
1498attaches it with =repo runner add=. Do that right after the restart.
1499A full-scope admin key is unaffected. Merge request heads from forks
1500are built only by a runner started with =-untrusted=.
1501
1502* v1.16.0 — 2026-09-08
1503
1504What stops a stranger from moving here: the repository plumbing and
1505the team gates the #185 walk found missing, twelve merge requests
1506merged as one stack.
1507
1508** Repositories
1509
1510- =repo settings default-branch <owner/name> <branch>= moves HEAD and
1511  the record; a branch that does not exist is refused. A first push of
1512  =master= or =trunk= into a fresh repository moves the unborn HEAD to
1513  the branch that arrived, so the clone checks something out. Settings
1514  page select. #189
1515- =repo rename <owner/name> <new-name>=: the row and the directory move
1516  together, with transfer's revert on a failed move. Clone URLs change.
1517  #190
1518- =repo settings require-mr on=: an existing protected branch refuses
1519  every direct push in pre-receive, =repo commit-file= and the web
1520  editor included; =mr merge= is its only writer. Creating the branch
1521  is still a push. #197
1522- =repo settings protect-tag <glob>= (and =unprotect-tag=): matching
1523  tags are created once and refuse moves and deletion. Separately, a
1524  tag a release is anchored to refuses both while the release exists,
1525  protected or not; delete the release first. #201
1526- =repo access list= reports effective access: one row per account
1527  with the highest role and where it comes from (owner, direct, org
1528  admin, org member, team). It used to list direct grants only, so a
1529  repository reached through teams answered with nothing. #200
1530- Removing an org member drops their team memberships in the same
1531  transaction. They kept every grant their teams carried, and re-adding
1532  them to the org restored nothing because nothing had gone. #196
1533- An outsider gets one answer about an org: its existence and members
1534  are public, its teams are for members, and =org team list= and =show=
1535  refuse a non-member rather than say the org does not exist. Ref #200
1536- A repository name may not end in =.atom=, as it may not end in
1537  =.git=. Ref #192
1538
1539** Merge requests
1540
1541- A push that leaves the merge request's diff unchanged keeps its fresh
1542  reviews: the patch-id of each revision against its own merge base is
1543  compared, and a rebase onto a target that moved on no longer stales
1544  every approval. A push that changes the diff stales them as before.
1545  #198
1546- The merge gates are one computation shared by =mr show= (a =gates=
1547  block: approvals counted and required, owners outstanding per file,
1548  open threads, checks, whether a fast-forward is possible), the merge
1549  request page, and =mr merge=, which names every unmet gate in one
1550  refusal rather than the first. =mr review= reports =counts= and says
1551  when a verdict is advisory because the reviewer cannot write. #199
1552
1553** Notifications
1554
1555- =@name= in an issue, merge request, comment or diff comment files
1556  "mentioned you" in that account's inbox and makes them a participant
1557  of the thread, provided they can read the repository and have not
1558  muted it. Watchers are not told about a mention addressed to someone
1559  else. Migration 0047. #202
1560- =notifications settings mail on|off= (and =show=): inbox rows are
1561  filed either way, this is the mail half. Login links are not activity
1562  and still arrive. The account page carries the same switch.
1563  Migration 0048. Ref #194
1564
1565** Web
1566
1567- Atom feeds: =/{owner}/{repo}/releases.atom=,
1568  =/{owner}/{repo}/log.atom[/{ref}]= and =/{owner}/activity.atom=,
1569  rendered over the rows the pages already serve. The owner feed covers
1570  public repositories only, since a reader carries no session; a
1571  private repository answers 404. The releases, log and owner pages
1572  carry the discovery link. #192
1573
1574** Documentation
1575
1576- The Users page says what differs over stock ssh: a multi-word value
1577  needs a second layer of quotes, and =help <noun>= replaces =--help=.
1578  The companion-wiki paragraph #170 made stale now points at
1579  =.gitbay/wiki/=. #204
1580
1581** Upgrading
1582
1583Replace the binary and reinstall the CLI. Two migrations (0047, the
1584mentions table; 0048, the per-account mail switch), applied on start.
1585Nothing changes behaviour until a setting is turned on: =require-mr=,
1586=protect-tag= and =mail off= are all opt-in.
1587
1588* v1.15.0 — 2026-09-07
1589
1590Builds run in containers, a rebase is not rebuilt, and a runner restart
1591no longer strands the build it was running.
1592
1593** CI
1594
1595- A build's steps run in a rootless podman container, one per job. The
1596  runner clones outside the container with its key and bind-mounts the
1597  workspace in, so a step cannot reach the key, the runner's environment,
1598  or another build's workspace. =image:= is required per job and is
1599  validated as a reference, never pulled: an operator provisions images
1600  on the host. A runner configured for podman that has none refuses to
1601  start rather than fall back to the host. =-isolation none= is the
1602  explicit host-execution mode. =-cpus= and =-memory= cap a build's
1603  container. #144
1604- Builds have a home directory that outlives the build, so the Go module
1605  cache and the sonar scanner survive between runs. It is mounted into
1606  the container at the same path, and only that directory. Ref #144
1607- The host preparation script, the unit drop-in and the weekly image
1608  prune ship with =make deploy-runner=; each hardening flag the drop-in
1609  relaxes carries the reason in place. Ref #144
1610- A nightly canary on the runner host proves the boundary holds:
1611  =cmc/ci-smoke= runs a job that tries to read the key and list sibling
1612  workspaces, and fails if either succeeds. Ref #144
1613- Dedupe keys on the commit's tree, not its sha. A rebase that changes
1614  nothing is not rebuilt: the new commit gets the earlier success as its
1615  status, naming the build. Scheduled and tag builds carry no tree and
1616  are never reused. #177
1617- =vuln= and =sonar= run nightly on =main= rather than on every push;
1618  neither could inform a merge. Branches run =build= and =test=. #177
1619- A rewritten branch is filtered against the merge base rather than the
1620  old tip, so a rebased branch whose own commits change code no longer
1621  reads as a docs-only push and skips its jobs. #176
1622- A build whose runner's log stream ended with no outcome is failed two
1623  minutes later, instead of sitting =running= until a fixed deadline.
1624  Migration 0046. Ref #179
1625- The runner retries reporting a finished build's outcome, four times
1626  over about thirty seconds, when the server is unreachable. A gitbayd
1627  restart at that moment used to lose the result. Ref #179
1628- The runner drains on SIGTERM: it claims nothing more, finishes and
1629  reports the build in flight, then exits. A second signal exits at once.
1630  The unit allows fifty minutes. #179
1631
1632** Repositories
1633
1634- =repo show= reports the caller's watch and bookmark state, and the
1635  parent of a fork when the caller can read it. #178
1636- =repo unwatch= clears the row from either state; =repo mute= is the
1637  explicit silence. Watch then unwatch used to leave an account below
1638  the default with no way back. The web header toggle follows. #180
1639
1640** Upgrading
1641
1642Replace the binary and reinstall the CLI. One migration (0046, the
1643build log's close time), applied on start.
1644
1645The runner now defaults to =-isolation podman= and refuses to start
1646without a working podman and a named image. Prepare the host with
1647=deploy/runner-podman-setup.sh= and build =localhost/gitbay-ci:1= from
1648=deploy/Containerfile.ci= before deploying it, or pass =-isolation
1649none= to keep running steps on the host. Validate on a scratch
1650repository with =-repos= scoped to it first; the wiki's Admin page has
1651the procedure.
1652
1653The runner's unit gains =TimeoutStopSec=50min= and =KillMode=mixed= so
1654a stop reaches the runner alone and it can drain; under the default
1655kill mode systemd ends the build's container with the runner.
1656=make deploy-runner= therefore waits for a build in flight.
1657
1658* v1.14.0 — 2026-09-06
1659
1660Logging into the web without an SSH key, wikis inside the repository,
1661CI that skips what a change does not touch, and the browser catching up
1662with the command line on nine capabilities.
1663
1664** Accounts and the web
1665
1666- A browser session can be requested by mail: the login page takes a
1667  username or a verified address and sends a link that works once and
1668  expires in fifteen minutes. An account with no SSH key had no way into
1669  the web at all. The response never says whether the account exists, and
1670  the form appears only when the instance has SMTP. #155
1671- A login link resolves to any verified address on the account, not only
1672  the primary. #158
1673- Login mail is queued rather than sent from a goroutine, so a link in
1674  flight survives a restart. #159
1675- A suspended account cannot mail itself a session, and a link minted
1676  before suspension opens nothing. #156
1677- The session cookie is =SameSite=Lax=, and a test now walks every
1678  mutating route to assert it carries the origin check. #157
1679- =POST /register= is reachable on an open instance again.
1680
1681** Wikis
1682
1683- A wiki lives at =.gitbay/wiki/= on the default branch, so editing one
1684  is editing a file in the repository — a push, or the web editor — and
1685  it is cloned, diffed and reviewed like anything else. The companion
1686  =<repo>.wiki= is gone. #170
1687
1688** CI
1689
1690- Path filters: =paths= and =paths-ignore= per job, so a docs commit
1691  does not run the whole suite. #169
1692- A branch's first push derives its diff base from the merge base
1693  rather than treating every file as changed. #171
1694- A job filtered out records a skipped status instead of nothing, so
1695  =require_checks= cannot wait forever for a check that will never
1696  arrive. #172
1697- A force-push no longer leaves queued builds pointing at an object
1698  that is gone; the orphan is cancelled when a runner claims it. #152
1699- A build step's environment is constructed rather than inherited. It
1700  was =os.Environ()= plus the build's variables, which handed repository
1701  content everything set on the runner service. A step now gets =PATH=,
1702  =HOME=, =LANG=, =CI=, its =GITBAY_*= variables and its secrets. =HOME=
1703  is the workspace, so a build cannot read the runner's =.netrc=,
1704  =.npmrc= or =.gitconfig=, where tools keep credentials. Ref #144
1705- A runner host can be prepared for rootless podman:
1706  =deploy/runner-podman-setup.sh=, the systemd changes it needs, and
1707  weekly image pruning. Nothing reads them yet; the preparation ships
1708  before the runner that requires it, on purpose. Ref #144
1709
1710** Collaboration
1711
1712- =mr review request --add <user>= asks a particular person for a
1713  review, who then carries it in their queue and is notified;
1714  =--remove= withdraws the ask. The queue was computed from involvement
1715  alone, so a collaborator who had not touched a thread heard nothing.
1716  #145
1717- Bookmarks save someone else's repository to come back to, and the
1718  count is the instance's only popularity signal. Separate from pins
1719  rather than a flag on them: a pin is private quick access to your own
1720  work and drives the rail, a bookmark is public and counted. =repo
1721  bookmark=, =repo unbookmark=, =repo bookmarks=, a control on the
1722  repository header, the count in the facts bar, and =/bookmarks=. Read
1723  access is all a bookmark needs, and one made while a repository was
1724  public drops out of the listing if it goes private. #146
1725
1726** The browser catches up
1727
1728Nine capabilities that were CLI-only and had no reason to be:
1729
1730- label management — list, create, colour, remove #163
1731- dependency status under the toggle that turns checks on #164
1732- release delete #165
1733- the account export bundle, as a download #166
1734- organization create and rename; delete stays CLI-only, wanting a
1735  typed confirmation, and the page says so #167
1736- opening a merge request from a fork, with a source picker offering
1737  the branches of every fork you can push to #168
1738- forking a repository #174
1739- cancelling a queued or running build #162
1740- the profile form #161, and a markup picker on issue and merge
1741  request create #160
1742- admin table headers align with their columns #151
1743
1744** CLI
1745
1746- =gitbay mr rebase <n>= replays a merge request's branch onto its
1747  target and re-pushes it. A repository requiring signed commits accepts
1748  only fast-forward merges, so a merge request whose target moved had to
1749  be rebased by hand; the refusal already named the procedure and this
1750  runs it. The git work is local, so the replayed commits carry your
1751  signature — the server still holds no key. A branch in a fork is
1752  refused, naming the repository to run it in. #175
1753
1754** Security
1755
1756- Mutating commands are bounded per account in the dispatcher, so SSH,
1757  the JSON API and the web spend one budget and a caller cannot refresh
1758  it by changing surface. Authentication failures were throttled;
1759  commands were not. #148
1760- A dead-lettered mail is logged by its queue row id, not the recipient
1761  address, and the relay's error is redacted before logging because a
1762  rejection quotes the address it rejected. The address stays on the
1763  row, where =/admin= shows it. One rule for every mail type. #173
1764- The 2026-09 sweep's coverage — and what it did not reach — is recorded
1765  in the wiki's Threat-Model rather than in a closed issue. #149
1766
1767** Dependencies
1768
1769- goldmark 1.8.6, sqlite 1.58.0. #140
1770
1771** Upgrading
1772
1773Replace the binary and reinstall the CLI. One migration (0043,
1774bookmarks), applied on start.
1775
1776=limits.write_rate= defaults to 60 mutating commands a minute per
1777account. A script that writes faster will be refused with exit 4 and a
1778retry time; raise it in =[limits]=, or slow the script. Read-only
1779commands, the runner protocol and the host CLI are not counted.
1780
1781A companion =<repo>.wiki= repository is no longer read. Move its pages
1782to =.gitbay/wiki/= on the default branch.
1783
1784Runner isolation is half done. Builds still run as the runner's user
1785with no container: the step environment no longer leaks the service's,
1786and a host can be prepared for podman, but nothing yet executes a build
1787in one. Do not enable CI for repositories you do not trust. #144 stays
1788open for the execution half.
1789
1790* v1.13.3 — 2026-09-05
1791
1792Only a writer's review decides a merge gate, and a scan of one branch
1793stops overwriting another's results.
1794
1795- =mr review= resolves with =CanRead= and applied no further check, and
1796  the merge gates counted every fresh verdict. On a public repository
1797  that let anyone with an account satisfy =require_approvals= — defeating
1798  four-eyes review by holding two accounts, which on an instance with
1799  open registration means defeating it outright — and equally let a
1800  passer-by block a merge the owner wanted, with no override and only a
1801  force-push to clear it. Both were confirmed against a running instance.
1802  Reviewing stays open to every reader, because an outside opinion on a
1803  public change is worth having; it no longer decides the gate. What
1804  does is write access, the same question the gates already answer. An
1805  uncounted review is marked advisory by =mr show= and by the merge
1806  request page, both reading the same rule, so the page cannot show an
1807  approval the gate ignores. #147
1808- The two =git upload-pack= spawns behind the smart HTTP transport now
1809  resolve git at start-up like everything else. The v1.13.2 rewrite
1810  matched a plain identifier for the context and these pass
1811  =r.Context()=, so it skipped them. #153
1812- CI analyses each branch as itself. Every scan was recorded against the
1813  project's main branch whatever branch produced it, so a feature branch
1814  replaced main's results — a branch that removes findings made main look
1815  clean before the fix merged, and one that added them made main look
1816  broken when it was not. #154
1817
1818Replace the binary and reinstall the CLI. No migration.
1819
1820A repository relying on approvals from accounts without write access
1821will find those merges now refused. That was the defect: such an approval
1822never meant the repository accepted the change. Grant write, or name the
1823reviewer in CODEOWNERS and grant write, if their approval is meant to
1824count.
1825
1826* v1.13.2 — 2026-09-04
1827
1828The first SonarCloud scan's findings: eight fixed, the rest triaged and
1829dismissed with reasons.
1830
1831- A pages directory redirect could leave the site. Both redirects passed
1832  the raw request path to =http.Redirect= while the cleaned path sat a
1833  line above; =net/url= keeps a leading =//=, and Go emits
1834  =Location: //evil.example/= unchanged, which a browser reads as
1835  protocol-relative. Reaching it needed a public repository named like a
1836  host under the subdomain's own owner — repository names permit dots —
1837  so it was narrow rather than impossible. The destination is built from
1838  the cleaned path through =url.URL= now, which also settles the two
1839  spellings the first fix missed: a =..= that escapes to the root, and a
1840  backslash, which browsers following the WHATWG rules treat as a
1841  separator. #153
1842- The runner's default workspace was =<tmp>/gitbay-runner=: a fixed name
1843  in a world-writable directory, created with =MkdirAll=, which succeeds
1844  against a directory whoever already owns it. bay1 was never exposed —
1845  its unit names a workspace — but the default is what anyone running the
1846  binary by hand gets, and this is the process that clones repositories
1847  and exports build secrets. The default moves under the user's cache
1848  directory, the workspace is created 0700, and a symlink or a directory
1849  owned by someone else is refused. One we own that is merely too
1850  permissive is tightened rather than refused, since every runner before
1851  this one made it 0755 and refusing would take the runner down on
1852  upgrade. #153
1853- Logout and flash consumption expire their cookies with the attributes
1854  the setting calls used. Deletion worked either way; the difference was
1855  a reviewer's puzzle, and four findings. #153
1856- The topics-remove field has a label. A placeholder is not an accessible
1857  name. TestEveryInputHasAnAccessibleName is the guard that was missing,
1858  and it knows both associations — six inputs use
1859  =<label>Name <input></label>=, which is as good as for/id. #153
1860- git and ssh are resolved once at start-up rather than searched on every
1861  spawn, and gitbayd refuses to start when one is absent instead of
1862  failing on whichever request first needed it. This was 74 of the 118
1863  findings; a dashboard that is mostly permanent noise is one nobody
1864  reads. #153
1865
1866Also: SQLite migrations are excluded from analysis. They were read as
1867PL/SQL, where ='' is NULL=, so =WHERE col = ''= on a =NOT NULL DEFAULT ''=
1868column — correct SQLite, and the shape used throughout — read as a
1869null-comparison bug.
1870
1871Replace the binary and reinstall the CLI. No migration. A runner whose
1872workspace is group- or world-readable will have it tightened to 0700 on
1873next start, and will refuse to start if that workspace is a symlink or
1874belongs to another user.
1875
1876* v1.13.1 — 2026-09-04
1877
1878A command that reads its payload from stdin says so, and SonarCloud runs
1879alongside the vulnerability scan.
1880
1881- =repo secret set= blocked with nothing printed, which is
1882  indistinguishable from a hung connection, and pressing Enter did not
1883  end it because the server reads to EOF — so it looked the same before
1884  and after the value had been typed, and the secret echoed into the
1885  scrollback on the way. A terminal is now told what is wanted and that
1886  Ctrl-D ends it; a secret is read without echo and takes one line, so
1887  Enter is enough. Piped input is unchanged, byte for byte: =printf %s
1888  "$TOKEN" | gitbay repo secret set ...= still sends exactly the token.
1889  Applies to =keys add=, =auth pgp add=, =repo deploy-key add= and
1890  =release asset add= as well; public keys keep echoing, since they are
1891  public. #150
1892- A =sonar= CI job reports to SonarCloud, alongside =vuln=. Report-only:
1893  it does not gate a build, unlike the vulnerability scan. A merge
1894  request from a fork builds without secrets by design, so the job says
1895  why it is skipping there rather than failing on a missing credential.
1896  Only =SONAR_TOKEN= is secret and it is a build secret; the
1897  organization, project key and host are checked in. Ref #149
1898
1899Replace the binary and reinstall the CLI. No migration.
1900
1901* v1.13.0 — 2026-09-04
1902
1903Collaboration. A review is composed and submitted as one thing, a merge
1904request can say it is not asking yet and can show what changed since you
1905last looked, issues are searched by their text, and the events half the
1906mutations never recorded now exist.
1907
1908- A review is composed as a unit. =mr diff-comment --pending= holds a
1909  comment back; =mr review= publishes the batch with the verdict and says
1910  how many went with it; =mr review --discard= throws away what was never
1911  submitted. A pending comment notifies nobody when written — the review
1912  is the announcement, and it names its own size — and does not gate a
1913  merge, since a thread only its author can see is one nobody else could
1914  resolve. #111
1915- =mr create --draft=, =mr draft=, =mr ready=. A draft does not merge and
1916  does not appear in anyone's review queue; marking it ready is the
1917  request for review. Draft is a flag rather than a fifth state, so every
1918  =state = 'open'= rule still means what it did, and the merge refusal is
1919  unconditional: every other gate is a setting an admin turns on, and
1920  this one is the author's own statement about their own work. #111
1921- =mr range-diff= shows what changed between two revisions of a merge
1922  request, and =mr revisions= lists them. A push stales every review and
1923  nothing said what had moved; a diff of the two heads cannot answer it,
1924  and the previous head was overwritten in place. Each side of the
1925  comparison carries the merge base it had at the time, since measuring
1926  both against today's would attribute every commit that landed on the
1927  target in between to this merge request's author. #111
1928- Issues and merge requests are searched by their title and body, over
1929  FTS5. =issue list --search= and =mr list --search= narrow one
1930  repository; the instance-wide =search= reaches bodies now, and both
1931  list pages carry a search box. What someone types is quoted term by
1932  term, so an FTS5 operator — =c++=, =AND=, a lone quote — is a word to
1933  match rather than a syntax error. #114
1934- Ten mutations that changed a repository silently now record an event:
1935  =mr.closed=, =mr.reviewed=, =mr.edited=, =mr.retargeted=, =mr.draft=,
1936  =issue.edited=, =issue.labeled=, =issue.assigned=, =issue.milestoned=,
1937  =mr.milestoned=, =release.deleted=. =mr close= and =issue edit= also
1938  notify participants, which they did not. The full list is on the API
1939  wiki page and =webhook add --events= refuses a name that is not on it,
1940  since a subscription to a typo would never fire and nothing would say
1941  so. #112
1942- =gitbay-runner -jobs N= runs N builds at once. Claiming was always a
1943  single transaction that selects and updates, and each build already
1944  worked in its own directory, so several workers were safe the whole
1945  time; the runner never used more than one. #115
1946- A merge request replayed from a migration bundle has a diff. The bundle
1947  carried no head at all, and =mr diff= resolves through the head ref, so
1948  a merged merge request — which has no source branch left — could only
1949  fail. Re-running an import after the git push sets the head it could
1950  not set the first time. The GitHub import fetches =refs/pull/*/head=,
1951  which a mirror made with the default refspecs does not carry. #128
1952- The review loop is driven end to end by three accounts in the test
1953  suite: draft, ready, thread, approval, resolve, merge, with approvals,
1954  CODEOWNERS and require-resolved all on at once. Every one of those had
1955  its own test and none of them met. #139
1956- A bare =go test ./...= says the timeout is too short instead of
1957  panicking eleven minutes in and blaming whichever test was running.
1958  =make test= is what CONTRIBUTING asks for now. #143
1959
1960Migrations 0036 through 0039 add the search index, the draft flag,
1961pending review comments and merge request head history; 0036 and 0039
1962backfill from what is already there. They run on daemon start.
1963
1964Two things this does not do. There is still no way to ask a particular
1965person for a review — the queue is computed from involvement, so a
1966collaborator with write access who has not touched a thread hears nothing
1967(krz/gitbay#145). And a CI build still runs as the runner's own user with
1968no container; the runner on this instance is scoped to one repository,
1969which is what keeps that narrow (krz/gitbay#144). Both are v1.14.0.
1970
1971* v1.12.0 — 2026-09-04
1972
1973The store and the push path. Dashboard queries walk an index instead of
1974sorting the table, concurrent writers wait instead of failing, expired
1975rows are swept, and a large first push no longer forks a process per
1976commit.
1977
1978- Every dashboard list scanned its table and sorted the result to take
1979  fifty rows. Reachability is correlated subqueries and cannot be
1980  indexed; the index supplies the =ORDER BY= instead, so the walk stops
1981  at =LIMIT=. On 20k issues and 20k merge requests: open issues 11.8ms
1982  to 0.8ms, open merge requests 12.1ms to 0.8ms, the review queue 15.5ms
1983  to 0.3ms, assigned issues 10.6ms to 0.04ms. The last of those also
1984  drives from =issue_assignees= rather than testing =EXISTS= against
1985  every issue. #137
1986- Concurrent writers serialise rather than failing. Every transaction in
1987  the store writes, and a deferred one takes the write lock at its first
1988  write, by which point another may hold it; SQLite answers
1989  =SQLITE_BUSY= and does not run the busy handler for that case, so
1990  =busy_timeout= could not help. Measured with eight concurrent
1991  read-then-write transactions, 44% of them failed. Beginning immediate
1992  takes the lock up front, where the timeout applies. #121
1993- =repo settings= updates no longer overwrite each other.
1994  =settings_json= is one blob, and every caller read it off a repository
1995  loaded earlier, changed a field and wrote it all back; two admins at
1996  once and the later write put back what it had read for the other's
1997  field. The read and the write happen together now, under one
1998  immediate transaction. #123
1999- Expired sessions and tokens are swept, and =[retention]= caps how long
2000  the audit log, the activity feed, webhook deliveries and the mail
2001  queue keep a row. Unset means forever, which is what every existing
2002  instance gets. #122
2003- The audit entry records flag names without their values. Secrets never
2004  reached argv — they travel on stdin — but prose did: =--body <the
2005  whole issue>= was stored verbatim, in a table nothing pruned, for a
2006  repository that may be private. Identifiers are positional and
2007  survive. #122
2008- pre-receive on a require-signed repository forked a =cat-file= per
2009  incoming commit and built one JSON message holding the whole push. A
2010  50k-commit first push forked 50k processes and held the history in
2011  memory twice. One =cat-file --batch= serves the push now, and the
2012  daemon verifies each commit as it arrives. #100
2013- The payloads other surfaces decode are named types in =control=. httpd
2014  had its own copies of what the build, profile and dashboard commands
2015  emit, so a field added to a command was silently absent on the page.
2016  #126
2017
2018Migration 0035 adds three indexes; it runs on daemon start.
2019
2020Two changes in behaviour rather than configuration. A heavily contended
2021write now blocks for up to =busy_timeout= (five seconds) instead of
2022returning an error immediately — waiting is the point, but a caller that
2023treated the error as normal will see a pause instead. And anything
2024parsing =audit --json= for command arguments will find flag values gone;
2025the flag names and the positional arguments are still there.
2026
2027* v1.11.0 — 2026-09-04
2028
2029The web catches up with the rest of the forge: search across the
2030instance, a notification inbox, a compare view, linkable diff lines,
2031and a pass over contrast, heading structure and the stylesheet.
2032
2033- Notifications are no longer mail or nothing. An =inbox= table holds a
2034  row per recipient whether or not the instance has SMTP;
2035  =notifications list= reads it, unread by default, and =notifications
2036  read <id>... | --all= clears it. =repo watch= adds you to a
2037  repository's notifications and =repo unwatch= mutes it, with a mute
2038  beating every other reason to be told, including owning the
2039  repository or having written the thread. The unread count rides on
2040  =dashboard= and in the web rail. #113
2041- =search= matches repository paths, descriptions and topics, and issue
2042  and merge request titles, across everything the caller can read;
2043  =/search= renders it with a field in the rail on every page, and an
2044  anonymous visitor gets the public rows from the same query. Titles
2045  only — body search is #114. #118
2046- =/{owner}/{repo}/compare/{a}...{b}= shows what one ref adds on top of
2047  another. Diff rows, files and review threads carry ids, so a line can
2048  be linked to. The issue and merge request lists page at fifty with
2049  the cursors the commands already emit. #118
2050- CODEOWNERS gating is a setting rather than a file that happens to
2051  exist: =repo settings require-codeowners <owner/name> on|off=, off by
2052  default, still independent of =require-approvals=. A repository can
2053  carry the file as documentation of who to ask without it gating
2054  merges. #142
2055- A failed form action's reason rides a one-shot cookie instead of
2056  =?e=<message>=, so it no longer survives a reload or lands in
2057  history. #119
2058- A diff cut at 4 MiB cuts on a line boundary and says so, the
2059  diffstat says its counts are partial, and a merge request's commit
2060  list says "first 100 of N". #117
2061- Page templates parse once with the layout at start-up, so a template
2062  that does not parse fails the process rather than the first visit to
2063  its page. #116
2064- Markdown headings carry ids, matching org pages, and the stylesheet
2065  serves a hash ETag with a day's lifetime and answers a matching
2066  =If-None-Match= with 304. #132
2067- Dark-mode buttons carry a visible edge (a 1 px border was 1.3:1
2068  against the 3:1 non-text contrast floor), and a stored label colour
2069  is held between 0.12 and 0.28 relative luminance so it clears 3:1 on
2070  both grounds while keeping its hue. #120
2071- Accessibility: the pin star is decoration and the word carries the
2072  meaning, the refs and release asset tables have scoped column
2073  headers, state filters carry =aria-current= rather than marking the
2074  active one by colour alone, and a rendered README or wiki page's
2075  headings move down one level so they sit under the page's own. #133
2076- The stylesheet drops rules no template reaches, folds two off-scale
2077  values onto the type scale, and resolves the classes templates asked
2078  for and it never defined. #131
2079- On a phone the tab bar wraps to a second row instead of scrolling
2080  sideways with its scrollbar hidden, and the landing page says in
2081  three sections what a reader, a writer and a reviewer can do. #134
2082
2083Migration 0034 adds =inbox= and =repo_watchers=; it runs on daemon
2084start. Reinstall the CLI for =search=, =notifications= and =repo
2085watch/unwatch=.
2086
2087Two upgrade notes beyond replacing the binary. A repository that
2088relied on a CODEOWNERS file gating merges by its presence alone loses
2089that gate until =require-codeowners= is set: nothing back-fills it,
2090since the database cannot say which branches carry the file. And
2091=search= and =notifications= are now reserved top-level routes, so a
2092user or organization already holding either name keeps it but its
2093profile page is shadowed by the route.
2094
2095* v1.10.0 — 2026-09-04
2096
2097Every command parses its arguments the same way, the web answers by
2098exit code, and a restart no longer waits on idle connections.
2099
2100- One flag parser for every command: an unknown flag, a missing value or
2101  too many arguments is exit 2 with the command's usage, everywhere.
2102  =mr review --approve --bogus= used to report repository =--bogus= as
2103  not found. #96
2104- =--json= is honoured by the dispatcher's own refusals, so a script told
2105  no gets the envelope. #109
2106- A store failure is exit 1 and not-found is exit 3; both used to be
2107  usage errors. #107
2108- Web form actions answer by exit code: the 404 page for a thing that
2109  does not exist, the page with the message for anything else. #106
2110- Inside a clone, =gitbay mr create= takes the checked-out branch as
2111  =--source=; =gitbay <noun> --help= is the server's reference for the
2112  noun, flags included. #101 #130
2113- Shutdown closes idle SSH connections at once and drains only sessions
2114  mid-command; a store failure during key lookup no longer counts as a
2115  bad key against the auth limiter; the CLI says on ssh's exit 255 that
2116  a burst may have tripped it. #141
2117- A merge request head the target already contains is recorded as
2118  merged instead of refused; a fork is created with its parent in one
2119  insert; a failed transfer revert is reported; the repository quota is
2120  checked under a lock. #108
2121- Issues and merge requests share their comment, reference and
2122  author-or-write code. #110
2123- The payloads the web and clients decode are named types: =Created=,
2124  =MRCreated=, =IssueShow=, =MRShow=. JSON unchanged. #126
2125- Tests: parse failures per command, non-ASCII paths (which found
2126  =ls-tree= returning octal escapes, fixed with =core.quotepath=off= for
2127  every git the server runs), concurrent pushes. #129
2128
2129Replace the binary and restart, and reinstall the CLI. No migration.
2130
2131* v1.9.0 — 2026-09-03
2132
2133The runner is no longer an admin, the web no longer reaches around the
2134registry, and the CLI stops paying a handshake per command.
2135
2136- =keys add --scope runner= confines a key to =runner next/log/done= and
2137  read-only git; the runner commands accept that scope or an admin. The
2138  systemd drop-in sandboxes the runner process. gitbay.org's runner now
2139  polls as a non-admin =ci= account scoped to one repository. #92
2140- The web's repo create, issue create and edit, MR edit and both comment
2141  forms dispatch the command the CLI runs, so the repository quota, the
2142  archived-repository refusal, notifications, the body format and the
2143  audit entry hold from a browser. #93
2144- The CLI shares one SSH connection per instance (=ControlMaster=, five
2145  minutes idle): a command costs a round trip instead of a handshake,
2146  0.4 s instead of 4 s from a distant laptop. =no_multiplex = true= on
2147  an instance opts out. #94
2148- A disabled account is refused on every surface, and disabling revokes
2149  its API tokens along with its sessions. #95
2150- CODEOWNERS gates whenever the file exists on the target branch, not
2151  only under =require-approvals=. #99
2152- The HTTP listeners have header and idle timeouts, and SIGTERM drains
2153  in-flight requests and SSH sessions before exit. #104 #105
2154- =git archive= runs under a two-minute deadline and a 512 MiB cap. #124
2155- Every git invocation ends option parsing before the ref, so a ref
2156  shaped like an option is a bad revision and never a flag. #135
2157- The admin noun is gated in the dispatcher as well as in each handler;
2158  registry tests cover that and =ReadsStdin=. #127
2159- An e2e test runs every =ReadOnly= command against a populated instance
2160  and fails on any row it changes. #97
2161- =http.trusted_proxies= attributes proxied API requests to the last
2162  untrusted =X-Forwarded-For= hop for rate limiting; =email add= is
2163  capped at five codes an hour per account. #136
2164- A merge request head is built in the target repository, at
2165  =refs/merge-requests/<n>/head=, so a fork's merge request has
2166  =ci/<job>= statuses for =require-checks= to gate on. A head from
2167  another repository is built without the target's secrets. #98
2168- Triggers refuse deleting a user or organization that still owns
2169  repositories, whatever path the delete takes. #136
2170- The stylesheet's fonts are served again, and directory crumbs on blob
2171  and blame pages link to the tree. #102 #103
2172- The Threat-Model wiki page covers the runner. #138
2173
2174Replace the binary and restart, reinstall the CLI, and =make
2175deploy-runner=: the runner fetches merge request refs before checkout.
2176Migrations 0032 and 0033 run on start. The daemon host needs git 2.24
2177or newer for =--end-of-options=.
2178Operators running =gitbay-runner=: give it a non-admin account with a
2179key added by =keys add --scope runner=, remove the admin key it held,
2180and =make deploy-runner= to install the sandboxed unit drop-in; an
2181admin key keeps working meanwhile.
2182
2183* v1.8.1 — 2026-09-03
2184
2185Markdown and org files render when opened.
2186
2187- A =.md=, =.markdown= or =.org= file renders on its page the way a
2188  README does on the directory page, through the same renderer with
2189  relative links resolved against the file's directory. =source= in the
2190  action bar, or =?view=source=, shows the text as before. Every other
2191  file is unchanged. #88
2192- The e2e harness waits for the HTTP and git listeners as well as SSH
2193  before a test starts; a test whose first act was an HTTP request could
2194  be refused, which failed two otherwise green runs. #91
2195
2196Replace the binary and restart. No migration.
2197
2198* v1.8.0 — 2026-09-03
2199
2200The tracker's lists narrow, labels have colours you set, and the CLI's
2201help is the server's.
2202
2203- =issue list= takes =--label=, =--assignee=, =--author= and
2204  =--milestone= (a title, or =none= for issues with no milestone);
2205  =mr list= takes =--author= and =--milestone=. The store narrows in
2206  SQL, and the web lists take the same names as query parameters and
2207  show each active filter with a link that drops it and keeps the rest.
2208  Both lists had taken =--state= and nothing else, so the web's
2209  filtering could never match the CLI's. #84
2210- =label list= shows a repository's labels with their colour and how
2211  many issues carry each; =label set <label> [--color rrggbb|'']=
2212  creates a label or sets its colour; =label remove= takes it off every
2213  issue. The colour column had existed since labels did and nothing
2214  wrote it. The hash is optional because over bare ssh a bare =#= starts
2215  a comment for the tokenizer. =issue label --add= still creates a
2216  colourless label on the fly. #85
2217- =gitbay help= with a prefix or =--json= runs the server's help, the
2218  only place flags are written down and whose JSON is the contract;
2219  bare =gitbay help= is still the local tree. Cobra's built-in help had
2220  owned the word, so =gitbay help --json= failed on an unknown flag. #86
2221
2222Replace the binary and restart, and reinstall the CLI for the help
2223change. No migration.
2224
2225* v1.7.0 — 2026-09-02
2226
2227What an open instance needs before it is open: a cap on what one
2228account can take, a way out of a browser session you no longer hold,
2229and accounts that never verified do not stay forever.
2230
2231- =limits.max_repos_per_user= caps the repositories an account owns
2232  directly; =repo create=, =fork= and =import= refuse past it with the
2233  numbers. =limits.max_bytes_per_user= caps their disk: a push may be no
2234  larger than what the owner has left, riding the same
2235  =receive.maxInputSize= as the pack cap, and is refused outright when
2236  nothing is left. Organizations are not capped. Migration 0031 adds
2237  per-account overrides, set with =admin user limits <name> [--repos
2238  n|default] [--bytes n|default]= and shown by =admin user show=. Both
2239  default to 0, unlimited, so nothing changes until set. #82
2240- =registration.pending_expiry=, a duration, removes self-registered
2241  accounts still unverified after that long, hourly and once at start,
2242  audited as =pending.expired=. Empty keeps them, as before. #82
2243- =web sessions list= shows each unexpired browser session by a short id
2244  with its creation and expiry; =web sessions revoke <id>= ends one and
2245  =--all= ends every one. SSH-only, matching the token commands, and
2246  scoped to the caller. #83
2247- A step runs in its own process group and a cancel or timeout kills the
2248  group. On a host whose =/bin/sh= is dash, killing the shell alone left
2249  its child holding the log pipe, so a cancelled build held the runner
2250  until the child finished on its own, minutes for a test suite. The
2251  wait after a kill is capped at ten seconds besides.
2252- A commit with a build still queued or running is not queued again
2253  when a fast-forward lands it; the v1.6.0 skip counted only a finished
2254  success. #90
2255
2256- =golang.org/x/crypto= v0.56.0: GO-2026-6354 and GO-2026-6355 in its
2257  =ssh= package, both reached through =ssh.NewServerConn= in the
2258  embedded SSH server; one is a denial of service on a deadlocked
2259  undecided channel.
2260
2261Replace both binaries and restart: =make deploy= for the daemon
2262(migration 0031 adds two columns to =users= on start), then
2263=make deploy-runner= for the process-group kill.
2264
2265* v1.6.1 — 2026-09-02
2266
2267A cancel reaches a build in its clone.
2268
2269- The runner honoured a cancel only in its step loop; a build cancelled
2270  during its clone or checkout ran git to completion first, which on a
2271  loaded host was long enough for the v1.6.0 test to fail on the CI
2272  host while passing locally. One =runStep= now drives the clone, the
2273  checkout and each step with the cancel signal and the deadline, and
2274  checks the signal before starting at all. The runner logs how its log
2275  session ended when that was not a cancel.
2276
2277Replace the runner: =make deploy-runner=. The daemon is unchanged from
2278v1.6.0.
2279
2280* v1.6.0 — 2026-09-02
2281
2282The v1.4.0 admin surface answered questions about accounts. This one
2283answers questions about the machinery: which runner is alive, what is
2284stuck, whether last night's backup exists, and it lets an operator stop
2285a build instead of waiting it out.
2286
2287- A build a runner claimed and never reported is failed by the
2288  scheduler's minute tick, with no runner involved. It used to happen
2289  only when some runner polled again, so a dead sole runner left its
2290  builds running forever. =GITBAY_STALE_BUILD_DEADLINE= shortens the
2291  deadline for tests. #75
2292- Runners are visible. Migration 0030 adds =runner_seen=: one row per
2293  runner account with its last poll, the =-repos= scope it asked for,
2294  and the build it holds. =admin runners= lists them, over SSH and on
2295  the host. #76
2296- =GET /healthz=: whether the database answers and which commit serves,
2297  no auth, no repository data, 503 when the database does not answer.
2298  =healthz= joins the reserved names. #77
2299- The host monitor's hourly reading carries the age of the newest full
2300  backup and database snapshot, alerting at 25 and 2 hours, and the
2301  daemon's own =/healthz= answer read through =site_url=. Both ride the
2302  journald line and the webhook body. #78
2303- =admin stats= reports =lfs_bytes=. =admin gc --lfs= scans every
2304  repository's objects for LFS pointers and removes stored objects none
2305  names, keeping anything younger than a day since git lfs uploads
2306  before it pushes. #79
2307- =admin backup --verify <archive>= reads an archive back: SQLite's
2308  integrity check on the snapshot, and the repositories it names against
2309  the archive's. A database-only archive says so. Damage or a missing
2310  repository exits non-zero. #80
2311- A commit that already passed a job on another branch is not built
2312  again when a fast-forward lands it. Merging the six-layer v1.6.0 stack
2313  had queued eighteen jobs for commits that had each just gone green.
2314  Failed or abandoned builds still re-queue. #90
2315- =build cancel <owner/name> <n>= withdraws a queued build or ends a
2316  running one. For a running build the server closes the runner's log
2317  session, the runner kills the step within seconds, and its late report
2318  changes nothing. The commit status goes back to the passed result from
2319  another build of the same commit when one exists, else reads
2320  =cancelled=. Needs write access.
2321- Deploys copy with =rsync --partial=, so a transfer the host's load
2322  stalled resumes, and =make deploy-runner= installs a systemd drop-in
2323  (=Nice=10=, =CPUWeight=30=, =IOWeight=30=) so a build never starves the
2324  host's sshd again.
2325
2326Replace both binaries and restart: =make deploy= for the daemon, then
2327=make deploy-runner= for the runner, which carries its half of running-
2328build cancellation and installs the drop-in. Migration 0030 adds the
2329=runner_seen= table on start. The monitor change ships in
2330=deploy/cloud-init.yaml=; an existing host takes it by hand.
2331
2332* v1.5.0 — 2026-09-02
2333
2334Merge requests stack.
2335
2336- A merge request whose target is the source branch of another open
2337  merge request in the same repository is stacked on it. Nothing is
2338  stored and no flag exists; the forge reads the stack from the
2339  branches. =mr create= says =stacked on !A= when it applies, =mr show=
2340  carries =stacked_on= and =stacked=, =mr list= rows carry =stacked_on=,
2341  and the page says both directions in the header. #87
2342- When the lower merge request merges, everything stacked on it is
2343  retargeted onto what it merged into, with a system comment naming the
2344  merge and its reviews kept: after a fast-forward or merge commit the
2345  diff against the new target is the diff they were of. A squash or
2346  rebase merge under a stack is refused, naming the stack, since it
2347  would rewrite the commits the stack builds on.
2348- The first stack merged on gitbay.org was the six merge requests of
2349  v1.6.0, bottom-up, with no =mr retarget= typed. The wiki's
2350  Stacked-MRs page walks through it.
2351
2352Replace the binary and restart. No migration.
2353
2354* v1.4.0 — 2026-09-01
2355
2356Until now the instance had one operator surface: root on the host. Every
2357question about the instance itself — who is on it, what is stuck, what a
2358spam repository is doing — needed a shell on port 2222. This release
2359gives an instance admin the same answers over SSH, and one page on the
2360web.
2361
2362- =admin user list= pages accounts by username with
2363  =--state active|pending|disabled|admin=, each row carrying its state
2364  and =last_seen=, the newest use of any of its SSH keys or API tokens.
2365  =admin user show <name>= adds the keys with their last use, each
2366  address with how it was verified, PGP keys, org roles, owned
2367  repository count, API token names and live browser sessions. Both are
2368  SSH-only and refused to non-admins, like =audit=. #69
2369- =admin user promote|demote=. The only way to admin was
2370  =admin user create --admin=; an existing account could not be raised
2371  and an admin could not step down. Demoting the last admin is refused
2372  inside the transaction that counts them. The host-local twin is the
2373  recovery path when no admin key is reachable. #70
2374- Repository overrides for moderation: =admin repo list= with size and
2375  last push, and =admin repo archive|unarchive|visibility|delete=. Policy
2376  still knows nothing about instance admin — a private repository
2377  answers not-found to an admin as before — so each override skips the
2378  access check explicitly and writes its own =admin repo.<action>= audit
2379  row. #71
2380- =gitbayd admin= dispatches into the registry. User create, disable,
2381  enable and delete, email verify, invite and stats were reimplemented on
2382  the host; they now live in the registry, SSH-only and admin-gated, and
2383  the host binary runs them as the host — an admin context with no
2384  account behind it, so its audit rows say =source: host= where a
2385  session says the key fingerprint. Invite and stats gain an SSH twin by
2386  the same move. =backup=, =gc= and the backfills stay host-local. #72
2387- =audit= filters: =--actor <user>= or =--actor -= for actorless rows,
2388  =--action <prefix>=, and =--since= as a duration (=30m=, =24h=, =7d=)
2389  or a date. =gitbayd admin audit= takes the same flags and =--json=. #73
2390- =dashboard= carries a =queues= block for admins: per worker —
2391  webhooks, mail, mirrors, builds, dependency checks — the pending,
2392  retrying and dead-lettered counts, the oldest pending age, and the
2393  retrying or failed rows themselves, capped at twenty each. The mail
2394  queue was readable nowhere before. =/admin= renders the block by
2395  dispatching =dashboard=; non-admins get a 404 and no rail link. #74
2396- =gitbayd admin config show= prints the configuration in effect as
2397  TOML, defaults filled in and =smtp_pass= redacted, so a support
2398  question starts from what runs rather than what was written. #81
2399- Build badges are served as PNG at =badge/build.png= as well as SVG,
2400  for places that will not render SVG.
2401- Host monitoring writes its reading to journald on every run and exits
2402  non-zero on an alert, so an unset webhook no longer looks like a
2403  healthy host; it reads the ACME cache where it actually lives and
2404  reports the soonest expiry. govulncheck runs as its own CI job. The
2405  database is snapshotted hourly by =gitbay-db-backup.timer=, keeping 48,
2406  alongside the nightly full archive; archives inherit the database's
2407  mode rather than the umask default. #28
2408- A runner whose log stream drops no longer fails the build it was
2409  recording. #67
2410- =go.yaml.in/yaml/v3= and =golang.org/x/net= bumped. #60
2411
2412Replace the binary and restart. No migration. The =gitbay-db-backup=
2413timer and the monitor changes ship in =deploy/cloud-init.yaml= for new
2414hosts; an existing host takes them from there by hand.
2415
2416* v1.3.0 — 2026-08-31
2417
2418A runner took every repository's work, which decided where you could run
2419one.
2420
2421- =runner next= takes optional =owner/name= arguments and =gitbay-runner=
2422  takes =-repos=, so a runner claims builds only for the repositories it
2423  names. Naming none is the old behaviour, so an existing runner is
2424  unaffected. This is what makes a runner outside the server practical: one
2425  on a machine that should build a single project no longer picks up a
2426  build belonging to someone else, which with open registration need not be
2427  anyone the operator knows. The scoping is what the runner asks for rather
2428  than an ACL the server holds over it — a runner account is admin by
2429  necessity, so the boundary is the operator choosing how to start it. #66
2430
2431Replace the binary and restart. Runners want the new binary too, though an
2432old one keeps working unscoped.
2433
2434* v1.2.1 — 2026-08-31
2435
2436Merging landed commits without running anything.
2437
2438- A merge moves the target ref with a direct ref update, so it never
2439  reached post-receive and none of the ref-update work fired: no =push=
2440  event for webhooks to subscribe to, and no builds. Pushing a commit to a
2441  branch ran the whole =.gitbay/ci.yml=; merging the identical commit ran
2442  nothing. Both now happen in the merge path, with the build queueing
2443  shared between it and post-receive rather than living in one of them.
2444  #65
2445
2446Replace the binary and restart.
2447
2448* v1.2.0 — 2026-08-31
2449
2450A merge request said what its state was and almost nothing about when it
2451got there. It now keeps time.
2452
2453- Reviews and checks carry the moment they last said something, on the
2454  merge request page and in =mr show=. A =ci/<job>= check also reports how
2455  long its build ran, so the timing of a run is readable without opening
2456  it. Checks posted through =status set= have no build and report only the
2457  time. !137
2458- A merged or closed merge request names who resolved it and when. The
2459  header stated "X wants to merge" whatever the state; it now says "X
2460  merged A into main on <date>", or "closed this without merging", and
2461  drops the claim entirely for a row that carries no stamp rather than
2462  inventing a time.
2463- =mr show= gains =merged_at=/=merged_by= and =closed_at=/=closed_by=, a
2464  =created_at= per review, and =updated_at= plus =duration= per check, in
2465  both JSON and text. Additive: nothing existing changed shape.
2466- The iOS client renders all of it as of krz/gitbay-ios!37.
2467
2468Replace the binary and restart. Migration 0029 adds four columns to
2469=merge_requests= and backfills the merge stamp for merge requests already
2470merged, reading the =mr.merged= events. A merge with no such event to read
2471— an import, or a row older than its events — keeps no stamp, and every
2472surface says nothing about when it happened rather than guessing.
2473
2474* v1.1.0 — 2026-08-31
2475
2476Every release until now answered questions. This one notices something
2477on its own: that a repository's dependencies have moved, and says so
2478without being asked.
2479
2480- Dependency update checks, opt-in per repository. A daemon worker reads
2481  the manifests on the default branch, asks the ecosystem's registry what
2482  the current release is, and maintains one issue per repository — opened
2483  when something falls behind, rewritten when the set changes, closed once
2484  nothing is behind. No package manager runs, so it needs no CI runner and
2485  no configuration beyond turning it on. #58
2486  - =go.mod= against proxy.golang.org, =package.json= with
2487    =package-lock.json= against npm, =Cargo.toml= with =Cargo.lock=
2488    against crates.io, =requirements.txt= and =pyproject.toml= against
2489    PyPI. A lockfile wins where both exist. A requirement naming a set
2490    rather than a release — a range, a wildcard, a git or path source — is
2491    skipped, since a range that already admits the newest release is not
2492    news.
2493  - =repo deps enable|disable|status=, a toggle on the repository settings
2494    page, and the same three over the JSON API.
2495  - Off by default, because checking a private repository tells a public
2496    registry what it depends on. That is the owner's disclosure to make.
2497    =[deps] check_interval_hours= sets the cadence, default 24.
2498  - The issue is authored by a =gitbay-bot= account, so the existing
2499    notification mail reaches the repository's owner rather than excluding
2500    them as the actor. Its table is padded to its columns, which a
2501    renderer ignores and a mail client needs. #61
2502- =help= takes a prefix — =help mr= narrows the registry to one noun — and
2503  every command now documents its arguments, so the server answers "what
2504  are the flags" instead of being guessed at. #57
2505- Web: settings rows end in one column of controls, checkboxes drawn at
2506  the height of the inputs and buttons they sit beside #59; an added line
2507  keeps its leading dash in the diff; a contributor's several verified
2508  addresses collapse to one row #56.
2509
2510Replace the binary and restart. Migration 0028 adds two tables and, when
2511the name is free, the =gitbay-bot= account. An instance already using that
2512name for a user or an org keeps what it has: the account is not created,
2513and dependency checks report that as the reason they cannot open an issue
2514rather than the migration failing and the daemon not starting. #64
2515
2516* v1.0.1 — 2026-08-30
2517
2518Two CI fixes found by running orgo's release pipeline on this instance.
2519
2520- A runner killed between claiming a build and reporting it left the build
2521  =running= forever, and the commit's =ci/<job>= status pending with it.
2522  =runner next= now fails builds past a 90-minute deadline — longer than the
2523  runner's own =-timeout= — and resolves their commit status. #53
2524- =gitbay keys add= and =gitbay repo deploy-key add= take stdin as a bare
2525  =< key.pub=, but only forwarded it when =--file -= appeared in the
2526  arguments, so both sent an empty body and rejected input the SSH API
2527  accepts. #55
2528
2529Replace the binary and restart.
2530
2531* v1.0.0 — 2026-08-26
2532
2533The web finishes the job #35 set it: reading, reviewing and responding,
2534with the CLI still the complete interface. Every capability exists over
2535SSH, every web write dispatches the same control command, and anything
2536whose input is a credential stays on the command line. The [[https://gitbay.org/krz/gitbay/wiki/Parity][Parity]] page in
2537the wiki is the maintained matrix and says which rows are deliberately
2538CLI-only.
2539
2540- Diff view: one foldable section per file with line-number gutters,
2541  per-file stats, rename and binary handling, and syntax highlighting
2542  run per hunk per side so multi-line constructs lex as real code.
2543  Commit and merge request pages share it; review threads anchor
2544  inline.
2545- Repository facts on the code page: commit, branch and tag counts,
2546  detected license, latest release, build status, a language census by
2547  tracked bytes, and contributors resolved to accounts by verified
2548  email. All derived from git at render time.
2549- Account settings on the web: SSH keys with scope, OpenPGP keys, and
2550  email addresses. Public keys are the only credential-shaped input the
2551  web accepts — they are not secret, and a new user needs one
2552  registered before the CLI is reachable to them. Token minting and
2553  account export stay SSH-only.
2554- Organizations are run from their page: membership and roles, teams,
2555  team members, and team repository grants, for org admins.
2556- Commit log shows each commit's combined check status and gains a path
2557  filter, so per-file history is reachable without editing the URL.
2558- Issue references from commit messages read "referenced in commit
2559  <sha> by <author>", linking the author when their email is verified
2560  here.
2561- The rail's focus ring uses the shell's own mark: the light scheme's
2562  accent was a dark blue ring on a black rail.
2563
2564No migrations. No new config.
2565
2566Upgrading from v0.5.0 is replace-the-binary-and-restart.
2567
2568* v0.5.0 — 2026-08-26
2569
2570A design pass and a parity pass. The web stops being a read-only
2571mirror of the CLI without becoming the place you are expected to work.
2572
2573- New design: a black shell with a persistent left rail carrying
2574  cross-repo state (pinned repos, review queue), the repo header
2575  rendered identically on every tab so navigation never moves, sharp
2576  lines, self-hosted IBM Plex, and code blocks that read against both
2577  color schemes. Tree listings sort directories first and carry each
2578  file's last commit; diffs, inputs and controls were reworked to
2579  match.
2580- Web parity with the CLI, dispatched through the same command
2581  registry the CLI and JSON API use — every web write is the
2582  equivalent =gitbay= command with =--source web=:
2583  - merge requests: review, resolve threads, merge, close, and open a
2584    new MR from the browser
2585  - issues: state, labels, assignees, milestones
2586  - repositories: settings, branch protection, visibility
2587  - releases: create and edit; builds: trigger a job
2588  Commands marked SSH-only still refuse over the web: build secrets,
2589  mirror tokens, domain claims, token minting, deletion and transfer.
2590- A dashboard that answers "what needs me": review queue, assigned
2591  issues, pinned repos, and an activity feed. Author names resolve to
2592  accounts and link to profiles wherever commits appear.
2593- Build status badges at =/{owner}/{repo}/badge/build.svg= for public
2594  repos.
2595- =[web] title= sets the instance's display name, separate from the
2596  hostname commands are pasted with.
2597- =make build/test/deploy= targets.
2598- Fixes: the mobile tab strip scrolls sideways only, long commit
2599  subjects no longer overflow on narrow screens, the shell fills the
2600  viewport with the line-length cap moved onto prose, and the account
2601  cell lines up with the page footer.
2602
2603No migrations. New config: =[web] title=.
2604
2605* v0.4.0 — 2026-08-25
2606
2607- Git LFS: standard clients work over both transports.
2608  =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
2609  included; download needs read, upload write), minting stateless
2610  repo- and operation-scoped tokens for the batch API and basic
2611  transfers. Anonymous HTTPS downloads for public repos; uploads
2612  verified against size and sha256 before landing. Storage is
2613  content-addressed under =[lfs] root= behind a small interface an
2614  S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
2615  objects (512MB default).
2616- Build failures mail the repo's notify targets with the log tail and
2617  build link — failed scheduled jobs reach an inbox.
2618- =release edit= updates a release's title and notes (absent flags
2619  keep their field); omaha-style CI note rebuilds work again.
2620- Syntax highlighting follows the color scheme: class-based chroma
2621  with light and dark palettes, the light-pinned code background is
2622  gone, and markdown fences and org src blocks highlight too. The UGC
2623  sanitizer admits only chroma's token-code classes.
2624
2625No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
2626
2627* v0.3.0 — 2026-08-25
2628
2629- CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=
2630  over SSH (admin-only runner protocol; statuses feed =require-checks=).
2631  Per-repo secrets set over stdin and injected into build environments;
2632  cron schedules (server-local time) and tag-glob triggers, mutually
2633  exclusive per job; =build list/show/log/trigger= and a builds tab.
2634- Pages: public repos' =pages= branches served on =<owner>.<domain>=
2635  (=[pages] domain=), custom domains with DNS TXT ownership challenges
2636  and 7-day expiry for pending claims, per-subdomain on-demand ACME.
2637- Wikis (=.wiki= companion repos, access mirrors the parent) and teams
2638  within orgs (members-role scoping, per-repo team grants).
2639- Activity graphs on user and org pages, backfillable
2640  (=admin backfill-activity=); commits attributed by verified author
2641  email, deduped by sha.
2642- MR pages list the commits the MR carries; =mr show= gains a commits
2643  section.
2644- Per-file history: =?path== on the web log, =--path= on =repo log=,
2645  history link on blob pages.
2646- Mirror status surfaced in =repo show= and the repo header
2647  (admin-only), with sync errors visible; tag-only pushes now schedule
2648  mirror syncs.
2649- Rendering: GFM tables/strikethrough/autolinks/task lists, blob image
2650  previews, raw serves images with real content types (README images
2651  render under nosniff), 0BSD license recognition, repo website links,
2652  compact dashboard pins.
2653- =admin user delete= for accounts that anchor nothing, with named
2654  blockers otherwise.
2655- Fixes: wiki pages no longer overflow on mobile (iOS font-inflation
2656  trigger), GHSA-free deps, secret values pipe correctly through the
2657  CLI.
2658
2659Migrations 0020-0025 apply on start. New config: =[pages] domain=.
2660The runner is a new binary (=gitbay-runner=); see the wiki's Admin
2661guide for setup. Stress-tested against an import of git.git (82k
2662commits): see the wiki's Performance page.
2663
2664* v0.2.0 — 2026-08-24
2665
2666- Deploy keys: repo-bound CI keys (=repo deploy-key=), ro/rw, rename- and
2667  transfer-proof.
2668- Commit statuses (=status set/list=), combined state on MR pages, and a
2669  =require-checks= merge gate.
2670- Email notifications for issue and MR activity (participants with
2671  verified addresses; never the actor).
2672- Inline review threads on MR diffs (=mr diff-comment/threads/resolve=),
2673  stale on force-push, =require-resolved= merge gate.
2674- Required approvals with CODEOWNERS (=require-approvals=; latest review
2675  wins, author excluded) and a =require-resolved= gate; merge gate order
2676  is checks → approvals → CODEOWNERS → resolved threads → signatures.
2677- Web design revamp: token-based stylesheet (light+dark), wordmark and
2678  favicon, aligned layout grid, card-based listings, designed 404,
2679  mobile pass.
2680- Cross-references and mentions: =#N=, =!N=, =owner/name#N=, =@user=
2681  autolink in issue/MR text, viewer-aware for private repos.
2682- Archived repositories (read-only with badge) and repo topics.
2683- Blame view with signature-aware attribution and 1000-line pages.
2684- Repository search (name/description/topic) and per-repo code search
2685  (=repo grep=, web search tab); blob line anchors.
2686- Homepage: dashboard for logged-in users (pinned repos via =repo pin=,
2687  open MRs and issues involving you), landing page for visitors, full
2688  public listing at =/explore=; MR diffs collapsed by default.
2689- Milestones (=milestone create/list/close=, =issue/mr milestone=) with
2690  web progress; issue templates from =.gitbay/issue-template*.md=
2691  (CLI =$EDITOR= prefill and web form).
2692- Issue actions from commit messages landing on the default branch:
2693  =closes/fixes/resolves #N= closes, bare =#N= leaves a reference
2694  comment; once per issue+commit.
2695- Vanity Go imports: =[go_import]= config serves go-import meta tags, so
2696  =go install gitbay.org/gitbay/cmd/...@latest= works.
2697- Release script: =deploy/release.sh <tag>= builds reproducible
2698  linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
2699- Repository maintenance: =admin gc= (repack/prune, per-repo sizes),
2700  =admin stats= (counts + disk usage), weekly =gitbay-gc.timer=.
2701- Releases: tag-anchored notes and binary assets (=release= commands,
2702  assets over SSH stdin/stdout, web releases tab with downloads).
2703- GitHub history import: =repo import-issues= brings issues and PRs
2704  (as merged/closed MRs) with comments, labels, and state, attributed
2705  inline and resumable.
2706- Push and pull mirroring (=repo mirror=): background sync, read-only
2707  pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
2708- Web signup at =/register= for open and invite instances.
2709- Audit log (=audit=, =gitbayd admin audit=): every mutating command
2710  with source key fingerprint, registrations, force-pushes, auth
2711  failures. Hardening: per-IP auth-failure throttling
2712  (=ssh_auth_rate=), =max_pack_bytes= enforced, =admin user
2713  disable/enable=.
2714- Account migration: =gitbay migrate --from <host>= (bundle
2715  export/replay + client-side git mirror); =gitbay auth export= as a
2716  user-level backup.
2717- Editable issues and MRs (=issue edit=, =mr edit=, web forms).
2718- Commit references appear as system messages with linked shas.
2719- Design: top nav, repo listing rows (topics, license, last updated),
2720  file table headers, README relative-link resolution, branch
2721  dropdown, web pinning, org owner picker, label filters, linked
2722  usernames and commit parents, =/privacy= page, blue accent.
2723
2724Upgrade notes: migrations 0006–0019 apply on start. No config changes
2725required; =[go_import]=, =[mirrors]=, =web.privacy_notice=, and
2726=web.mode = "accounts"= are opt-in.
2727
2728* v0.1.0 — 2026-08-24
2729
2730First tagged release: the complete CLI-first forge. SSH control plane
2731(bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues,
2732merge requests (ff/merge/squash/rebase with signature policy), OpenPGP
2733and SSHSIG verification with retroactive re-verification, orgs, repo
2734import, web UI (view-only or accounts mode), registration with invites
2735and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups,
2736ACME TLS, systemd deployment.