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