CHANGELOG.org

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