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