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