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