CHANGELOG.org

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