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