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