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