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