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