CHANGELOG.org

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