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