CHANGELOG.org

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