CHANGELOG.org

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