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