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