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