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