CHANGELOG.org

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