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