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.31.1 — 2026-09-20
   8
   9The stylesheet URL carries the build's hash (#239).
  10
  11- =/static/style.css= was served with a day's cache lifetime at an
  12  unversioned URL, and =must-revalidate= only forces a check once that
  13  lifetime expires. For a day after a deploy a browser rendered the new
  14  markup against its old stylesheet; the ETag was never consulted.
  15- The layout stamps the served bytes' hash on the link. A deploy changes
  16  the URL, so a cached copy cannot answer it, and a request carrying the
  17  current hash names bytes that cannot change and is served without
  18  revalidating at all.
  19
  20* v1.31.0 — 2026-09-20
  21
  22The desktop layout (#226): the web UI uses a wide screen.
  23
  24- One centered container at 100rem; the repository header, main and
  25  footer align on it. Text keeps its measure.
  26- The repository header is two rows: name, description and buttons,
  27  then the tabs.
  28- Issue, merge request, build, explore, search and notification rows
  29  are one line above 64rem, and those pages render at the container
  30  width.
  31- The dashboard is three columns: pinned repositories with open issue,
  32  merge request and last-build counts; a tile per queue with the queue
  33  rows below; the activity feed.
  34- A file navigator beside blob, blame and edit pages lists the file's
  35  directory and marks the file.
  36- Side columns: state, labels and open milestones on the issue and
  37  merge request lists; status, jobs and branches on builds; topics on
  38  explore; kinds on search; sections on repository settings, account
  39  settings and admin. A label or milestone nothing is filed under is
  40  left out, so the merge request list offers the labels that have
  41  merge requests rather than every label the repository holds; the
  42  branch group caps at ten, and the branch field below it still takes
  43  any ref.
  44- Below 62rem the facet and section columns become a closed disclosure
  45  before their content, headed by the filters in force, and the
  46  navigator hides, since the tree page is the navigator on a phone.
  47  Below 80rem the dashboard's pinned repositories return to a chip row
  48  above the queues.
  49
  50Three accessibility defects the wider scan found, on pages the
  51sixteen-page one never covered (#226):
  52
  53- A label chip carries a tone per scheme. Chip text is 12px, which owes
  54  4.5:1 against the ground mixed from the colour itself, and no single
  55  colour clears that on both canvases; the stored hex still names the
  56  label, and the page picks the tone. A page stamped light or dark now
  57  sets =color-scheme= to match, so native controls follow the theme.
  58- Every =pre= scrolls sideways, so every one takes =tabindex="0"=: a
  59  keyboard reaches a blame view, a build log and a search match the way
  60  it already reached the pre blocks of rendered markup.
  61- A link that shares its line with other text is underlined — a path
  62  crumb, a heading that names an owner, an empty-state note. Link and
  63  muted text are 1.07:1 apart in dark.
  64
  65The profile about text is a file (#236).
  66
  67*Upgrade note.* Run =gitbayd admin migrate-profile-about= after
  68upgrading. Migration 0058 parks each owner's about text in a holding
  69table and drops the columns; that command writes it into a public
  70=<owner>/.gitbay=. Until it runs, profiles that had an about show none.
  71Nothing is lost in between — the table keeps the text.
  72
  73- The about text on a profile is =profile/README.md= or
  74  =profile/README.org= on the default branch of =<owner>/.gitbay=,
  75  read with that repository's own access. The extension picks the
  76  renderer; =.md=, =.org= and =.markdown= resolve in that order.
  77  =profile show= gains =about_path=, the file the text came from.
  78- =profile set= and =org profile= lose =--about=, =--about-format= and
  79  =--file=. The about is written by a push or =repo commit-file=, the
  80  way a wiki page is. The settings page points at the file and offers
  81  to create the repository that holds it.
  82- Repository names may start with a dot; owner names may not. A
  83  repository whose name starts with a dot stays out of =explore= and
  84  off the profile's repository list, and remains in =repo list= and at
  85  its own URL.
  86- =repo commit-file= writes the first commit of a repository that has
  87  never been pushed to. An unresolvable branch is still an error
  88  anywhere the repository already has refs.
  89
  90A web UI sweep.
  91
  92- The rail's squares are 44px at every width, and its glyphs are 20px
  93  on a phone. Below 34rem eleven squares no longer fit, so explore,
  94  bookmarks, snippets, new repository, settings, admin and log out
  95  move into a More menu and the strip keeps dashboard, search,
  96  notifications, More and your account.
  97- Snippets are on the rail. The link on a profile page stays.
  98- =/new= creates an organization as well as a repository; the form
  99  leaves the profile page.
 100- =repo fork= takes =--owner=, and the web's Fork button opens a form
 101  with an owner and a name. The owner is you or an organization you
 102  administer, checked as =repo create= checks it; an organization's
 103  fork is not counted against your repository quota. A name of your
 104  own is how you fork the same repository twice.
 105- The dashboard's pinned key reads above the list rather than under
 106  it, its build dot sits on the row's centre line, and a pinned chip
 107  on the second row has its bottom border back.
 108- The activity feed drops its state dot.
 109- The SSH key and account tables keep each row on one line and scroll
 110  sideways, rather than wrapping a fingerprint or a timestamp.
 111- =.pathbar= actions sit on the centre line with the ref and the
 112  crumbs.
 113
 114The SonarCloud dashboard is at zero (#238). Four of its 38 findings were
 115real; the rest are dismissed with their reasons recorded on the
 116dashboard.
 117
 118- A trailing-slash redirect cannot leave the site. =net/http= fills
 119  =URL.Scheme= and =URL.Host= from an absolute-form request line, which
 120  RFC 7230 requires a server to accept, so =GET http://evil.example/cmc/=
 121  answered =301 Location: http://evil.example/cmc=. A browser sends
 122  absolute form only to a proxy, so nothing reached this through one
 123  directly.
 124- The global search, repository search and register forms no longer
 125  carry =autofocus=, which moved focus past the heading, the result
 126  count and the search page's filters. The diff line-comment box keeps
 127  it: that form renders only after the reader asks for it on a line,
 128  and with no JavaScript nothing else carries focus across the reload.
 129
 130* v1.30.0 — 2026-09-19
 131
 132Every command runs on every surface, markup previews before it is
 133written, and the web findings from the forge comparison (#232, #233,
 134#234, #235).
 135
 136*Upgrade note.* Dropping =SSHOnly= widens what a full-scope API token
 137can do: it can now administer the instance and mint further tokens.
 138Review the tokens you have issued and re-mint as =--scope read= any
 139that only need to read.
 140
 141- *Every command now runs on every surface.* The registry's =SSHOnly=
 142  flag is gone, and with it the refusal that met build secrets, mirror
 143  credentials, API token minting, web sessions, deploy keys, the audit
 144  log and instance administration when they arrived over HTTP. What a
 145  caller may do is the account's rights narrowed by the scope of the
 146  key or token the request came with, decided in one place. A
 147  full-scope API token can now do anything its owner can, minting
 148  another token included; a read-scoped one still cannot write.
 149  Operators should review the tokens they have issued and re-mint as
 150  =--scope read= any that only need to read (#234).
 151- =/admin/users= lists every account with the state filter and cursor
 152  =admin user list= takes, and runs promote, demote, disable and enable
 153  per row. Demote and disable ask for the username to be typed (#234).
 154- =[registration] notify_admin= mails the instance's admins when an
 155  account becomes active: an invite redeemed, or an open-mode signup
 156  that verified its address. Off by default, requires =[mail]=, and
 157  queued like any other notice (#234).
 158- Every web form that takes markup has a Preview button beside its own
 159  submit: issue and merge request create, their edit and comment boxes,
 160  release create and edit, the profile about text, and the file editor
 161  on a path the forge renders. It renders the draft above the textarea
 162  and writes nothing (#235).
 163- Links inside running text are underlined: the meta lines on issues,
 164  merge requests and releases no longer tell a link apart by colour
 165  alone.
 166- File view line numbers are 24px targets and keep the focus ring;
 167  chroma's LineLink rule, which set =outline: none=, is dropped from the
 168  served palette.
 169- Every rendered =<pre>= and the landing page's quickstart block take
 170  keyboard focus, so a block that scrolls sideways can be reached.
 171- On one column the issue and merge request aside follows the thread
 172  instead of preceding it.
 173- The file tree at 320px keeps its last column inside the card.
 174- A path no route matches renders the 404 page instead of a plain-text
 175  body.
 176- An org image link with no description gets its file name as alt text,
 177  so a README badge is a named link.
 178- Release titles are h2.
 179- Text responses are gzipped for clients that accept it.
 180- =web theme set system|light|dark= and an Appearance section on the
 181  account page fix the colour scheme per account. Migration 0057 adds
 182  =users.theme=.
 183- A path that only misses because of a trailing slash redirects to the
 184  path without it: =/cmc/= reaches =/cmc=, =/cmc/-/snippets/= reaches
 185  =/cmc/-/snippets= (#233).
 186
 187* v1.29.0 — 2026-09-19
 188
 189The icon nav is a top bar at every width.
 190
 191- The 48px row of glyphs that narrow screens already used is now the
 192  only shell layout; the left column is gone. The row keeps the same
 193  order, labels and current-page mark, with settings, admin and the
 194  account cell at the far right.
 195- The landing picture is recaptured under the new shell.
 196
 197* v1.28.1 — 2026-09-19
 198
 199The newcomer route names its web path (#226).
 200
 201- After registering, the page and the verification mail say the code
 202  can be pasted under Settings after signing in with an emailed link,
 203  beside the terminal command.
 204- The SSH keys wiki page names this instance instead of a placeholder;
 205  the Quickstart leads with the browser route and Homebrew before
 206  =go install=.
 207
 208* v1.28.0 — 2026-09-19
 209
 210Labels on merge requests (#231), and a one-column dashboard. Migration
 2110056 adds =mr_labels=; the daemon migrates on start.
 212
 213- =mr label <owner/name> <n> --add <l> --remove <l>= attaches and
 214  detaches labels the way =issue label= does, resolving an org's label
 215  first and creating a repository label on the fly; =mr list --label=
 216  filters; =mr show= carries them; the event is =mr.labeled=.
 217- The merge request page has a Labels group with the same form as an
 218  issue; list rows show label chips and =?label== filters the list.
 219- =label list= and the labels pages count merge requests beside issues;
 220  removing a label detaches it from every issue and merge request. An
 221  org label folding repository rows moves merge request rows too.
 222- The dashboard is one column: the activity feed is a section after
 223  the queues, since the icon rail leaves no wide column to balance.
 224
 225* v1.27.0 — 2026-09-19
 226
 227The follow-ups from the forge benchmark (#226) and two profile fixes.
 228
 229- On a wide repository overview the About block (counts, licence, latest
 230  release, build, contributors, languages) and the clone commands sit in
 231  a column beside the file table; under 62rem the order is unchanged
 232  (#228).
 233- The landing page's Explore and Create an account routes sit above the
 234  picture, and the picture is capped so the first screen carries a call
 235  to action (#229).
 236- Each row of the merge request list shows the combined check state of
 237  its head, linking to the diff, and a comment count (#230). Labels on
 238  merge requests do not exist yet (#231).
 239- The profile page lists repositories after the activity graph, and a
 240  table in rendered prose keeps its last row's bottom border (#225).
 241
 242* v1.26.0 — 2026-09-18
 243
 244A closed merge request can name the request that carried its change
 245(#223). Migration 0055 adds the column; the daemon migrates on start.
 246
 247- =mr close <owner/name> <n> --by <m>= records, at close time, that !m
 248  supersedes !n; =mr edit <n> --superseded-by <m>= sets it on a request
 249  already closed and =--superseded-by none= clears it. Both refuse a
 250  number that is not a request in the same repository, or the request
 251  itself. =mr show= carries the field.
 252- The web close form takes the number as an optional field. The closed
 253  request's title line says "in favour of !m"; the request it names
 254  says "supersedes !n". The state stays closed; nothing is inferred
 255  from prose.
 256- On a phone the dashboard's activity feed stacks after the queues; the
 257  aside-first rule is for checks and reviewers on a merge request
 258  (#222).
 259
 260* v1.25.0 — 2026-09-18
 261
 262The site rail is an icon column (#220).
 263
 264- At desktop the rail is a 3.5rem column of inline glyphs: dashboard,
 265  explore, search, notifications with the unread count as a badge,
 266  bookmarks, new repository, then settings and admin, then the account
 267  and sign-out. The search field leaves the rail; =/search= has its own.
 268- Under 52rem the rail is one 48px row that neither wraps nor scrolls.
 269- Every icon link carries an accessible name (=aria-label=, a title and
 270  visually hidden text) and hides its SVG from assistive tech; a test
 271  enforces it.
 272- Pinned repositories are a chip row under the dashboard heading; the
 273  review queue is the dashboard's section. Neither is in the rail.
 274
 275* v1.24.1 — 2026-09-18
 276
 277The dashboard feed and the phone-width rail strip (#222, #220).
 278
 279- Build events record their commit; the dashboard's activity feed folds
 280  a commit's jobs into one line per run with the combined state and a
 281  state dot. A status outside the known set is never shown as success.
 282- Feed times are relative, with the exact UTC time in a title, as the
 283  tree listings already do.
 284- Under 52rem the rail strip keeps the brand on its first row, shows
 285  pinned repositories as a compact labelled sub-row, and New repository
 286  is a =+= button at every width.
 287
 288* v1.24.0 — 2026-09-18
 289
 290The web follow-ups to the design foundation (#219, #220, #221, #222,
 291#224, #225), and a repository maintenance command.
 292
 293- =build list= takes =--ref=, =--status= and =--job=, pushed down to the
 294  store query; the builds page reads the same three as GET parameters
 295  with shareable links, and groups a commit's jobs into one run showing
 296  the combined state (#224).
 297- The merge request page's "Files changed" view is wide; the
 298  conversation and commits views stay at reading width (#219).
 299- The profile page lists repositories above the biography; the
 300  contribution grid carries month labels and a legend (#225).
 301- The dashboard shows populated queues first, collapses empty ones to a
 302  heading, and says what the two Open lists cover (#222, in part).
 303- Under 52rem the rail strip keeps one scrolling row and shows pinned
 304  repositories as a second row instead of hiding them (#220).
 305- Polish from the v1.23.0 review: caption spans instead of dangling
 306  labels, runner attach keeps a rejected key and reports success, the
 307  tree root of the default branch is the repository home so the header
 308  is identical within the code tab, the file editor is wide (#221).
 309- =admin mr prune <owner/name> <n>... --yes= drops the named merged or
 310  closed MRs' =refs/merge-requests/N/head= and runs =git gc --prune=now=
 311  on the repository, for commits a history rewrite left reachable only
 312  through them. Open and source-gone MRs are refused. Nothing drops a
 313  head ref on its own. =mr diff= and the MR page say when a head is gone
 314  (#227).
 315
 316* v1.23.0 — 2026-09-17
 317
 318The web design foundation (#218). Tokens measured in both schemes, one
 319control family, content widths per page, and the landing, repository
 320overview, merge request and settings pages recomposed. Set =[web]
 321title= to =gitbay= in lower case; the templates already are.
 322
 323- =style.css= rewritten on tokens defined on =:root= and again for dark;
 324  =TestTokenContrast= enforces the floors and
 325  =TestEveryTemplateClassHasARule= that every template class has a rule.
 326- Buttons are primary, secondary, quiet or destructive; one focus ring on
 327  everything; success and error flashes share one shape.
 328- Every page picks a width: wide for code, reading for lists and threads,
 329  bounded for forms.
 330- The repository header shows description and topics on the code tab
 331  only; the overview leads with the file table and puts clone commands
 332  and facts after the README; "Find file" is "Search code".
 333- A merge request states who merged or closed it under its title and
 334  explains an empty diff.
 335- Repository settings are bounded rows with a consequence beside each
 336  control, a saved flash, a rejected value kept, and topics as one field.
 337- Landing copy says what the product is and where to go; the register
 338  form says to paste the contents of the key file and links the SSH keys
 339  wiki page.
 340- The landing page shows the merge request page, light and dark,
 341  captured from gitbay.org (two embedded PNGs under =/static/img/=).
 342
 343* v1.22.1 — 2026-09-13
 344
 345One merge gate fix.
 346
 347- =require-checks= no longer refuses a merge request head that carries
 348  no statuses when nothing was going to report one: a repository with
 349  no =.gitbay/ci.yml=, or one whose jobs all wait on a schedule or a
 350  tag, had no mergeable merge request and no remedy but turning the
 351  setting off. A head whose config carries a job a push runs, and a
 352  head in a repository that has recorded a status before — which is
 353  what reporting from outside through =status set= looks like — is
 354  still refused (#216).
 355
 356* v1.22.0 — 2026-09-12
 357
 358The CLI output sweep (#183). The rules are on the wiki's Users page,
 359under "Output rules".
 360
 361- A bad invocation prints the command's registered usage, the one
 362  source of it; the hand-written copies are gone.
 363- The =gitbay= CLI pads list rows into aligned columns at a terminal
 364  and leaves the tabs alone when piped.
 365- An empty list prints nothing on stdout and =nothing to list= on
 366  stderr.
 367- Every refusal (exit 4) says what to do instead.
 368- =status list= and =repo topics= print rows.
 369- =admin runners remove=; =forget= stays as an alias until the next
 370  release.
 371- A missing positional argument prints the hint and the usage line
 372  (#215).
 373
 374* v1.21.0 — 2026-09-12
 375
 376The web UI/UX sweep (#182).
 377
 378- Destructive controls ask for the object's name typed beside the
 379  button: release delete, snippet delete and file remove, team delete,
 380  label remove, and SSH key, email and PGP key removal. Reversible
 381  controls keep a plain button.
 382- Login returns to the page that asked for it, and says so.
 383- One timestamp format everywhere, =2006-01-02 15:04 UTC=.
 384- Tags on the refs page and in the release form are in version order,
 385  newest first.
 386- The file editor explains up front when signed commits or
 387  merge-requests-only protection would refuse the commit, answers 404
 388  for a branch that does not exist, and says when a path is new.
 389- Merge refusals name the strategy rather than the flag; an issue
 390  closed by a commit reads "closed by <who> in commit <sha>".
 391- Repository settings: every Save names its field. Labels: the colour
 392  column appears only when it means something. Sidebars use one shape
 393  for empty. List rows show the state only under "all" and say "in
 394  <milestone>". Global search counts its results. A merged MR shows
 395  its merged head and a deleted source branch. The repository home
 396  shows the SSH clone URL beside HTTPS. The settings page names
 397  =auth token create=.
 398
 399* v1.20.1 — 2026-09-11
 400
 401One config check.
 402
 403- A negative =limits.max_snippets_per_user= is refused at config load,
 404  as =max_repos_per_user= and =max_bytes_per_user= already were; it
 405  used to pass validation and read as unlimited (#214).
 406
 407* v1.20.0 — 2026-09-11
 408
 409Snippets (#195): named text files a user owns outside any repository,
 410shared by URL and edited in place.
 411
 412- Migration 0054: =snippets= and =snippet_files=.
 413- =snippet create|show|list|edit|delete= and =snippet file
 414  set|get|remove=. Files are UTF-8 under =limits.max_snippet_bytes=
 415  (1MB), at most 64 per snippet; a snippet keeps at least one.
 416  =limits.max_snippets_per_user= (0, unlimited) caps how many an
 417  account may own, admins included. Visibility =public=, =unlisted=
 418  (default) or =private=; a private snippet is not found to everyone
 419  but its owner and admins.
 420- Web: =/<owner>/-/snippets= lists, each snippet page renders its
 421  files with a raw route per file, and the owner creates, edits and
 422  deletes from the page through the same commands. The owner page
 423  links to the list.
 424
 425* v1.19.0 — 2026-09-11
 426
 427Labels and milestones an org defines once for every repository under
 428it, and =Closes owner/name#N= acting across repositories (#203).
 429
 430** Org labels and milestones
 431
 432- Migration 0052: =labels= and =milestones= rows belong to a
 433  repository or to an org, exactly one, with a partial unique index
 434  per scope. Existing rows and their memberships keep their ids.
 435- A repository owned by an org sees the org's labels and milestones
 436  beside its own; =issue label --add=, =issue milestone= and =mr
 437  milestone= resolve the org's row first. A repository cannot create,
 438  recolour, remove, close or reopen a name its org holds; the refusal
 439  names the org command.
 440- =org label set|list|remove= and =org milestone
 441  create|list|close|reopen=, for org admins. Creating a name that
 442  repositories under the org already use folds them in: their issues
 443  and merge requests move to the org's row and the repository rows
 444  go. =repo transfer= into an org folds the same way. Counts on org
 445  rows span the repositories the caller can read.
 446- Web: read-only =/<org>/-/labels= and =/<org>/-/milestones=, linked
 447  from the org page; an "org" mark on repository label and milestone
 448  pages, whose forms act on repository rows only.
 449- =label list= and =milestone list= JSON carry =org: true= on an org
 450  row.
 451
 452** Cross-repository closes
 453
 454- =Closes owner/name#N= in a commit on the default branch, or in a
 455  merged merge request's title or body, closes that issue when the
 456  actor holds write on the target and the pushing key's scope allows
 457  it: a deploy key never acts outside its binding. An unknown or
 458  refused target does nothing and logs nothing; the text stays a
 459  plain autolink. An archived target is refused. Bare =owner/name#N=
 460  without a keyword stays display-only.
 461
 462** Store
 463
 464- A migration whose first line is =-- foreign_keys: off= runs on one
 465  pinned connection with foreign keys off, re-enabled afterwards and
 466  =foreign_key_check= required empty. Rebuilding a table other tables
 467  reference loses the children's rows otherwise, even under
 468  =legacy_alter_table=.
 469
 470** Behaviour changes
 471
 472- =milestone create= exits 1 on a duplicate title, as =org milestone
 473  create= does; it exited 2 before.
 474
 475Upgrade: replace the binary and restart; migration 0052 runs on
 476start and copies every label and milestone row once.
 477
 478* v1.18.1 — 2026-09-11
 479
 480A runner that cannot hang on a dead connection, SSH keys with names,
 481and dependency updates.
 482
 483** CI runner
 484
 485- Every ssh invocation carries =ConnectTimeout=10=,
 486  =ServerAliveInterval=15= and =ServerAliveCountMax=3=, placed after
 487  the identity and the operator's =-ssh-opts= so an operator's value
 488  wins. A claim whose TCP session had died under it blocked a laptop
 489  runner's poll loop for thirteen hours; it now fails within a minute
 490  and the loop resumes.
 491- The build comment in =deploy/Containerfile.ci= stages the file in
 492  the runner user's home before =podman build=: a login shell under
 493  =su= cannot read root's stdin and does not share root's =/tmp=.
 494
 495** Keys
 496
 497- SSH keys carry a label (migration 0051). =keys add --label= defaults
 498  to the authorized_keys comment; =keys label <fingerprint> [<text>]=
 499  renames or clears it. =keys list=, =admin user show=, =repo
 500  deploy-key list= and the settings page show it. Deploy, runner and
 501  admin-created keys take the comment as their label. Closes #208.
 502
 503** Web
 504
 505- Org autolinks stop before trailing punctuation: a bare URL closing a
 506  sentence or a parenthesis no longer takes the =.=, =,= or =)= into
 507  the href. Closes #209.
 508
 509** Dependencies
 510
 511- golang.org/x/crypto 0.57, x/image 0.46, x/net 0.59, x/term 0.46.
 512  Closes #205.
 513
 514* v1.18.0 — 2026-09-10
 515
 516What the first real job on a user's runner needed. A twice-daily
 517archive pull that had run on the server's host moved into a container
 518and then onto a laptop, and each hop found a gap.
 519
 520** CI runner
 521
 522- A secret with newlines — a private key — reaches the build. An env
 523  file has no escape for one, so such values are named on podman's
 524  command line with =--env NAME= and valued in the podman process's own
 525  environment; the value touches neither argv nor the file.
 526- =GITBAY_SSH= in every build's environment: the instance's ssh
 527  destination as the build reaches it. Under podman the host's own
 528  addresses belong to the container (pasta), so a loopback remote is
 529  rewritten to the address pasta exposes the host at. A job that
 530  publishes back to the instance uses the variable rather than
 531  guessing. Inside a container =ssh= expands =~= from the passwd entry,
 532  not =$HOME=; keep a build's ssh config in the workspace and pass =-F=.
 533- =-identity= drops the user's =~/.ssh/config= (=-F /dev/null=):
 534  =IdentitiesOnly= kept identities the config named, so a laptop runner
 535  authenticated as the user's own full-scope key and, on an admin's
 536  machine, could claim every repository's builds. A first-seen host key
 537  is accepted, since a service cannot answer a prompt.
 538- A schedule tick queues nothing while the job's last build is pending
 539  or running, matching the push path. A repository no runner served
 540  gained one row per tick forever. A finished build does not suppress
 541  the tick; a schedule re-runs an unchanged commit on purpose. #206
 542- =admin runners forget <fingerprint>= drops a key's heartbeat row; the
 543  key stays. =admin runners= rows are the repositories a key may claim.
 544- The bay1 unit names no =-repos=: the runner key's attachments are the
 545  boundary. =gitbay-ci:2= carries =python3-venv= and =sqlite3=, since
 546  it is also the default image for every repository the runner is
 547  attached to.
 548
 549** Decisions
 550
 551- Claim order stays oldest-first across everything a key may claim; a
 552  repository that must never wait on another gets a runner of its own.
 553  #207
 554- No per-account cap on queued builds and no schedule floor: with the
 555  tick dedupe a repository with no runner holds one row per scheduled
 556  job, and a busy schedule spends its owner's compute. #206
 557- Attaching a runner is =n/a= on iOS: the key lives on the machine that
 558  runs builds.
 559
 560** Documentation
 561
 562- Users: =GITBAY_SSH=, ssh's home inside a container, the =ci.yml= caps
 563  (ten jobs, fifty steps, 4096 bytes a step, 64 KiB a file) and where a
 564  broken config shows up. Admin, CI and Threat-Model follow the changes
 565  above.
 566
 567** Upgrading
 568
 569Replace the binaries and reinstall the CLI. No migration. A runner
 570started with =-identity= (every runner =gitbay-runner init= set up) now
 571ignores =~/.ssh/config=; a runner that relied on it for a =ProxyJump=
 572or an alias passes the equivalent in =-ssh-opts=. Homebrew:
 573=brew upgrade krz/tap/gitbay-runner=.
 574
 575* v1.17.0 — 2026-09-09
 576
 577CI without the operator's compute: a runner anyone installs and
 578attaches to their own repositories, and the server rule that makes
 579that safe. The rest of the #184 list besides.
 580
 581** CI
 582
 583- A runner key claims builds only for the repositories it is attached
 584  to. =repo runner add <owner/name> < key.pub= attaches one; a key the
 585  server has not seen lands on the caller's account with scope
 586  =runner=. =repo runner list= shows each attached key with its last
 587  poll and the build it holds; =repo runner remove <fingerprint>=
 588  detaches it. All three on the settings page. A runner-scoped key
 589  with nothing attached claims nothing, whoever owns it; a full-scope
 590  admin key still claims any repository. =runner log= and =runner
 591  done= refuse a build outside the key's attachments. #184
 592- Closed: any account could add a runner-scoped key, and =runner next=
 593  with no arguments handed it the oldest pending build on the
 594  instance, secrets included.
 595- =runner next --untrusted=: without it a merge request head from a
 596  fork is never claimed. The runner passes it when started with
 597  =-untrusted=; the bay1 unit does, because it isolates in podman.
 598- =gitbay-runner init= generates a key under =~/.config/gitbay-runner/=,
 599  writes =config.toml= beside it, and prints the public key with the
 600  command that attaches it. The runner reads that file when present
 601  and flags override it. =-identity=, defaulting to the generated key,
 602  makes ssh and git use the runner's own key and no other. Homebrew:
 603  =brew install krz/tap/gitbay-runner=, then =brew services start
 604  krz/tap/gitbay-runner=. Releases ship =gitbay-runner= binaries.
 605- =admin runners= heads its output with the queue: builds pending now,
 606  and over the last day the builds claimed, the wait to claim (average
 607  and worst) and the builds the reaper ended instead of a runner
 608  reporting them. Rows are per key, with the fingerprint and the
 609  repositories the key may claim. Migration 0049. #184
 610- Stop tests for the runner's drain: a signal mid-step, the drop-in's
 611  =KillMode= and =TimeoutStopSec=, and a transient systemd user unit
 612  where one exists. #179
 613- The CI wiki page carries every push shape against every job kind and
 614  what dedupe, path filters, schedules and the reaper make of it, with
 615  a test per row. #176, #177
 616
 617** Importing
 618
 619- =import-issues --api-base= reads Forgejo instances: paging by =limit=,
 620  oldest first, comments read once, attribution and pull heads taken
 621  from the API base rather than github.com. #191
 622
 623** Documentation
 624
 625- Users: "Your own runner". Admin, Threat-Model, CI, FAQ and Parity
 626  follow the attachment rule.
 627
 628** Upgrading
 629
 630Replace the binaries and reinstall the CLI. Migration 0050 (runner
 631attachments; the runner heartbeat table is rekeyed by key and
 632emptied), applied on start. One behaviour change: a runner polling
 633with a key of scope =runner= claims nothing until a repository admin
 634attaches it with =repo runner add=. Do that right after the restart.
 635A full-scope admin key is unaffected. Merge request heads from forks
 636are built only by a runner started with =-untrusted=.
 637
 638* v1.16.0 — 2026-09-08
 639
 640What stops a stranger from moving here: the repository plumbing and
 641the team gates the #185 walk found missing, twelve merge requests
 642merged as one stack.
 643
 644** Repositories
 645
 646- =repo settings default-branch <owner/name> <branch>= moves HEAD and
 647  the record; a branch that does not exist is refused. A first push of
 648  =master= or =trunk= into a fresh repository moves the unborn HEAD to
 649  the branch that arrived, so the clone checks something out. Settings
 650  page select. #189
 651- =repo rename <owner/name> <new-name>=: the row and the directory move
 652  together, with transfer's revert on a failed move. Clone URLs change.
 653  #190
 654- =repo settings require-mr on=: an existing protected branch refuses
 655  every direct push in pre-receive, =repo commit-file= and the web
 656  editor included; =mr merge= is its only writer. Creating the branch
 657  is still a push. #197
 658- =repo settings protect-tag <glob>= (and =unprotect-tag=): matching
 659  tags are created once and refuse moves and deletion. Separately, a
 660  tag a release is anchored to refuses both while the release exists,
 661  protected or not; delete the release first. #201
 662- =repo access list= reports effective access: one row per account
 663  with the highest role and where it comes from (owner, direct, org
 664  admin, org member, team). It used to list direct grants only, so a
 665  repository reached through teams answered with nothing. #200
 666- Removing an org member drops their team memberships in the same
 667  transaction. They kept every grant their teams carried, and re-adding
 668  them to the org restored nothing because nothing had gone. #196
 669- An outsider gets one answer about an org: its existence and members
 670  are public, its teams are for members, and =org team list= and =show=
 671  refuse a non-member rather than say the org does not exist. Ref #200
 672- A repository name may not end in =.atom=, as it may not end in
 673  =.git=. Ref #192
 674
 675** Merge requests
 676
 677- A push that leaves the merge request's diff unchanged keeps its fresh
 678  reviews: the patch-id of each revision against its own merge base is
 679  compared, and a rebase onto a target that moved on no longer stales
 680  every approval. A push that changes the diff stales them as before.
 681  #198
 682- The merge gates are one computation shared by =mr show= (a =gates=
 683  block: approvals counted and required, owners outstanding per file,
 684  open threads, checks, whether a fast-forward is possible), the merge
 685  request page, and =mr merge=, which names every unmet gate in one
 686  refusal rather than the first. =mr review= reports =counts= and says
 687  when a verdict is advisory because the reviewer cannot write. #199
 688
 689** Notifications
 690
 691- =@name= in an issue, merge request, comment or diff comment files
 692  "mentioned you" in that account's inbox and makes them a participant
 693  of the thread, provided they can read the repository and have not
 694  muted it. Watchers are not told about a mention addressed to someone
 695  else. Migration 0047. #202
 696- =notifications settings mail on|off= (and =show=): inbox rows are
 697  filed either way, this is the mail half. Login links are not activity
 698  and still arrive. The account page carries the same switch.
 699  Migration 0048. Ref #194
 700
 701** Web
 702
 703- Atom feeds: =/{owner}/{repo}/releases.atom=,
 704  =/{owner}/{repo}/log.atom[/{ref}]= and =/{owner}/activity.atom=,
 705  rendered over the rows the pages already serve. The owner feed covers
 706  public repositories only, since a reader carries no session; a
 707  private repository answers 404. The releases, log and owner pages
 708  carry the discovery link. #192
 709
 710** Documentation
 711
 712- The Users page says what differs over stock ssh: a multi-word value
 713  needs a second layer of quotes, and =help <noun>= replaces =--help=.
 714  The companion-wiki paragraph #170 made stale now points at
 715  =.gitbay/wiki/=. #204
 716
 717** Upgrading
 718
 719Replace the binary and reinstall the CLI. Two migrations (0047, the
 720mentions table; 0048, the per-account mail switch), applied on start.
 721Nothing changes behaviour until a setting is turned on: =require-mr=,
 722=protect-tag= and =mail off= are all opt-in.
 723
 724* v1.15.0 — 2026-09-07
 725
 726Builds run in containers, a rebase is not rebuilt, and a runner restart
 727no longer strands the build it was running.
 728
 729** CI
 730
 731- A build's steps run in a rootless podman container, one per job. The
 732  runner clones outside the container with its key and bind-mounts the
 733  workspace in, so a step cannot reach the key, the runner's environment,
 734  or another build's workspace. =image:= is required per job and is
 735  validated as a reference, never pulled: an operator provisions images
 736  on the host. A runner configured for podman that has none refuses to
 737  start rather than fall back to the host. =-isolation none= is the
 738  explicit host-execution mode. =-cpus= and =-memory= cap a build's
 739  container. #144
 740- Builds have a home directory that outlives the build, so the Go module
 741  cache and the sonar scanner survive between runs. It is mounted into
 742  the container at the same path, and only that directory. Ref #144
 743- The host preparation script, the unit drop-in and the weekly image
 744  prune ship with =make deploy-runner=; each hardening flag the drop-in
 745  relaxes carries the reason in place. Ref #144
 746- A nightly canary on the runner host proves the boundary holds:
 747  =cmc/ci-smoke= runs a job that tries to read the key and list sibling
 748  workspaces, and fails if either succeeds. Ref #144
 749- Dedupe keys on the commit's tree, not its sha. A rebase that changes
 750  nothing is not rebuilt: the new commit gets the earlier success as its
 751  status, naming the build. Scheduled and tag builds carry no tree and
 752  are never reused. #177
 753- =vuln= and =sonar= run nightly on =main= rather than on every push;
 754  neither could inform a merge. Branches run =build= and =test=. #177
 755- A rewritten branch is filtered against the merge base rather than the
 756  old tip, so a rebased branch whose own commits change code no longer
 757  reads as a docs-only push and skips its jobs. #176
 758- A build whose runner's log stream ended with no outcome is failed two
 759  minutes later, instead of sitting =running= until a fixed deadline.
 760  Migration 0046. Ref #179
 761- The runner retries reporting a finished build's outcome, four times
 762  over about thirty seconds, when the server is unreachable. A gitbayd
 763  restart at that moment used to lose the result. Ref #179
 764- The runner drains on SIGTERM: it claims nothing more, finishes and
 765  reports the build in flight, then exits. A second signal exits at once.
 766  The unit allows fifty minutes. #179
 767
 768** Repositories
 769
 770- =repo show= reports the caller's watch and bookmark state, and the
 771  parent of a fork when the caller can read it. #178
 772- =repo unwatch= clears the row from either state; =repo mute= is the
 773  explicit silence. Watch then unwatch used to leave an account below
 774  the default with no way back. The web header toggle follows. #180
 775
 776** Upgrading
 777
 778Replace the binary and reinstall the CLI. One migration (0046, the
 779build log's close time), applied on start.
 780
 781The runner now defaults to =-isolation podman= and refuses to start
 782without a working podman and a named image. Prepare the host with
 783=deploy/runner-podman-setup.sh= and build =localhost/gitbay-ci:1= from
 784=deploy/Containerfile.ci= before deploying it, or pass =-isolation
 785none= to keep running steps on the host. Validate on a scratch
 786repository with =-repos= scoped to it first; the wiki's Admin page has
 787the procedure.
 788
 789The runner's unit gains =TimeoutStopSec=50min= and =KillMode=mixed= so
 790a stop reaches the runner alone and it can drain; under the default
 791kill mode systemd ends the build's container with the runner.
 792=make deploy-runner= therefore waits for a build in flight.
 793
 794* v1.14.0 — 2026-09-06
 795
 796Logging into the web without an SSH key, wikis inside the repository,
 797CI that skips what a change does not touch, and the browser catching up
 798with the command line on nine capabilities.
 799
 800** Accounts and the web
 801
 802- A browser session can be requested by mail: the login page takes a
 803  username or a verified address and sends a link that works once and
 804  expires in fifteen minutes. An account with no SSH key had no way into
 805  the web at all. The response never says whether the account exists, and
 806  the form appears only when the instance has SMTP. #155
 807- A login link resolves to any verified address on the account, not only
 808  the primary. #158
 809- Login mail is queued rather than sent from a goroutine, so a link in
 810  flight survives a restart. #159
 811- A suspended account cannot mail itself a session, and a link minted
 812  before suspension opens nothing. #156
 813- The session cookie is =SameSite=Lax=, and a test now walks every
 814  mutating route to assert it carries the origin check. #157
 815- =POST /register= is reachable on an open instance again.
 816
 817** Wikis
 818
 819- A wiki lives at =.gitbay/wiki/= on the default branch, so editing one
 820  is editing a file in the repository — a push, or the web editor — and
 821  it is cloned, diffed and reviewed like anything else. The companion
 822  =<repo>.wiki= is gone. #170
 823
 824** CI
 825
 826- Path filters: =paths= and =paths-ignore= per job, so a docs commit
 827  does not run the whole suite. #169
 828- A branch's first push derives its diff base from the merge base
 829  rather than treating every file as changed. #171
 830- A job filtered out records a skipped status instead of nothing, so
 831  =require_checks= cannot wait forever for a check that will never
 832  arrive. #172
 833- A force-push no longer leaves queued builds pointing at an object
 834  that is gone; the orphan is cancelled when a runner claims it. #152
 835- A build step's environment is constructed rather than inherited. It
 836  was =os.Environ()= plus the build's variables, which handed repository
 837  content everything set on the runner service. A step now gets =PATH=,
 838  =HOME=, =LANG=, =CI=, its =GITBAY_*= variables and its secrets. =HOME=
 839  is the workspace, so a build cannot read the runner's =.netrc=,
 840  =.npmrc= or =.gitconfig=, where tools keep credentials. Ref #144
 841- A runner host can be prepared for rootless podman:
 842  =deploy/runner-podman-setup.sh=, the systemd changes it needs, and
 843  weekly image pruning. Nothing reads them yet; the preparation ships
 844  before the runner that requires it, on purpose. Ref #144
 845
 846** Collaboration
 847
 848- =mr review request --add <user>= asks a particular person for a
 849  review, who then carries it in their queue and is notified;
 850  =--remove= withdraws the ask. The queue was computed from involvement
 851  alone, so a collaborator who had not touched a thread heard nothing.
 852  #145
 853- Bookmarks save someone else's repository to come back to, and the
 854  count is the instance's only popularity signal. Separate from pins
 855  rather than a flag on them: a pin is private quick access to your own
 856  work and drives the rail, a bookmark is public and counted. =repo
 857  bookmark=, =repo unbookmark=, =repo bookmarks=, a control on the
 858  repository header, the count in the facts bar, and =/bookmarks=. Read
 859  access is all a bookmark needs, and one made while a repository was
 860  public drops out of the listing if it goes private. #146
 861
 862** The browser catches up
 863
 864Nine capabilities that were CLI-only and had no reason to be:
 865
 866- label management — list, create, colour, remove #163
 867- dependency status under the toggle that turns checks on #164
 868- release delete #165
 869- the account export bundle, as a download #166
 870- organization create and rename; delete stays CLI-only, wanting a
 871  typed confirmation, and the page says so #167
 872- opening a merge request from a fork, with a source picker offering
 873  the branches of every fork you can push to #168
 874- forking a repository #174
 875- cancelling a queued or running build #162
 876- the profile form #161, and a markup picker on issue and merge
 877  request create #160
 878- admin table headers align with their columns #151
 879
 880** CLI
 881
 882- =gitbay mr rebase <n>= replays a merge request's branch onto its
 883  target and re-pushes it. A repository requiring signed commits accepts
 884  only fast-forward merges, so a merge request whose target moved had to
 885  be rebased by hand; the refusal already named the procedure and this
 886  runs it. The git work is local, so the replayed commits carry your
 887  signature — the server still holds no key. A branch in a fork is
 888  refused, naming the repository to run it in. #175
 889
 890** Security
 891
 892- Mutating commands are bounded per account in the dispatcher, so SSH,
 893  the JSON API and the web spend one budget and a caller cannot refresh
 894  it by changing surface. Authentication failures were throttled;
 895  commands were not. #148
 896- A dead-lettered mail is logged by its queue row id, not the recipient
 897  address, and the relay's error is redacted before logging because a
 898  rejection quotes the address it rejected. The address stays on the
 899  row, where =/admin= shows it. One rule for every mail type. #173
 900- The 2026-09 sweep's coverage — and what it did not reach — is recorded
 901  in the wiki's Threat-Model rather than in a closed issue. #149
 902
 903** Dependencies
 904
 905- goldmark 1.8.6, sqlite 1.58.0. #140
 906
 907** Upgrading
 908
 909Replace the binary and reinstall the CLI. One migration (0043,
 910bookmarks), applied on start.
 911
 912=limits.write_rate= defaults to 60 mutating commands a minute per
 913account. A script that writes faster will be refused with exit 4 and a
 914retry time; raise it in =[limits]=, or slow the script. Read-only
 915commands, the runner protocol and the host CLI are not counted.
 916
 917A companion =<repo>.wiki= repository is no longer read. Move its pages
 918to =.gitbay/wiki/= on the default branch.
 919
 920Runner isolation is half done. Builds still run as the runner's user
 921with no container: the step environment no longer leaks the service's,
 922and a host can be prepared for podman, but nothing yet executes a build
 923in one. Do not enable CI for repositories you do not trust. #144 stays
 924open for the execution half.
 925
 926* v1.13.3 — 2026-09-05
 927
 928Only a writer's review decides a merge gate, and a scan of one branch
 929stops overwriting another's results.
 930
 931- =mr review= resolves with =CanRead= and applied no further check, and
 932  the merge gates counted every fresh verdict. On a public repository
 933  that let anyone with an account satisfy =require_approvals= — defeating
 934  four-eyes review by holding two accounts, which on an instance with
 935  open registration means defeating it outright — and equally let a
 936  passer-by block a merge the owner wanted, with no override and only a
 937  force-push to clear it. Both were confirmed against a running instance.
 938  Reviewing stays open to every reader, because an outside opinion on a
 939  public change is worth having; it no longer decides the gate. What
 940  does is write access, the same question the gates already answer. An
 941  uncounted review is marked advisory by =mr show= and by the merge
 942  request page, both reading the same rule, so the page cannot show an
 943  approval the gate ignores. #147
 944- The two =git upload-pack= spawns behind the smart HTTP transport now
 945  resolve git at start-up like everything else. The v1.13.2 rewrite
 946  matched a plain identifier for the context and these pass
 947  =r.Context()=, so it skipped them. #153
 948- CI analyses each branch as itself. Every scan was recorded against the
 949  project's main branch whatever branch produced it, so a feature branch
 950  replaced main's results — a branch that removes findings made main look
 951  clean before the fix merged, and one that added them made main look
 952  broken when it was not. #154
 953
 954Replace the binary and reinstall the CLI. No migration.
 955
 956A repository relying on approvals from accounts without write access
 957will find those merges now refused. That was the defect: such an approval
 958never meant the repository accepted the change. Grant write, or name the
 959reviewer in CODEOWNERS and grant write, if their approval is meant to
 960count.
 961
 962* v1.13.2 — 2026-09-04
 963
 964The first SonarCloud scan's findings: eight fixed, the rest triaged and
 965dismissed with reasons.
 966
 967- A pages directory redirect could leave the site. Both redirects passed
 968  the raw request path to =http.Redirect= while the cleaned path sat a
 969  line above; =net/url= keeps a leading =//=, and Go emits
 970  =Location: //evil.example/= unchanged, which a browser reads as
 971  protocol-relative. Reaching it needed a public repository named like a
 972  host under the subdomain's own owner — repository names permit dots —
 973  so it was narrow rather than impossible. The destination is built from
 974  the cleaned path through =url.URL= now, which also settles the two
 975  spellings the first fix missed: a =..= that escapes to the root, and a
 976  backslash, which browsers following the WHATWG rules treat as a
 977  separator. #153
 978- The runner's default workspace was =<tmp>/gitbay-runner=: a fixed name
 979  in a world-writable directory, created with =MkdirAll=, which succeeds
 980  against a directory whoever already owns it. bay1 was never exposed —
 981  its unit names a workspace — but the default is what anyone running the
 982  binary by hand gets, and this is the process that clones repositories
 983  and exports build secrets. The default moves under the user's cache
 984  directory, the workspace is created 0700, and a symlink or a directory
 985  owned by someone else is refused. One we own that is merely too
 986  permissive is tightened rather than refused, since every runner before
 987  this one made it 0755 and refusing would take the runner down on
 988  upgrade. #153
 989- Logout and flash consumption expire their cookies with the attributes
 990  the setting calls used. Deletion worked either way; the difference was
 991  a reviewer's puzzle, and four findings. #153
 992- The topics-remove field has a label. A placeholder is not an accessible
 993  name. TestEveryInputHasAnAccessibleName is the guard that was missing,
 994  and it knows both associations — six inputs use
 995  =<label>Name <input></label>=, which is as good as for/id. #153
 996- git and ssh are resolved once at start-up rather than searched on every
 997  spawn, and gitbayd refuses to start when one is absent instead of
 998  failing on whichever request first needed it. This was 74 of the 118
 999  findings; a dashboard that is mostly permanent noise is one nobody
1000  reads. #153
1001
1002Also: SQLite migrations are excluded from analysis. They were read as
1003PL/SQL, where ='' is NULL=, so =WHERE col = ''= on a =NOT NULL DEFAULT ''=
1004column — correct SQLite, and the shape used throughout — read as a
1005null-comparison bug.
1006
1007Replace the binary and reinstall the CLI. No migration. A runner whose
1008workspace is group- or world-readable will have it tightened to 0700 on
1009next start, and will refuse to start if that workspace is a symlink or
1010belongs to another user.
1011
1012* v1.13.1 — 2026-09-04
1013
1014A command that reads its payload from stdin says so, and SonarCloud runs
1015alongside the vulnerability scan.
1016
1017- =repo secret set= blocked with nothing printed, which is
1018  indistinguishable from a hung connection, and pressing Enter did not
1019  end it because the server reads to EOF — so it looked the same before
1020  and after the value had been typed, and the secret echoed into the
1021  scrollback on the way. A terminal is now told what is wanted and that
1022  Ctrl-D ends it; a secret is read without echo and takes one line, so
1023  Enter is enough. Piped input is unchanged, byte for byte: =printf %s
1024  "$TOKEN" | gitbay repo secret set ...= still sends exactly the token.
1025  Applies to =keys add=, =auth pgp add=, =repo deploy-key add= and
1026  =release asset add= as well; public keys keep echoing, since they are
1027  public. #150
1028- A =sonar= CI job reports to SonarCloud, alongside =vuln=. Report-only:
1029  it does not gate a build, unlike the vulnerability scan. A merge
1030  request from a fork builds without secrets by design, so the job says
1031  why it is skipping there rather than failing on a missing credential.
1032  Only =SONAR_TOKEN= is secret and it is a build secret; the
1033  organization, project key and host are checked in. Ref #149
1034
1035Replace the binary and reinstall the CLI. No migration.
1036
1037* v1.13.0 — 2026-09-04
1038
1039Collaboration. A review is composed and submitted as one thing, a merge
1040request can say it is not asking yet and can show what changed since you
1041last looked, issues are searched by their text, and the events half the
1042mutations never recorded now exist.
1043
1044- A review is composed as a unit. =mr diff-comment --pending= holds a
1045  comment back; =mr review= publishes the batch with the verdict and says
1046  how many went with it; =mr review --discard= throws away what was never
1047  submitted. A pending comment notifies nobody when written — the review
1048  is the announcement, and it names its own size — and does not gate a
1049  merge, since a thread only its author can see is one nobody else could
1050  resolve. #111
1051- =mr create --draft=, =mr draft=, =mr ready=. A draft does not merge and
1052  does not appear in anyone's review queue; marking it ready is the
1053  request for review. Draft is a flag rather than a fifth state, so every
1054  =state = 'open'= rule still means what it did, and the merge refusal is
1055  unconditional: every other gate is a setting an admin turns on, and
1056  this one is the author's own statement about their own work. #111
1057- =mr range-diff= shows what changed between two revisions of a merge
1058  request, and =mr revisions= lists them. A push stales every review and
1059  nothing said what had moved; a diff of the two heads cannot answer it,
1060  and the previous head was overwritten in place. Each side of the
1061  comparison carries the merge base it had at the time, since measuring
1062  both against today's would attribute every commit that landed on the
1063  target in between to this merge request's author. #111
1064- Issues and merge requests are searched by their title and body, over
1065  FTS5. =issue list --search= and =mr list --search= narrow one
1066  repository; the instance-wide =search= reaches bodies now, and both
1067  list pages carry a search box. What someone types is quoted term by
1068  term, so an FTS5 operator — =c++=, =AND=, a lone quote — is a word to
1069  match rather than a syntax error. #114
1070- Ten mutations that changed a repository silently now record an event:
1071  =mr.closed=, =mr.reviewed=, =mr.edited=, =mr.retargeted=, =mr.draft=,
1072  =issue.edited=, =issue.labeled=, =issue.assigned=, =issue.milestoned=,
1073  =mr.milestoned=, =release.deleted=. =mr close= and =issue edit= also
1074  notify participants, which they did not. The full list is on the API
1075  wiki page and =webhook add --events= refuses a name that is not on it,
1076  since a subscription to a typo would never fire and nothing would say
1077  so. #112
1078- =gitbay-runner -jobs N= runs N builds at once. Claiming was always a
1079  single transaction that selects and updates, and each build already
1080  worked in its own directory, so several workers were safe the whole
1081  time; the runner never used more than one. #115
1082- A merge request replayed from a migration bundle has a diff. The bundle
1083  carried no head at all, and =mr diff= resolves through the head ref, so
1084  a merged merge request — which has no source branch left — could only
1085  fail. Re-running an import after the git push sets the head it could
1086  not set the first time. The GitHub import fetches =refs/pull/*/head=,
1087  which a mirror made with the default refspecs does not carry. #128
1088- The review loop is driven end to end by three accounts in the test
1089  suite: draft, ready, thread, approval, resolve, merge, with approvals,
1090  CODEOWNERS and require-resolved all on at once. Every one of those had
1091  its own test and none of them met. #139
1092- A bare =go test ./...= says the timeout is too short instead of
1093  panicking eleven minutes in and blaming whichever test was running.
1094  =make test= is what CONTRIBUTING asks for now. #143
1095
1096Migrations 0036 through 0039 add the search index, the draft flag,
1097pending review comments and merge request head history; 0036 and 0039
1098backfill from what is already there. They run on daemon start.
1099
1100Two things this does not do. There is still no way to ask a particular
1101person for a review — the queue is computed from involvement, so a
1102collaborator with write access who has not touched a thread hears nothing
1103(krz/gitbay#145). And a CI build still runs as the runner's own user with
1104no container; the runner on this instance is scoped to one repository,
1105which is what keeps that narrow (krz/gitbay#144). Both are v1.14.0.
1106
1107* v1.12.0 — 2026-09-04
1108
1109The store and the push path. Dashboard queries walk an index instead of
1110sorting the table, concurrent writers wait instead of failing, expired
1111rows are swept, and a large first push no longer forks a process per
1112commit.
1113
1114- Every dashboard list scanned its table and sorted the result to take
1115  fifty rows. Reachability is correlated subqueries and cannot be
1116  indexed; the index supplies the =ORDER BY= instead, so the walk stops
1117  at =LIMIT=. On 20k issues and 20k merge requests: open issues 11.8ms
1118  to 0.8ms, open merge requests 12.1ms to 0.8ms, the review queue 15.5ms
1119  to 0.3ms, assigned issues 10.6ms to 0.04ms. The last of those also
1120  drives from =issue_assignees= rather than testing =EXISTS= against
1121  every issue. #137
1122- Concurrent writers serialise rather than failing. Every transaction in
1123  the store writes, and a deferred one takes the write lock at its first
1124  write, by which point another may hold it; SQLite answers
1125  =SQLITE_BUSY= and does not run the busy handler for that case, so
1126  =busy_timeout= could not help. Measured with eight concurrent
1127  read-then-write transactions, 44% of them failed. Beginning immediate
1128  takes the lock up front, where the timeout applies. #121
1129- =repo settings= updates no longer overwrite each other.
1130  =settings_json= is one blob, and every caller read it off a repository
1131  loaded earlier, changed a field and wrote it all back; two admins at
1132  once and the later write put back what it had read for the other's
1133  field. The read and the write happen together now, under one
1134  immediate transaction. #123
1135- Expired sessions and tokens are swept, and =[retention]= caps how long
1136  the audit log, the activity feed, webhook deliveries and the mail
1137  queue keep a row. Unset means forever, which is what every existing
1138  instance gets. #122
1139- The audit entry records flag names without their values. Secrets never
1140  reached argv — they travel on stdin — but prose did: =--body <the
1141  whole issue>= was stored verbatim, in a table nothing pruned, for a
1142  repository that may be private. Identifiers are positional and
1143  survive. #122
1144- pre-receive on a require-signed repository forked a =cat-file= per
1145  incoming commit and built one JSON message holding the whole push. A
1146  50k-commit first push forked 50k processes and held the history in
1147  memory twice. One =cat-file --batch= serves the push now, and the
1148  daemon verifies each commit as it arrives. #100
1149- The payloads other surfaces decode are named types in =control=. httpd
1150  had its own copies of what the build, profile and dashboard commands
1151  emit, so a field added to a command was silently absent on the page.
1152  #126
1153
1154Migration 0035 adds three indexes; it runs on daemon start.
1155
1156Two changes in behaviour rather than configuration. A heavily contended
1157write now blocks for up to =busy_timeout= (five seconds) instead of
1158returning an error immediately — waiting is the point, but a caller that
1159treated the error as normal will see a pause instead. And anything
1160parsing =audit --json= for command arguments will find flag values gone;
1161the flag names and the positional arguments are still there.
1162
1163* v1.11.0 — 2026-09-04
1164
1165The web catches up with the rest of the forge: search across the
1166instance, a notification inbox, a compare view, linkable diff lines,
1167and a pass over contrast, heading structure and the stylesheet.
1168
1169- Notifications are no longer mail or nothing. An =inbox= table holds a
1170  row per recipient whether or not the instance has SMTP;
1171  =notifications list= reads it, unread by default, and =notifications
1172  read <id>... | --all= clears it. =repo watch= adds you to a
1173  repository's notifications and =repo unwatch= mutes it, with a mute
1174  beating every other reason to be told, including owning the
1175  repository or having written the thread. The unread count rides on
1176  =dashboard= and in the web rail. #113
1177- =search= matches repository paths, descriptions and topics, and issue
1178  and merge request titles, across everything the caller can read;
1179  =/search= renders it with a field in the rail on every page, and an
1180  anonymous visitor gets the public rows from the same query. Titles
1181  only — body search is #114. #118
1182- =/{owner}/{repo}/compare/{a}...{b}= shows what one ref adds on top of
1183  another. Diff rows, files and review threads carry ids, so a line can
1184  be linked to. The issue and merge request lists page at fifty with
1185  the cursors the commands already emit. #118
1186- CODEOWNERS gating is a setting rather than a file that happens to
1187  exist: =repo settings require-codeowners <owner/name> on|off=, off by
1188  default, still independent of =require-approvals=. A repository can
1189  carry the file as documentation of who to ask without it gating
1190  merges. #142
1191- A failed form action's reason rides a one-shot cookie instead of
1192  =?e=<message>=, so it no longer survives a reload or lands in
1193  history. #119
1194- A diff cut at 4 MiB cuts on a line boundary and says so, the
1195  diffstat says its counts are partial, and a merge request's commit
1196  list says "first 100 of N". #117
1197- Page templates parse once with the layout at start-up, so a template
1198  that does not parse fails the process rather than the first visit to
1199  its page. #116
1200- Markdown headings carry ids, matching org pages, and the stylesheet
1201  serves a hash ETag with a day's lifetime and answers a matching
1202  =If-None-Match= with 304. #132
1203- Dark-mode buttons carry a visible edge (a 1 px border was 1.3:1
1204  against the 3:1 non-text contrast floor), and a stored label colour
1205  is held between 0.12 and 0.28 relative luminance so it clears 3:1 on
1206  both grounds while keeping its hue. #120
1207- Accessibility: the pin star is decoration and the word carries the
1208  meaning, the refs and release asset tables have scoped column
1209  headers, state filters carry =aria-current= rather than marking the
1210  active one by colour alone, and a rendered README or wiki page's
1211  headings move down one level so they sit under the page's own. #133
1212- The stylesheet drops rules no template reaches, folds two off-scale
1213  values onto the type scale, and resolves the classes templates asked
1214  for and it never defined. #131
1215- On a phone the tab bar wraps to a second row instead of scrolling
1216  sideways with its scrollbar hidden, and the landing page says in
1217  three sections what a reader, a writer and a reviewer can do. #134
1218
1219Migration 0034 adds =inbox= and =repo_watchers=; it runs on daemon
1220start. Reinstall the CLI for =search=, =notifications= and =repo
1221watch/unwatch=.
1222
1223Two upgrade notes beyond replacing the binary. A repository that
1224relied on a CODEOWNERS file gating merges by its presence alone loses
1225that gate until =require-codeowners= is set: nothing back-fills it,
1226since the database cannot say which branches carry the file. And
1227=search= and =notifications= are now reserved top-level routes, so a
1228user or organization already holding either name keeps it but its
1229profile page is shadowed by the route.
1230
1231* v1.10.0 — 2026-09-04
1232
1233Every command parses its arguments the same way, the web answers by
1234exit code, and a restart no longer waits on idle connections.
1235
1236- One flag parser for every command: an unknown flag, a missing value or
1237  too many arguments is exit 2 with the command's usage, everywhere.
1238  =mr review --approve --bogus= used to report repository =--bogus= as
1239  not found. #96
1240- =--json= is honoured by the dispatcher's own refusals, so a script told
1241  no gets the envelope. #109
1242- A store failure is exit 1 and not-found is exit 3; both used to be
1243  usage errors. #107
1244- Web form actions answer by exit code: the 404 page for a thing that
1245  does not exist, the page with the message for anything else. #106
1246- Inside a clone, =gitbay mr create= takes the checked-out branch as
1247  =--source=; =gitbay <noun> --help= is the server's reference for the
1248  noun, flags included. #101 #130
1249- Shutdown closes idle SSH connections at once and drains only sessions
1250  mid-command; a store failure during key lookup no longer counts as a
1251  bad key against the auth limiter; the CLI says on ssh's exit 255 that
1252  a burst may have tripped it. #141
1253- A merge request head the target already contains is recorded as
1254  merged instead of refused; a fork is created with its parent in one
1255  insert; a failed transfer revert is reported; the repository quota is
1256  checked under a lock. #108
1257- Issues and merge requests share their comment, reference and
1258  author-or-write code. #110
1259- The payloads the web and clients decode are named types: =Created=,
1260  =MRCreated=, =IssueShow=, =MRShow=. JSON unchanged. #126
1261- Tests: parse failures per command, non-ASCII paths (which found
1262  =ls-tree= returning octal escapes, fixed with =core.quotepath=off= for
1263  every git the server runs), concurrent pushes. #129
1264
1265Replace the binary and restart, and reinstall the CLI. No migration.
1266
1267* v1.9.0 — 2026-09-03
1268
1269The runner is no longer an admin, the web no longer reaches around the
1270registry, and the CLI stops paying a handshake per command.
1271
1272- =keys add --scope runner= confines a key to =runner next/log/done= and
1273  read-only git; the runner commands accept that scope or an admin. The
1274  systemd drop-in sandboxes the runner process. gitbay.org's runner now
1275  polls as a non-admin =ci= account scoped to one repository. #92
1276- The web's repo create, issue create and edit, MR edit and both comment
1277  forms dispatch the command the CLI runs, so the repository quota, the
1278  archived-repository refusal, notifications, the body format and the
1279  audit entry hold from a browser. #93
1280- The CLI shares one SSH connection per instance (=ControlMaster=, five
1281  minutes idle): a command costs a round trip instead of a handshake,
1282  0.4 s instead of 4 s from a distant laptop. =no_multiplex = true= on
1283  an instance opts out. #94
1284- A disabled account is refused on every surface, and disabling revokes
1285  its API tokens along with its sessions. #95
1286- CODEOWNERS gates whenever the file exists on the target branch, not
1287  only under =require-approvals=. #99
1288- The HTTP listeners have header and idle timeouts, and SIGTERM drains
1289  in-flight requests and SSH sessions before exit. #104 #105
1290- =git archive= runs under a two-minute deadline and a 512 MiB cap. #124
1291- Every git invocation ends option parsing before the ref, so a ref
1292  shaped like an option is a bad revision and never a flag. #135
1293- The admin noun is gated in the dispatcher as well as in each handler;
1294  registry tests cover that and =ReadsStdin=. #127
1295- An e2e test runs every =ReadOnly= command against a populated instance
1296  and fails on any row it changes. #97
1297- =http.trusted_proxies= attributes proxied API requests to the last
1298  untrusted =X-Forwarded-For= hop for rate limiting; =email add= is
1299  capped at five codes an hour per account. #136
1300- A merge request head is built in the target repository, at
1301  =refs/merge-requests/<n>/head=, so a fork's merge request has
1302  =ci/<job>= statuses for =require-checks= to gate on. A head from
1303  another repository is built without the target's secrets. #98
1304- Triggers refuse deleting a user or organization that still owns
1305  repositories, whatever path the delete takes. #136
1306- The stylesheet's fonts are served again, and directory crumbs on blob
1307  and blame pages link to the tree. #102 #103
1308- The Threat-Model wiki page covers the runner. #138
1309
1310Replace the binary and restart, reinstall the CLI, and =make
1311deploy-runner=: the runner fetches merge request refs before checkout.
1312Migrations 0032 and 0033 run on start. The daemon host needs git 2.24
1313or newer for =--end-of-options=.
1314Operators running =gitbay-runner=: give it a non-admin account with a
1315key added by =keys add --scope runner=, remove the admin key it held,
1316and =make deploy-runner= to install the sandboxed unit drop-in; an
1317admin key keeps working meanwhile.
1318
1319* v1.8.1 — 2026-09-03
1320
1321Markdown and org files render when opened.
1322
1323- A =.md=, =.markdown= or =.org= file renders on its page the way a
1324  README does on the directory page, through the same renderer with
1325  relative links resolved against the file's directory. =source= in the
1326  action bar, or =?view=source=, shows the text as before. Every other
1327  file is unchanged. #88
1328- The e2e harness waits for the HTTP and git listeners as well as SSH
1329  before a test starts; a test whose first act was an HTTP request could
1330  be refused, which failed two otherwise green runs. #91
1331
1332Replace the binary and restart. No migration.
1333
1334* v1.8.0 — 2026-09-03
1335
1336The tracker's lists narrow, labels have colours you set, and the CLI's
1337help is the server's.
1338
1339- =issue list= takes =--label=, =--assignee=, =--author= and
1340  =--milestone= (a title, or =none= for issues with no milestone);
1341  =mr list= takes =--author= and =--milestone=. The store narrows in
1342  SQL, and the web lists take the same names as query parameters and
1343  show each active filter with a link that drops it and keeps the rest.
1344  Both lists had taken =--state= and nothing else, so the web's
1345  filtering could never match the CLI's. #84
1346- =label list= shows a repository's labels with their colour and how
1347  many issues carry each; =label set <label> [--color rrggbb|'']=
1348  creates a label or sets its colour; =label remove= takes it off every
1349  issue. The colour column had existed since labels did and nothing
1350  wrote it. The hash is optional because over bare ssh a bare =#= starts
1351  a comment for the tokenizer. =issue label --add= still creates a
1352  colourless label on the fly. #85
1353- =gitbay help= with a prefix or =--json= runs the server's help, the
1354  only place flags are written down and whose JSON is the contract;
1355  bare =gitbay help= is still the local tree. Cobra's built-in help had
1356  owned the word, so =gitbay help --json= failed on an unknown flag. #86
1357
1358Replace the binary and restart, and reinstall the CLI for the help
1359change. No migration.
1360
1361* v1.7.0 — 2026-09-02
1362
1363What an open instance needs before it is open: a cap on what one
1364account can take, a way out of a browser session you no longer hold,
1365and accounts that never verified do not stay forever.
1366
1367- =limits.max_repos_per_user= caps the repositories an account owns
1368  directly; =repo create=, =fork= and =import= refuse past it with the
1369  numbers. =limits.max_bytes_per_user= caps their disk: a push may be no
1370  larger than what the owner has left, riding the same
1371  =receive.maxInputSize= as the pack cap, and is refused outright when
1372  nothing is left. Organizations are not capped. Migration 0031 adds
1373  per-account overrides, set with =admin user limits <name> [--repos
1374  n|default] [--bytes n|default]= and shown by =admin user show=. Both
1375  default to 0, unlimited, so nothing changes until set. #82
1376- =registration.pending_expiry=, a duration, removes self-registered
1377  accounts still unverified after that long, hourly and once at start,
1378  audited as =pending.expired=. Empty keeps them, as before. #82
1379- =web sessions list= shows each unexpired browser session by a short id
1380  with its creation and expiry; =web sessions revoke <id>= ends one and
1381  =--all= ends every one. SSH-only, matching the token commands, and
1382  scoped to the caller. #83
1383- A step runs in its own process group and a cancel or timeout kills the
1384  group. On a host whose =/bin/sh= is dash, killing the shell alone left
1385  its child holding the log pipe, so a cancelled build held the runner
1386  until the child finished on its own, minutes for a test suite. The
1387  wait after a kill is capped at ten seconds besides.
1388- A commit with a build still queued or running is not queued again
1389  when a fast-forward lands it; the v1.6.0 skip counted only a finished
1390  success. #90
1391
1392- =golang.org/x/crypto= v0.56.0: GO-2026-6354 and GO-2026-6355 in its
1393  =ssh= package, both reached through =ssh.NewServerConn= in the
1394  embedded SSH server; one is a denial of service on a deadlocked
1395  undecided channel.
1396
1397Replace both binaries and restart: =make deploy= for the daemon
1398(migration 0031 adds two columns to =users= on start), then
1399=make deploy-runner= for the process-group kill.
1400
1401* v1.6.1 — 2026-09-02
1402
1403A cancel reaches a build in its clone.
1404
1405- The runner honoured a cancel only in its step loop; a build cancelled
1406  during its clone or checkout ran git to completion first, which on a
1407  loaded host was long enough for the v1.6.0 test to fail on the CI
1408  host while passing locally. One =runStep= now drives the clone, the
1409  checkout and each step with the cancel signal and the deadline, and
1410  checks the signal before starting at all. The runner logs how its log
1411  session ended when that was not a cancel.
1412
1413Replace the runner: =make deploy-runner=. The daemon is unchanged from
1414v1.6.0.
1415
1416* v1.6.0 — 2026-09-02
1417
1418The v1.4.0 admin surface answered questions about accounts. This one
1419answers questions about the machinery: which runner is alive, what is
1420stuck, whether last night's backup exists, and it lets an operator stop
1421a build instead of waiting it out.
1422
1423- A build a runner claimed and never reported is failed by the
1424  scheduler's minute tick, with no runner involved. It used to happen
1425  only when some runner polled again, so a dead sole runner left its
1426  builds running forever. =GITBAY_STALE_BUILD_DEADLINE= shortens the
1427  deadline for tests. #75
1428- Runners are visible. Migration 0030 adds =runner_seen=: one row per
1429  runner account with its last poll, the =-repos= scope it asked for,
1430  and the build it holds. =admin runners= lists them, over SSH and on
1431  the host. #76
1432- =GET /healthz=: whether the database answers and which commit serves,
1433  no auth, no repository data, 503 when the database does not answer.
1434  =healthz= joins the reserved names. #77
1435- The host monitor's hourly reading carries the age of the newest full
1436  backup and database snapshot, alerting at 25 and 2 hours, and the
1437  daemon's own =/healthz= answer read through =site_url=. Both ride the
1438  journald line and the webhook body. #78
1439- =admin stats= reports =lfs_bytes=. =admin gc --lfs= scans every
1440  repository's objects for LFS pointers and removes stored objects none
1441  names, keeping anything younger than a day since git lfs uploads
1442  before it pushes. #79
1443- =admin backup --verify <archive>= reads an archive back: SQLite's
1444  integrity check on the snapshot, and the repositories it names against
1445  the archive's. A database-only archive says so. Damage or a missing
1446  repository exits non-zero. #80
1447- A commit that already passed a job on another branch is not built
1448  again when a fast-forward lands it. Merging the six-layer v1.6.0 stack
1449  had queued eighteen jobs for commits that had each just gone green.
1450  Failed or abandoned builds still re-queue. #90
1451- =build cancel <owner/name> <n>= withdraws a queued build or ends a
1452  running one. For a running build the server closes the runner's log
1453  session, the runner kills the step within seconds, and its late report
1454  changes nothing. The commit status goes back to the passed result from
1455  another build of the same commit when one exists, else reads
1456  =cancelled=. Needs write access.
1457- Deploys copy with =rsync --partial=, so a transfer the host's load
1458  stalled resumes, and =make deploy-runner= installs a systemd drop-in
1459  (=Nice=10=, =CPUWeight=30=, =IOWeight=30=) so a build never starves the
1460  host's sshd again.
1461
1462Replace both binaries and restart: =make deploy= for the daemon, then
1463=make deploy-runner= for the runner, which carries its half of running-
1464build cancellation and installs the drop-in. Migration 0030 adds the
1465=runner_seen= table on start. The monitor change ships in
1466=deploy/cloud-init.yaml=; an existing host takes it by hand.
1467
1468* v1.5.0 — 2026-09-02
1469
1470Merge requests stack.
1471
1472- A merge request whose target is the source branch of another open
1473  merge request in the same repository is stacked on it. Nothing is
1474  stored and no flag exists; the forge reads the stack from the
1475  branches. =mr create= says =stacked on !A= when it applies, =mr show=
1476  carries =stacked_on= and =stacked=, =mr list= rows carry =stacked_on=,
1477  and the page says both directions in the header. #87
1478- When the lower merge request merges, everything stacked on it is
1479  retargeted onto what it merged into, with a system comment naming the
1480  merge and its reviews kept: after a fast-forward or merge commit the
1481  diff against the new target is the diff they were of. A squash or
1482  rebase merge under a stack is refused, naming the stack, since it
1483  would rewrite the commits the stack builds on.
1484- The first stack merged on gitbay.org was the six merge requests of
1485  v1.6.0, bottom-up, with no =mr retarget= typed. The wiki's
1486  Stacked-MRs page walks through it.
1487
1488Replace the binary and restart. No migration.
1489
1490* v1.4.0 — 2026-09-01
1491
1492Until now the instance had one operator surface: root on the host. Every
1493question about the instance itself — who is on it, what is stuck, what a
1494spam repository is doing — needed a shell on port 2222. This release
1495gives an instance admin the same answers over SSH, and one page on the
1496web.
1497
1498- =admin user list= pages accounts by username with
1499  =--state active|pending|disabled|admin=, each row carrying its state
1500  and =last_seen=, the newest use of any of its SSH keys or API tokens.
1501  =admin user show <name>= adds the keys with their last use, each
1502  address with how it was verified, PGP keys, org roles, owned
1503  repository count, API token names and live browser sessions. Both are
1504  SSH-only and refused to non-admins, like =audit=. #69
1505- =admin user promote|demote=. The only way to admin was
1506  =admin user create --admin=; an existing account could not be raised
1507  and an admin could not step down. Demoting the last admin is refused
1508  inside the transaction that counts them. The host-local twin is the
1509  recovery path when no admin key is reachable. #70
1510- Repository overrides for moderation: =admin repo list= with size and
1511  last push, and =admin repo archive|unarchive|visibility|delete=. Policy
1512  still knows nothing about instance admin — a private repository
1513  answers not-found to an admin as before — so each override skips the
1514  access check explicitly and writes its own =admin repo.<action>= audit
1515  row. #71
1516- =gitbayd admin= dispatches into the registry. User create, disable,
1517  enable and delete, email verify, invite and stats were reimplemented on
1518  the host; they now live in the registry, SSH-only and admin-gated, and
1519  the host binary runs them as the host — an admin context with no
1520  account behind it, so its audit rows say =source: host= where a
1521  session says the key fingerprint. Invite and stats gain an SSH twin by
1522  the same move. =backup=, =gc= and the backfills stay host-local. #72
1523- =audit= filters: =--actor <user>= or =--actor -= for actorless rows,
1524  =--action <prefix>=, and =--since= as a duration (=30m=, =24h=, =7d=)
1525  or a date. =gitbayd admin audit= takes the same flags and =--json=. #73
1526- =dashboard= carries a =queues= block for admins: per worker —
1527  webhooks, mail, mirrors, builds, dependency checks — the pending,
1528  retrying and dead-lettered counts, the oldest pending age, and the
1529  retrying or failed rows themselves, capped at twenty each. The mail
1530  queue was readable nowhere before. =/admin= renders the block by
1531  dispatching =dashboard=; non-admins get a 404 and no rail link. #74
1532- =gitbayd admin config show= prints the configuration in effect as
1533  TOML, defaults filled in and =smtp_pass= redacted, so a support
1534  question starts from what runs rather than what was written. #81
1535- Build badges are served as PNG at =badge/build.png= as well as SVG,
1536  for places that will not render SVG.
1537- Host monitoring writes its reading to journald on every run and exits
1538  non-zero on an alert, so an unset webhook no longer looks like a
1539  healthy host; it reads the ACME cache where it actually lives and
1540  reports the soonest expiry. govulncheck runs as its own CI job. The
1541  database is snapshotted hourly by =gitbay-db-backup.timer=, keeping 48,
1542  alongside the nightly full archive; archives inherit the database's
1543  mode rather than the umask default. #28
1544- A runner whose log stream drops no longer fails the build it was
1545  recording. #67
1546- =go.yaml.in/yaml/v3= and =golang.org/x/net= bumped. #60
1547
1548Replace the binary and restart. No migration. The =gitbay-db-backup=
1549timer and the monitor changes ship in =deploy/cloud-init.yaml= for new
1550hosts; an existing host takes them from there by hand.
1551
1552* v1.3.0 — 2026-08-31
1553
1554A runner took every repository's work, which decided where you could run
1555one.
1556
1557- =runner next= takes optional =owner/name= arguments and =gitbay-runner=
1558  takes =-repos=, so a runner claims builds only for the repositories it
1559  names. Naming none is the old behaviour, so an existing runner is
1560  unaffected. This is what makes a runner outside the server practical: one
1561  on a machine that should build a single project no longer picks up a
1562  build belonging to someone else, which with open registration need not be
1563  anyone the operator knows. The scoping is what the runner asks for rather
1564  than an ACL the server holds over it — a runner account is admin by
1565  necessity, so the boundary is the operator choosing how to start it. #66
1566
1567Replace the binary and restart. Runners want the new binary too, though an
1568old one keeps working unscoped.
1569
1570* v1.2.1 — 2026-08-31
1571
1572Merging landed commits without running anything.
1573
1574- A merge moves the target ref with a direct ref update, so it never
1575  reached post-receive and none of the ref-update work fired: no =push=
1576  event for webhooks to subscribe to, and no builds. Pushing a commit to a
1577  branch ran the whole =.gitbay/ci.yml=; merging the identical commit ran
1578  nothing. Both now happen in the merge path, with the build queueing
1579  shared between it and post-receive rather than living in one of them.
1580  #65
1581
1582Replace the binary and restart.
1583
1584* v1.2.0 — 2026-08-31
1585
1586A merge request said what its state was and almost nothing about when it
1587got there. It now keeps time.
1588
1589- Reviews and checks carry the moment they last said something, on the
1590  merge request page and in =mr show=. A =ci/<job>= check also reports how
1591  long its build ran, so the timing of a run is readable without opening
1592  it. Checks posted through =status set= have no build and report only the
1593  time. !137
1594- A merged or closed merge request names who resolved it and when. The
1595  header stated "X wants to merge" whatever the state; it now says "X
1596  merged A into main on <date>", or "closed this without merging", and
1597  drops the claim entirely for a row that carries no stamp rather than
1598  inventing a time.
1599- =mr show= gains =merged_at=/=merged_by= and =closed_at=/=closed_by=, a
1600  =created_at= per review, and =updated_at= plus =duration= per check, in
1601  both JSON and text. Additive: nothing existing changed shape.
1602- The iOS client renders all of it as of krz/gitbay-ios!37.
1603
1604Replace the binary and restart. Migration 0029 adds four columns to
1605=merge_requests= and backfills the merge stamp for merge requests already
1606merged, reading the =mr.merged= events. A merge with no such event to read
1607— an import, or a row older than its events — keeps no stamp, and every
1608surface says nothing about when it happened rather than guessing.
1609
1610* v1.1.0 — 2026-08-31
1611
1612Every release until now answered questions. This one notices something
1613on its own: that a repository's dependencies have moved, and says so
1614without being asked.
1615
1616- Dependency update checks, opt-in per repository. A daemon worker reads
1617  the manifests on the default branch, asks the ecosystem's registry what
1618  the current release is, and maintains one issue per repository — opened
1619  when something falls behind, rewritten when the set changes, closed once
1620  nothing is behind. No package manager runs, so it needs no CI runner and
1621  no configuration beyond turning it on. #58
1622  - =go.mod= against proxy.golang.org, =package.json= with
1623    =package-lock.json= against npm, =Cargo.toml= with =Cargo.lock=
1624    against crates.io, =requirements.txt= and =pyproject.toml= against
1625    PyPI. A lockfile wins where both exist. A requirement naming a set
1626    rather than a release — a range, a wildcard, a git or path source — is
1627    skipped, since a range that already admits the newest release is not
1628    news.
1629  - =repo deps enable|disable|status=, a toggle on the repository settings
1630    page, and the same three over the JSON API.
1631  - Off by default, because checking a private repository tells a public
1632    registry what it depends on. That is the owner's disclosure to make.
1633    =[deps] check_interval_hours= sets the cadence, default 24.
1634  - The issue is authored by a =gitbay-bot= account, so the existing
1635    notification mail reaches the repository's owner rather than excluding
1636    them as the actor. Its table is padded to its columns, which a
1637    renderer ignores and a mail client needs. #61
1638- =help= takes a prefix — =help mr= narrows the registry to one noun — and
1639  every command now documents its arguments, so the server answers "what
1640  are the flags" instead of being guessed at. #57
1641- Web: settings rows end in one column of controls, checkboxes drawn at
1642  the height of the inputs and buttons they sit beside #59; an added line
1643  keeps its leading dash in the diff; a contributor's several verified
1644  addresses collapse to one row #56.
1645
1646Replace the binary and restart. Migration 0028 adds two tables and, when
1647the name is free, the =gitbay-bot= account. An instance already using that
1648name for a user or an org keeps what it has: the account is not created,
1649and dependency checks report that as the reason they cannot open an issue
1650rather than the migration failing and the daemon not starting. #64
1651
1652* v1.0.1 — 2026-08-30
1653
1654Two CI fixes found by running orgo's release pipeline on this instance.
1655
1656- A runner killed between claiming a build and reporting it left the build
1657  =running= forever, and the commit's =ci/<job>= status pending with it.
1658  =runner next= now fails builds past a 90-minute deadline — longer than the
1659  runner's own =-timeout= — and resolves their commit status. #53
1660- =gitbay keys add= and =gitbay repo deploy-key add= take stdin as a bare
1661  =< key.pub=, but only forwarded it when =--file -= appeared in the
1662  arguments, so both sent an empty body and rejected input the SSH API
1663  accepts. #55
1664
1665Replace the binary and restart.
1666
1667* v1.0.0 — 2026-08-26
1668
1669The web finishes the job #35 set it: reading, reviewing and responding,
1670with the CLI still the complete interface. Every capability exists over
1671SSH, every web write dispatches the same control command, and anything
1672whose input is a credential stays on the command line. The [[https://gitbay.org/krz/gitbay/wiki/Parity][Parity]] page in
1673the wiki is the maintained matrix and says which rows are deliberately
1674CLI-only.
1675
1676- Diff view: one foldable section per file with line-number gutters,
1677  per-file stats, rename and binary handling, and syntax highlighting
1678  run per hunk per side so multi-line constructs lex as real code.
1679  Commit and merge request pages share it; review threads anchor
1680  inline.
1681- Repository facts on the code page: commit, branch and tag counts,
1682  detected license, latest release, build status, a language census by
1683  tracked bytes, and contributors resolved to accounts by verified
1684  email. All derived from git at render time.
1685- Account settings on the web: SSH keys with scope, OpenPGP keys, and
1686  email addresses. Public keys are the only credential-shaped input the
1687  web accepts — they are not secret, and a new user needs one
1688  registered before the CLI is reachable to them. Token minting and
1689  account export stay SSH-only.
1690- Organizations are run from their page: membership and roles, teams,
1691  team members, and team repository grants, for org admins.
1692- Commit log shows each commit's combined check status and gains a path
1693  filter, so per-file history is reachable without editing the URL.
1694- Issue references from commit messages read "referenced in commit
1695  <sha> by <author>", linking the author when their email is verified
1696  here.
1697- The rail's focus ring uses the shell's own mark: the light scheme's
1698  accent was a dark blue ring on a black rail.
1699
1700No migrations. No new config.
1701
1702Upgrading from v0.5.0 is replace-the-binary-and-restart.
1703
1704* v0.5.0 — 2026-08-26
1705
1706A design pass and a parity pass. The web stops being a read-only
1707mirror of the CLI without becoming the place you are expected to work.
1708
1709- New design: a black shell with a persistent left rail carrying
1710  cross-repo state (pinned repos, review queue), the repo header
1711  rendered identically on every tab so navigation never moves, sharp
1712  lines, self-hosted IBM Plex, and code blocks that read against both
1713  color schemes. Tree listings sort directories first and carry each
1714  file's last commit; diffs, inputs and controls were reworked to
1715  match.
1716- Web parity with the CLI, dispatched through the same command
1717  registry the CLI and JSON API use — every web write is the
1718  equivalent =gitbay= command with =--source web=:
1719  - merge requests: review, resolve threads, merge, close, and open a
1720    new MR from the browser
1721  - issues: state, labels, assignees, milestones
1722  - repositories: settings, branch protection, visibility
1723  - releases: create and edit; builds: trigger a job
1724  Commands marked SSH-only still refuse over the web: build secrets,
1725  mirror tokens, domain claims, token minting, deletion and transfer.
1726- A dashboard that answers "what needs me": review queue, assigned
1727  issues, pinned repos, and an activity feed. Author names resolve to
1728  accounts and link to profiles wherever commits appear.
1729- Build status badges at =/{owner}/{repo}/badge/build.svg= for public
1730  repos.
1731- =[web] title= sets the instance's display name, separate from the
1732  hostname commands are pasted with.
1733- =make build/test/deploy= targets.
1734- Fixes: the mobile tab strip scrolls sideways only, long commit
1735  subjects no longer overflow on narrow screens, the shell fills the
1736  viewport with the line-length cap moved onto prose, and the account
1737  cell lines up with the page footer.
1738
1739No migrations. New config: =[web] title=.
1740
1741* v0.4.0 — 2026-08-25
1742
1743- Git LFS: standard clients work over both transports.
1744  =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
1745  included; download needs read, upload write), minting stateless
1746  repo- and operation-scoped tokens for the batch API and basic
1747  transfers. Anonymous HTTPS downloads for public repos; uploads
1748  verified against size and sha256 before landing. Storage is
1749  content-addressed under =[lfs] root= behind a small interface an
1750  S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
1751  objects (512MB default).
1752- Build failures mail the repo's notify targets with the log tail and
1753  build link — failed scheduled jobs reach an inbox.
1754- =release edit= updates a release's title and notes (absent flags
1755  keep their field); omaha-style CI note rebuilds work again.
1756- Syntax highlighting follows the color scheme: class-based chroma
1757  with light and dark palettes, the light-pinned code background is
1758  gone, and markdown fences and org src blocks highlight too. The UGC
1759  sanitizer admits only chroma's token-code classes.
1760
1761No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
1762
1763* v0.3.0 — 2026-08-25
1764
1765- CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=
1766  over SSH (admin-only runner protocol; statuses feed =require-checks=).
1767  Per-repo secrets set over stdin and injected into build environments;
1768  cron schedules (server-local time) and tag-glob triggers, mutually
1769  exclusive per job; =build list/show/log/trigger= and a builds tab.
1770- Pages: public repos' =pages= branches served on =<owner>.<domain>=
1771  (=[pages] domain=), custom domains with DNS TXT ownership challenges
1772  and 7-day expiry for pending claims, per-subdomain on-demand ACME.
1773- Wikis (=.wiki= companion repos, access mirrors the parent) and teams
1774  within orgs (members-role scoping, per-repo team grants).
1775- Activity graphs on user and org pages, backfillable
1776  (=admin backfill-activity=); commits attributed by verified author
1777  email, deduped by sha.
1778- MR pages list the commits the MR carries; =mr show= gains a commits
1779  section.
1780- Per-file history: =?path== on the web log, =--path= on =repo log=,
1781  history link on blob pages.
1782- Mirror status surfaced in =repo show= and the repo header
1783  (admin-only), with sync errors visible; tag-only pushes now schedule
1784  mirror syncs.
1785- Rendering: GFM tables/strikethrough/autolinks/task lists, blob image
1786  previews, raw serves images with real content types (README images
1787  render under nosniff), 0BSD license recognition, repo website links,
1788  compact dashboard pins.
1789- =admin user delete= for accounts that anchor nothing, with named
1790  blockers otherwise.
1791- Fixes: wiki pages no longer overflow on mobile (iOS font-inflation
1792  trigger), GHSA-free deps, secret values pipe correctly through the
1793  CLI.
1794
1795Migrations 0020-0025 apply on start. New config: =[pages] domain=.
1796The runner is a new binary (=gitbay-runner=); see the wiki's Admin
1797guide for setup. Stress-tested against an import of git.git (82k
1798commits): see the wiki's Performance page.
1799
1800* v0.2.0 — 2026-08-24
1801
1802- Deploy keys: repo-bound CI keys (=repo deploy-key=), ro/rw, rename- and
1803  transfer-proof.
1804- Commit statuses (=status set/list=), combined state on MR pages, and a
1805  =require-checks= merge gate.
1806- Email notifications for issue and MR activity (participants with
1807  verified addresses; never the actor).
1808- Inline review threads on MR diffs (=mr diff-comment/threads/resolve=),
1809  stale on force-push, =require-resolved= merge gate.
1810- Required approvals with CODEOWNERS (=require-approvals=; latest review
1811  wins, author excluded) and a =require-resolved= gate; merge gate order
1812  is checks → approvals → CODEOWNERS → resolved threads → signatures.
1813- Web design revamp: token-based stylesheet (light+dark), wordmark and
1814  favicon, aligned layout grid, card-based listings, designed 404,
1815  mobile pass.
1816- Cross-references and mentions: =#N=, =!N=, =owner/name#N=, =@user=
1817  autolink in issue/MR text, viewer-aware for private repos.
1818- Archived repositories (read-only with badge) and repo topics.
1819- Blame view with signature-aware attribution and 1000-line pages.
1820- Repository search (name/description/topic) and per-repo code search
1821  (=repo grep=, web search tab); blob line anchors.
1822- Homepage: dashboard for logged-in users (pinned repos via =repo pin=,
1823  open MRs and issues involving you), landing page for visitors, full
1824  public listing at =/explore=; MR diffs collapsed by default.
1825- Milestones (=milestone create/list/close=, =issue/mr milestone=) with
1826  web progress; issue templates from =.gitbay/issue-template*.md=
1827  (CLI =$EDITOR= prefill and web form).
1828- Issue actions from commit messages landing on the default branch:
1829  =closes/fixes/resolves #N= closes, bare =#N= leaves a reference
1830  comment; once per issue+commit.
1831- Vanity Go imports: =[go_import]= config serves go-import meta tags, so
1832  =go install gitbay.org/gitbay/cmd/...@latest= works.
1833- Release script: =deploy/release.sh <tag>= builds reproducible
1834  linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
1835- Repository maintenance: =admin gc= (repack/prune, per-repo sizes),
1836  =admin stats= (counts + disk usage), weekly =gitbay-gc.timer=.
1837- Releases: tag-anchored notes and binary assets (=release= commands,
1838  assets over SSH stdin/stdout, web releases tab with downloads).
1839- GitHub history import: =repo import-issues= brings issues and PRs
1840  (as merged/closed MRs) with comments, labels, and state, attributed
1841  inline and resumable.
1842- Push and pull mirroring (=repo mirror=): background sync, read-only
1843  pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
1844- Web signup at =/register= for open and invite instances.
1845- Audit log (=audit=, =gitbayd admin audit=): every mutating command
1846  with source key fingerprint, registrations, force-pushes, auth
1847  failures. Hardening: per-IP auth-failure throttling
1848  (=ssh_auth_rate=), =max_pack_bytes= enforced, =admin user
1849  disable/enable=.
1850- Account migration: =gitbay migrate --from <host>= (bundle
1851  export/replay + client-side git mirror); =gitbay auth export= as a
1852  user-level backup.
1853- Editable issues and MRs (=issue edit=, =mr edit=, web forms).
1854- Commit references appear as system messages with linked shas.
1855- Design: top nav, repo listing rows (topics, license, last updated),
1856  file table headers, README relative-link resolution, branch
1857  dropdown, web pinning, org owner picker, label filters, linked
1858  usernames and commit parents, =/privacy= page, blue accent.
1859
1860Upgrade notes: migrations 0006–0019 apply on start. No config changes
1861required; =[go_import]=, =[mirrors]=, =web.privacy_notice=, and
1862=web.mode = "accounts"= are opt-in.
1863
1864* v0.1.0 — 2026-08-24
1865
1866First tagged release: the complete CLI-first forge. SSH control plane
1867(bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues,
1868merge requests (ff/merge/squash/rebase with signature policy), OpenPGP
1869and SSHSIG verification with retroactive re-verification, orgs, repo
1870import, web UI (view-only or accounts mode), registration with invites
1871and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups,
1872ACME TLS, systemd deployment.