CHANGELOG.org

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