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