CHANGELOG.org

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