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