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