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