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