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