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