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.12.0 — 2026-09-04
  8
  9The store and the push path. Dashboard queries walk an index instead of
 10sorting the table, concurrent writers wait instead of failing, expired
 11rows are swept, and a large first push no longer forks a process per
 12commit.
 13
 14- Every dashboard list scanned its table and sorted the result to take
 15  fifty rows. Reachability is correlated subqueries and cannot be
 16  indexed; the index supplies the =ORDER BY= instead, so the walk stops
 17  at =LIMIT=. On 20k issues and 20k merge requests: open issues 11.8ms
 18  to 0.8ms, open merge requests 12.1ms to 0.8ms, the review queue 15.5ms
 19  to 0.3ms, assigned issues 10.6ms to 0.04ms. The last of those also
 20  drives from =issue_assignees= rather than testing =EXISTS= against
 21  every issue. #137
 22- Concurrent writers serialise rather than failing. Every transaction in
 23  the store writes, and a deferred one takes the write lock at its first
 24  write, by which point another may hold it; SQLite answers
 25  =SQLITE_BUSY= and does not run the busy handler for that case, so
 26  =busy_timeout= could not help. Measured with eight concurrent
 27  read-then-write transactions, 44% of them failed. Beginning immediate
 28  takes the lock up front, where the timeout applies. #121
 29- =repo settings= updates no longer overwrite each other.
 30  =settings_json= is one blob, and every caller read it off a repository
 31  loaded earlier, changed a field and wrote it all back; two admins at
 32  once and the later write put back what it had read for the other's
 33  field. The read and the write happen together now, under one
 34  immediate transaction. #123
 35- Expired sessions and tokens are swept, and =[retention]= caps how long
 36  the audit log, the activity feed, webhook deliveries and the mail
 37  queue keep a row. Unset means forever, which is what every existing
 38  instance gets. #122
 39- The audit entry records flag names without their values. Secrets never
 40  reached argv — they travel on stdin — but prose did: =--body <the
 41  whole issue>= was stored verbatim, in a table nothing pruned, for a
 42  repository that may be private. Identifiers are positional and
 43  survive. #122
 44- pre-receive on a require-signed repository forked a =cat-file= per
 45  incoming commit and built one JSON message holding the whole push. A
 46  50k-commit first push forked 50k processes and held the history in
 47  memory twice. One =cat-file --batch= serves the push now, and the
 48  daemon verifies each commit as it arrives. #100
 49- The payloads other surfaces decode are named types in =control=. httpd
 50  had its own copies of what the build, profile and dashboard commands
 51  emit, so a field added to a command was silently absent on the page.
 52  #126
 53
 54Migration 0035 adds three indexes; it runs on daemon start.
 55
 56Two changes in behaviour rather than configuration. A heavily contended
 57write now blocks for up to =busy_timeout= (five seconds) instead of
 58returning an error immediately — waiting is the point, but a caller that
 59treated the error as normal will see a pause instead. And anything
 60parsing =audit --json= for command arguments will find flag values gone;
 61the flag names and the positional arguments are still there.
 62
 63* v1.11.0 — 2026-09-04
 64
 65The web catches up with the rest of the forge: search across the
 66instance, a notification inbox, a compare view, linkable diff lines,
 67and a pass over contrast, heading structure and the stylesheet.
 68
 69- Notifications are no longer mail or nothing. An =inbox= table holds a
 70  row per recipient whether or not the instance has SMTP;
 71  =notifications list= reads it, unread by default, and =notifications
 72  read <id>... | --all= clears it. =repo watch= adds you to a
 73  repository's notifications and =repo unwatch= mutes it, with a mute
 74  beating every other reason to be told, including owning the
 75  repository or having written the thread. The unread count rides on
 76  =dashboard= and in the web rail. #113
 77- =search= matches repository paths, descriptions and topics, and issue
 78  and merge request titles, across everything the caller can read;
 79  =/search= renders it with a field in the rail on every page, and an
 80  anonymous visitor gets the public rows from the same query. Titles
 81  only — body search is #114. #118
 82- =/{owner}/{repo}/compare/{a}...{b}= shows what one ref adds on top of
 83  another. Diff rows, files and review threads carry ids, so a line can
 84  be linked to. The issue and merge request lists page at fifty with
 85  the cursors the commands already emit. #118
 86- CODEOWNERS gating is a setting rather than a file that happens to
 87  exist: =repo settings require-codeowners <owner/name> on|off=, off by
 88  default, still independent of =require-approvals=. A repository can
 89  carry the file as documentation of who to ask without it gating
 90  merges. #142
 91- A failed form action's reason rides a one-shot cookie instead of
 92  =?e=<message>=, so it no longer survives a reload or lands in
 93  history. #119
 94- A diff cut at 4 MiB cuts on a line boundary and says so, the
 95  diffstat says its counts are partial, and a merge request's commit
 96  list says "first 100 of N". #117
 97- Page templates parse once with the layout at start-up, so a template
 98  that does not parse fails the process rather than the first visit to
 99  its page. #116
100- Markdown headings carry ids, matching org pages, and the stylesheet
101  serves a hash ETag with a day's lifetime and answers a matching
102  =If-None-Match= with 304. #132
103- Dark-mode buttons carry a visible edge (a 1 px border was 1.3:1
104  against the 3:1 non-text contrast floor), and a stored label colour
105  is held between 0.12 and 0.28 relative luminance so it clears 3:1 on
106  both grounds while keeping its hue. #120
107- Accessibility: the pin star is decoration and the word carries the
108  meaning, the refs and release asset tables have scoped column
109  headers, state filters carry =aria-current= rather than marking the
110  active one by colour alone, and a rendered README or wiki page's
111  headings move down one level so they sit under the page's own. #133
112- The stylesheet drops rules no template reaches, folds two off-scale
113  values onto the type scale, and resolves the classes templates asked
114  for and it never defined. #131
115- On a phone the tab bar wraps to a second row instead of scrolling
116  sideways with its scrollbar hidden, and the landing page says in
117  three sections what a reader, a writer and a reviewer can do. #134
118
119Migration 0034 adds =inbox= and =repo_watchers=; it runs on daemon
120start. Reinstall the CLI for =search=, =notifications= and =repo
121watch/unwatch=.
122
123Two upgrade notes beyond replacing the binary. A repository that
124relied on a CODEOWNERS file gating merges by its presence alone loses
125that gate until =require-codeowners= is set: nothing back-fills it,
126since the database cannot say which branches carry the file. And
127=search= and =notifications= are now reserved top-level routes, so a
128user or organization already holding either name keeps it but its
129profile page is shadowed by the route.
130
131* v1.10.0 — 2026-09-04
132
133Every command parses its arguments the same way, the web answers by
134exit code, and a restart no longer waits on idle connections.
135
136- One flag parser for every command: an unknown flag, a missing value or
137  too many arguments is exit 2 with the command's usage, everywhere.
138  =mr review --approve --bogus= used to report repository =--bogus= as
139  not found. #96
140- =--json= is honoured by the dispatcher's own refusals, so a script told
141  no gets the envelope. #109
142- A store failure is exit 1 and not-found is exit 3; both used to be
143  usage errors. #107
144- Web form actions answer by exit code: the 404 page for a thing that
145  does not exist, the page with the message for anything else. #106
146- Inside a clone, =gitbay mr create= takes the checked-out branch as
147  =--source=; =gitbay <noun> --help= is the server's reference for the
148  noun, flags included. #101 #130
149- Shutdown closes idle SSH connections at once and drains only sessions
150  mid-command; a store failure during key lookup no longer counts as a
151  bad key against the auth limiter; the CLI says on ssh's exit 255 that
152  a burst may have tripped it. #141
153- A merge request head the target already contains is recorded as
154  merged instead of refused; a fork is created with its parent in one
155  insert; a failed transfer revert is reported; the repository quota is
156  checked under a lock. #108
157- Issues and merge requests share their comment, reference and
158  author-or-write code. #110
159- The payloads the web and clients decode are named types: =Created=,
160  =MRCreated=, =IssueShow=, =MRShow=. JSON unchanged. #126
161- Tests: parse failures per command, non-ASCII paths (which found
162  =ls-tree= returning octal escapes, fixed with =core.quotepath=off= for
163  every git the server runs), concurrent pushes. #129
164
165Replace the binary and restart, and reinstall the CLI. No migration.
166
167* v1.9.0 — 2026-09-03
168
169The runner is no longer an admin, the web no longer reaches around the
170registry, and the CLI stops paying a handshake per command.
171
172- =keys add --scope runner= confines a key to =runner next/log/done= and
173  read-only git; the runner commands accept that scope or an admin. The
174  systemd drop-in sandboxes the runner process. gitbay.org's runner now
175  polls as a non-admin =ci= account scoped to one repository. #92
176- The web's repo create, issue create and edit, MR edit and both comment
177  forms dispatch the command the CLI runs, so the repository quota, the
178  archived-repository refusal, notifications, the body format and the
179  audit entry hold from a browser. #93
180- The CLI shares one SSH connection per instance (=ControlMaster=, five
181  minutes idle): a command costs a round trip instead of a handshake,
182  0.4 s instead of 4 s from a distant laptop. =no_multiplex = true= on
183  an instance opts out. #94
184- A disabled account is refused on every surface, and disabling revokes
185  its API tokens along with its sessions. #95
186- CODEOWNERS gates whenever the file exists on the target branch, not
187  only under =require-approvals=. #99
188- The HTTP listeners have header and idle timeouts, and SIGTERM drains
189  in-flight requests and SSH sessions before exit. #104 #105
190- =git archive= runs under a two-minute deadline and a 512 MiB cap. #124
191- Every git invocation ends option parsing before the ref, so a ref
192  shaped like an option is a bad revision and never a flag. #135
193- The admin noun is gated in the dispatcher as well as in each handler;
194  registry tests cover that and =ReadsStdin=. #127
195- An e2e test runs every =ReadOnly= command against a populated instance
196  and fails on any row it changes. #97
197- =http.trusted_proxies= attributes proxied API requests to the last
198  untrusted =X-Forwarded-For= hop for rate limiting; =email add= is
199  capped at five codes an hour per account. #136
200- A merge request head is built in the target repository, at
201  =refs/merge-requests/<n>/head=, so a fork's merge request has
202  =ci/<job>= statuses for =require-checks= to gate on. A head from
203  another repository is built without the target's secrets. #98
204- Triggers refuse deleting a user or organization that still owns
205  repositories, whatever path the delete takes. #136
206- The stylesheet's fonts are served again, and directory crumbs on blob
207  and blame pages link to the tree. #102 #103
208- The Threat-Model wiki page covers the runner. #138
209
210Replace the binary and restart, reinstall the CLI, and =make
211deploy-runner=: the runner fetches merge request refs before checkout.
212Migrations 0032 and 0033 run on start. The daemon host needs git 2.24
213or newer for =--end-of-options=.
214Operators running =gitbay-runner=: give it a non-admin account with a
215key added by =keys add --scope runner=, remove the admin key it held,
216and =make deploy-runner= to install the sandboxed unit drop-in; an
217admin key keeps working meanwhile.
218
219* v1.8.1 — 2026-09-03
220
221Markdown and org files render when opened.
222
223- A =.md=, =.markdown= or =.org= file renders on its page the way a
224  README does on the directory page, through the same renderer with
225  relative links resolved against the file's directory. =source= in the
226  action bar, or =?view=source=, shows the text as before. Every other
227  file is unchanged. #88
228- The e2e harness waits for the HTTP and git listeners as well as SSH
229  before a test starts; a test whose first act was an HTTP request could
230  be refused, which failed two otherwise green runs. #91
231
232Replace the binary and restart. No migration.
233
234* v1.8.0 — 2026-09-03
235
236The tracker's lists narrow, labels have colours you set, and the CLI's
237help is the server's.
238
239- =issue list= takes =--label=, =--assignee=, =--author= and
240  =--milestone= (a title, or =none= for issues with no milestone);
241  =mr list= takes =--author= and =--milestone=. The store narrows in
242  SQL, and the web lists take the same names as query parameters and
243  show each active filter with a link that drops it and keeps the rest.
244  Both lists had taken =--state= and nothing else, so the web's
245  filtering could never match the CLI's. #84
246- =label list= shows a repository's labels with their colour and how
247  many issues carry each; =label set <label> [--color rrggbb|'']=
248  creates a label or sets its colour; =label remove= takes it off every
249  issue. The colour column had existed since labels did and nothing
250  wrote it. The hash is optional because over bare ssh a bare =#= starts
251  a comment for the tokenizer. =issue label --add= still creates a
252  colourless label on the fly. #85
253- =gitbay help= with a prefix or =--json= runs the server's help, the
254  only place flags are written down and whose JSON is the contract;
255  bare =gitbay help= is still the local tree. Cobra's built-in help had
256  owned the word, so =gitbay help --json= failed on an unknown flag. #86
257
258Replace the binary and restart, and reinstall the CLI for the help
259change. No migration.
260
261* v1.7.0 — 2026-09-02
262
263What an open instance needs before it is open: a cap on what one
264account can take, a way out of a browser session you no longer hold,
265and accounts that never verified do not stay forever.
266
267- =limits.max_repos_per_user= caps the repositories an account owns
268  directly; =repo create=, =fork= and =import= refuse past it with the
269  numbers. =limits.max_bytes_per_user= caps their disk: a push may be no
270  larger than what the owner has left, riding the same
271  =receive.maxInputSize= as the pack cap, and is refused outright when
272  nothing is left. Organizations are not capped. Migration 0031 adds
273  per-account overrides, set with =admin user limits <name> [--repos
274  n|default] [--bytes n|default]= and shown by =admin user show=. Both
275  default to 0, unlimited, so nothing changes until set. #82
276- =registration.pending_expiry=, a duration, removes self-registered
277  accounts still unverified after that long, hourly and once at start,
278  audited as =pending.expired=. Empty keeps them, as before. #82
279- =web sessions list= shows each unexpired browser session by a short id
280  with its creation and expiry; =web sessions revoke <id>= ends one and
281  =--all= ends every one. SSH-only, matching the token commands, and
282  scoped to the caller. #83
283- A step runs in its own process group and a cancel or timeout kills the
284  group. On a host whose =/bin/sh= is dash, killing the shell alone left
285  its child holding the log pipe, so a cancelled build held the runner
286  until the child finished on its own, minutes for a test suite. The
287  wait after a kill is capped at ten seconds besides.
288- A commit with a build still queued or running is not queued again
289  when a fast-forward lands it; the v1.6.0 skip counted only a finished
290  success. #90
291
292- =golang.org/x/crypto= v0.56.0: GO-2026-6354 and GO-2026-6355 in its
293  =ssh= package, both reached through =ssh.NewServerConn= in the
294  embedded SSH server; one is a denial of service on a deadlocked
295  undecided channel.
296
297Replace both binaries and restart: =make deploy= for the daemon
298(migration 0031 adds two columns to =users= on start), then
299=make deploy-runner= for the process-group kill.
300
301* v1.6.1 — 2026-09-02
302
303A cancel reaches a build in its clone.
304
305- The runner honoured a cancel only in its step loop; a build cancelled
306  during its clone or checkout ran git to completion first, which on a
307  loaded host was long enough for the v1.6.0 test to fail on the CI
308  host while passing locally. One =runStep= now drives the clone, the
309  checkout and each step with the cancel signal and the deadline, and
310  checks the signal before starting at all. The runner logs how its log
311  session ended when that was not a cancel.
312
313Replace the runner: =make deploy-runner=. The daemon is unchanged from
314v1.6.0.
315
316* v1.6.0 — 2026-09-02
317
318The v1.4.0 admin surface answered questions about accounts. This one
319answers questions about the machinery: which runner is alive, what is
320stuck, whether last night's backup exists, and it lets an operator stop
321a build instead of waiting it out.
322
323- A build a runner claimed and never reported is failed by the
324  scheduler's minute tick, with no runner involved. It used to happen
325  only when some runner polled again, so a dead sole runner left its
326  builds running forever. =GITBAY_STALE_BUILD_DEADLINE= shortens the
327  deadline for tests. #75
328- Runners are visible. Migration 0030 adds =runner_seen=: one row per
329  runner account with its last poll, the =-repos= scope it asked for,
330  and the build it holds. =admin runners= lists them, over SSH and on
331  the host. #76
332- =GET /healthz=: whether the database answers and which commit serves,
333  no auth, no repository data, 503 when the database does not answer.
334  =healthz= joins the reserved names. #77
335- The host monitor's hourly reading carries the age of the newest full
336  backup and database snapshot, alerting at 25 and 2 hours, and the
337  daemon's own =/healthz= answer read through =site_url=. Both ride the
338  journald line and the webhook body. #78
339- =admin stats= reports =lfs_bytes=. =admin gc --lfs= scans every
340  repository's objects for LFS pointers and removes stored objects none
341  names, keeping anything younger than a day since git lfs uploads
342  before it pushes. #79
343- =admin backup --verify <archive>= reads an archive back: SQLite's
344  integrity check on the snapshot, and the repositories it names against
345  the archive's. A database-only archive says so. Damage or a missing
346  repository exits non-zero. #80
347- A commit that already passed a job on another branch is not built
348  again when a fast-forward lands it. Merging the six-layer v1.6.0 stack
349  had queued eighteen jobs for commits that had each just gone green.
350  Failed or abandoned builds still re-queue. #90
351- =build cancel <owner/name> <n>= withdraws a queued build or ends a
352  running one. For a running build the server closes the runner's log
353  session, the runner kills the step within seconds, and its late report
354  changes nothing. The commit status goes back to the passed result from
355  another build of the same commit when one exists, else reads
356  =cancelled=. Needs write access.
357- Deploys copy with =rsync --partial=, so a transfer the host's load
358  stalled resumes, and =make deploy-runner= installs a systemd drop-in
359  (=Nice=10=, =CPUWeight=30=, =IOWeight=30=) so a build never starves the
360  host's sshd again.
361
362Replace both binaries and restart: =make deploy= for the daemon, then
363=make deploy-runner= for the runner, which carries its half of running-
364build cancellation and installs the drop-in. Migration 0030 adds the
365=runner_seen= table on start. The monitor change ships in
366=deploy/cloud-init.yaml=; an existing host takes it by hand.
367
368* v1.5.0 — 2026-09-02
369
370Merge requests stack.
371
372- A merge request whose target is the source branch of another open
373  merge request in the same repository is stacked on it. Nothing is
374  stored and no flag exists; the forge reads the stack from the
375  branches. =mr create= says =stacked on !A= when it applies, =mr show=
376  carries =stacked_on= and =stacked=, =mr list= rows carry =stacked_on=,
377  and the page says both directions in the header. #87
378- When the lower merge request merges, everything stacked on it is
379  retargeted onto what it merged into, with a system comment naming the
380  merge and its reviews kept: after a fast-forward or merge commit the
381  diff against the new target is the diff they were of. A squash or
382  rebase merge under a stack is refused, naming the stack, since it
383  would rewrite the commits the stack builds on.
384- The first stack merged on gitbay.org was the six merge requests of
385  v1.6.0, bottom-up, with no =mr retarget= typed. The wiki's
386  Stacked-MRs page walks through it.
387
388Replace the binary and restart. No migration.
389
390* v1.4.0 — 2026-09-01
391
392Until now the instance had one operator surface: root on the host. Every
393question about the instance itself — who is on it, what is stuck, what a
394spam repository is doing — needed a shell on port 2222. This release
395gives an instance admin the same answers over SSH, and one page on the
396web.
397
398- =admin user list= pages accounts by username with
399  =--state active|pending|disabled|admin=, each row carrying its state
400  and =last_seen=, the newest use of any of its SSH keys or API tokens.
401  =admin user show <name>= adds the keys with their last use, each
402  address with how it was verified, PGP keys, org roles, owned
403  repository count, API token names and live browser sessions. Both are
404  SSH-only and refused to non-admins, like =audit=. #69
405- =admin user promote|demote=. The only way to admin was
406  =admin user create --admin=; an existing account could not be raised
407  and an admin could not step down. Demoting the last admin is refused
408  inside the transaction that counts them. The host-local twin is the
409  recovery path when no admin key is reachable. #70
410- Repository overrides for moderation: =admin repo list= with size and
411  last push, and =admin repo archive|unarchive|visibility|delete=. Policy
412  still knows nothing about instance admin — a private repository
413  answers not-found to an admin as before — so each override skips the
414  access check explicitly and writes its own =admin repo.<action>= audit
415  row. #71
416- =gitbayd admin= dispatches into the registry. User create, disable,
417  enable and delete, email verify, invite and stats were reimplemented on
418  the host; they now live in the registry, SSH-only and admin-gated, and
419  the host binary runs them as the host — an admin context with no
420  account behind it, so its audit rows say =source: host= where a
421  session says the key fingerprint. Invite and stats gain an SSH twin by
422  the same move. =backup=, =gc= and the backfills stay host-local. #72
423- =audit= filters: =--actor <user>= or =--actor -= for actorless rows,
424  =--action <prefix>=, and =--since= as a duration (=30m=, =24h=, =7d=)
425  or a date. =gitbayd admin audit= takes the same flags and =--json=. #73
426- =dashboard= carries a =queues= block for admins: per worker —
427  webhooks, mail, mirrors, builds, dependency checks — the pending,
428  retrying and dead-lettered counts, the oldest pending age, and the
429  retrying or failed rows themselves, capped at twenty each. The mail
430  queue was readable nowhere before. =/admin= renders the block by
431  dispatching =dashboard=; non-admins get a 404 and no rail link. #74
432- =gitbayd admin config show= prints the configuration in effect as
433  TOML, defaults filled in and =smtp_pass= redacted, so a support
434  question starts from what runs rather than what was written. #81
435- Build badges are served as PNG at =badge/build.png= as well as SVG,
436  for places that will not render SVG.
437- Host monitoring writes its reading to journald on every run and exits
438  non-zero on an alert, so an unset webhook no longer looks like a
439  healthy host; it reads the ACME cache where it actually lives and
440  reports the soonest expiry. govulncheck runs as its own CI job. The
441  database is snapshotted hourly by =gitbay-db-backup.timer=, keeping 48,
442  alongside the nightly full archive; archives inherit the database's
443  mode rather than the umask default. #28
444- A runner whose log stream drops no longer fails the build it was
445  recording. #67
446- =go.yaml.in/yaml/v3= and =golang.org/x/net= bumped. #60
447
448Replace the binary and restart. No migration. The =gitbay-db-backup=
449timer and the monitor changes ship in =deploy/cloud-init.yaml= for new
450hosts; an existing host takes them from there by hand.
451
452* v1.3.0 — 2026-08-31
453
454A runner took every repository's work, which decided where you could run
455one.
456
457- =runner next= takes optional =owner/name= arguments and =gitbay-runner=
458  takes =-repos=, so a runner claims builds only for the repositories it
459  names. Naming none is the old behaviour, so an existing runner is
460  unaffected. This is what makes a runner outside the server practical: one
461  on a machine that should build a single project no longer picks up a
462  build belonging to someone else, which with open registration need not be
463  anyone the operator knows. The scoping is what the runner asks for rather
464  than an ACL the server holds over it — a runner account is admin by
465  necessity, so the boundary is the operator choosing how to start it. #66
466
467Replace the binary and restart. Runners want the new binary too, though an
468old one keeps working unscoped.
469
470* v1.2.1 — 2026-08-31
471
472Merging landed commits without running anything.
473
474- A merge moves the target ref with a direct ref update, so it never
475  reached post-receive and none of the ref-update work fired: no =push=
476  event for webhooks to subscribe to, and no builds. Pushing a commit to a
477  branch ran the whole =.gitbay/ci.yml=; merging the identical commit ran
478  nothing. Both now happen in the merge path, with the build queueing
479  shared between it and post-receive rather than living in one of them.
480  #65
481
482Replace the binary and restart.
483
484* v1.2.0 — 2026-08-31
485
486A merge request said what its state was and almost nothing about when it
487got there. It now keeps time.
488
489- Reviews and checks carry the moment they last said something, on the
490  merge request page and in =mr show=. A =ci/<job>= check also reports how
491  long its build ran, so the timing of a run is readable without opening
492  it. Checks posted through =status set= have no build and report only the
493  time. !137
494- A merged or closed merge request names who resolved it and when. The
495  header stated "X wants to merge" whatever the state; it now says "X
496  merged A into main on <date>", or "closed this without merging", and
497  drops the claim entirely for a row that carries no stamp rather than
498  inventing a time.
499- =mr show= gains =merged_at=/=merged_by= and =closed_at=/=closed_by=, a
500  =created_at= per review, and =updated_at= plus =duration= per check, in
501  both JSON and text. Additive: nothing existing changed shape.
502- The iOS client renders all of it as of krz/gitbay-ios!37.
503
504Replace the binary and restart. Migration 0029 adds four columns to
505=merge_requests= and backfills the merge stamp for merge requests already
506merged, reading the =mr.merged= events. A merge with no such event to read
507— an import, or a row older than its events — keeps no stamp, and every
508surface says nothing about when it happened rather than guessing.
509
510* v1.1.0 — 2026-08-31
511
512Every release until now answered questions. This one notices something
513on its own: that a repository's dependencies have moved, and says so
514without being asked.
515
516- Dependency update checks, opt-in per repository. A daemon worker reads
517  the manifests on the default branch, asks the ecosystem's registry what
518  the current release is, and maintains one issue per repository — opened
519  when something falls behind, rewritten when the set changes, closed once
520  nothing is behind. No package manager runs, so it needs no CI runner and
521  no configuration beyond turning it on. #58
522  - =go.mod= against proxy.golang.org, =package.json= with
523    =package-lock.json= against npm, =Cargo.toml= with =Cargo.lock=
524    against crates.io, =requirements.txt= and =pyproject.toml= against
525    PyPI. A lockfile wins where both exist. A requirement naming a set
526    rather than a release — a range, a wildcard, a git or path source — is
527    skipped, since a range that already admits the newest release is not
528    news.
529  - =repo deps enable|disable|status=, a toggle on the repository settings
530    page, and the same three over the JSON API.
531  - Off by default, because checking a private repository tells a public
532    registry what it depends on. That is the owner's disclosure to make.
533    =[deps] check_interval_hours= sets the cadence, default 24.
534  - The issue is authored by a =gitbay-bot= account, so the existing
535    notification mail reaches the repository's owner rather than excluding
536    them as the actor. Its table is padded to its columns, which a
537    renderer ignores and a mail client needs. #61
538- =help= takes a prefix — =help mr= narrows the registry to one noun — and
539  every command now documents its arguments, so the server answers "what
540  are the flags" instead of being guessed at. #57
541- Web: settings rows end in one column of controls, checkboxes drawn at
542  the height of the inputs and buttons they sit beside #59; an added line
543  keeps its leading dash in the diff; a contributor's several verified
544  addresses collapse to one row #56.
545
546Replace the binary and restart. Migration 0028 adds two tables and, when
547the name is free, the =gitbay-bot= account. An instance already using that
548name for a user or an org keeps what it has: the account is not created,
549and dependency checks report that as the reason they cannot open an issue
550rather than the migration failing and the daemon not starting. #64
551
552* v1.0.1 — 2026-08-30
553
554Two CI fixes found by running orgo's release pipeline on this instance.
555
556- A runner killed between claiming a build and reporting it left the build
557  =running= forever, and the commit's =ci/<job>= status pending with it.
558  =runner next= now fails builds past a 90-minute deadline — longer than the
559  runner's own =-timeout= — and resolves their commit status. #53
560- =gitbay keys add= and =gitbay repo deploy-key add= take stdin as a bare
561  =< key.pub=, but only forwarded it when =--file -= appeared in the
562  arguments, so both sent an empty body and rejected input the SSH API
563  accepts. #55
564
565Replace the binary and restart.
566
567* v1.0.0 — 2026-08-26
568
569The web finishes the job #35 set it: reading, reviewing and responding,
570with the CLI still the complete interface. Every capability exists over
571SSH, every web write dispatches the same control command, and anything
572whose input is a credential stays on the command line. The [[https://gitbay.org/krz/gitbay/wiki/Parity][Parity]] page in
573the wiki is the maintained matrix and says which rows are deliberately
574CLI-only.
575
576- Diff view: one foldable section per file with line-number gutters,
577  per-file stats, rename and binary handling, and syntax highlighting
578  run per hunk per side so multi-line constructs lex as real code.
579  Commit and merge request pages share it; review threads anchor
580  inline.
581- Repository facts on the code page: commit, branch and tag counts,
582  detected license, latest release, build status, a language census by
583  tracked bytes, and contributors resolved to accounts by verified
584  email. All derived from git at render time.
585- Account settings on the web: SSH keys with scope, OpenPGP keys, and
586  email addresses. Public keys are the only credential-shaped input the
587  web accepts — they are not secret, and a new user needs one
588  registered before the CLI is reachable to them. Token minting and
589  account export stay SSH-only.
590- Organizations are run from their page: membership and roles, teams,
591  team members, and team repository grants, for org admins.
592- Commit log shows each commit's combined check status and gains a path
593  filter, so per-file history is reachable without editing the URL.
594- Issue references from commit messages read "referenced in commit
595  <sha> by <author>", linking the author when their email is verified
596  here.
597- The rail's focus ring uses the shell's own mark: the light scheme's
598  accent was a dark blue ring on a black rail.
599
600No migrations. No new config.
601
602Upgrading from v0.5.0 is replace-the-binary-and-restart.
603
604* v0.5.0 — 2026-08-26
605
606A design pass and a parity pass. The web stops being a read-only
607mirror of the CLI without becoming the place you are expected to work.
608
609- New design: a black shell with a persistent left rail carrying
610  cross-repo state (pinned repos, review queue), the repo header
611  rendered identically on every tab so navigation never moves, sharp
612  lines, self-hosted IBM Plex, and code blocks that read against both
613  color schemes. Tree listings sort directories first and carry each
614  file's last commit; diffs, inputs and controls were reworked to
615  match.
616- Web parity with the CLI, dispatched through the same command
617  registry the CLI and JSON API use — every web write is the
618  equivalent =gitbay= command with =--source web=:
619  - merge requests: review, resolve threads, merge, close, and open a
620    new MR from the browser
621  - issues: state, labels, assignees, milestones
622  - repositories: settings, branch protection, visibility
623  - releases: create and edit; builds: trigger a job
624  Commands marked SSH-only still refuse over the web: build secrets,
625  mirror tokens, domain claims, token minting, deletion and transfer.
626- A dashboard that answers "what needs me": review queue, assigned
627  issues, pinned repos, and an activity feed. Author names resolve to
628  accounts and link to profiles wherever commits appear.
629- Build status badges at =/{owner}/{repo}/badge/build.svg= for public
630  repos.
631- =[web] title= sets the instance's display name, separate from the
632  hostname commands are pasted with.
633- =make build/test/deploy= targets.
634- Fixes: the mobile tab strip scrolls sideways only, long commit
635  subjects no longer overflow on narrow screens, the shell fills the
636  viewport with the line-length cap moved onto prose, and the account
637  cell lines up with the page footer.
638
639No migrations. New config: =[web] title=.
640
641* v0.4.0 — 2026-08-25
642
643- Git LFS: standard clients work over both transports.
644  =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
645  included; download needs read, upload write), minting stateless
646  repo- and operation-scoped tokens for the batch API and basic
647  transfers. Anonymous HTTPS downloads for public repos; uploads
648  verified against size and sha256 before landing. Storage is
649  content-addressed under =[lfs] root= behind a small interface an
650  S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
651  objects (512MB default).
652- Build failures mail the repo's notify targets with the log tail and
653  build link — failed scheduled jobs reach an inbox.
654- =release edit= updates a release's title and notes (absent flags
655  keep their field); omaha-style CI note rebuilds work again.
656- Syntax highlighting follows the color scheme: class-based chroma
657  with light and dark palettes, the light-pinned code background is
658  gone, and markdown fences and org src blocks highlight too. The UGC
659  sanitizer admits only chroma's token-code classes.
660
661No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
662
663* v0.3.0 — 2026-08-25
664
665- CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=
666  over SSH (admin-only runner protocol; statuses feed =require-checks=).
667  Per-repo secrets set over stdin and injected into build environments;
668  cron schedules (server-local time) and tag-glob triggers, mutually
669  exclusive per job; =build list/show/log/trigger= and a builds tab.
670- Pages: public repos' =pages= branches served on =<owner>.<domain>=
671  (=[pages] domain=), custom domains with DNS TXT ownership challenges
672  and 7-day expiry for pending claims, per-subdomain on-demand ACME.
673- Wikis (=.wiki= companion repos, access mirrors the parent) and teams
674  within orgs (members-role scoping, per-repo team grants).
675- Activity graphs on user and org pages, backfillable
676  (=admin backfill-activity=); commits attributed by verified author
677  email, deduped by sha.
678- MR pages list the commits the MR carries; =mr show= gains a commits
679  section.
680- Per-file history: =?path== on the web log, =--path= on =repo log=,
681  history link on blob pages.
682- Mirror status surfaced in =repo show= and the repo header
683  (admin-only), with sync errors visible; tag-only pushes now schedule
684  mirror syncs.
685- Rendering: GFM tables/strikethrough/autolinks/task lists, blob image
686  previews, raw serves images with real content types (README images
687  render under nosniff), 0BSD license recognition, repo website links,
688  compact dashboard pins.
689- =admin user delete= for accounts that anchor nothing, with named
690  blockers otherwise.
691- Fixes: wiki pages no longer overflow on mobile (iOS font-inflation
692  trigger), GHSA-free deps, secret values pipe correctly through the
693  CLI.
694
695Migrations 0020-0025 apply on start. New config: =[pages] domain=.
696The runner is a new binary (=gitbay-runner=); see the wiki's Admin
697guide for setup. Stress-tested against an import of git.git (82k
698commits): see the wiki's Performance page.
699
700* v0.2.0 — 2026-08-24
701
702- Deploy keys: repo-bound CI keys (=repo deploy-key=), ro/rw, rename- and
703  transfer-proof.
704- Commit statuses (=status set/list=), combined state on MR pages, and a
705  =require-checks= merge gate.
706- Email notifications for issue and MR activity (participants with
707  verified addresses; never the actor).
708- Inline review threads on MR diffs (=mr diff-comment/threads/resolve=),
709  stale on force-push, =require-resolved= merge gate.
710- Required approvals with CODEOWNERS (=require-approvals=; latest review
711  wins, author excluded) and a =require-resolved= gate; merge gate order
712  is checks → approvals → CODEOWNERS → resolved threads → signatures.
713- Web design revamp: token-based stylesheet (light+dark), wordmark and
714  favicon, aligned layout grid, card-based listings, designed 404,
715  mobile pass.
716- Cross-references and mentions: =#N=, =!N=, =owner/name#N=, =@user=
717  autolink in issue/MR text, viewer-aware for private repos.
718- Archived repositories (read-only with badge) and repo topics.
719- Blame view with signature-aware attribution and 1000-line pages.
720- Repository search (name/description/topic) and per-repo code search
721  (=repo grep=, web search tab); blob line anchors.
722- Homepage: dashboard for logged-in users (pinned repos via =repo pin=,
723  open MRs and issues involving you), landing page for visitors, full
724  public listing at =/explore=; MR diffs collapsed by default.
725- Milestones (=milestone create/list/close=, =issue/mr milestone=) with
726  web progress; issue templates from =.gitbay/issue-template*.md=
727  (CLI =$EDITOR= prefill and web form).
728- Issue actions from commit messages landing on the default branch:
729  =closes/fixes/resolves #N= closes, bare =#N= leaves a reference
730  comment; once per issue+commit.
731- Vanity Go imports: =[go_import]= config serves go-import meta tags, so
732  =go install gitbay.org/gitbay/cmd/...@latest= works.
733- Release script: =deploy/release.sh <tag>= builds reproducible
734  linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
735- Repository maintenance: =admin gc= (repack/prune, per-repo sizes),
736  =admin stats= (counts + disk usage), weekly =gitbay-gc.timer=.
737- Releases: tag-anchored notes and binary assets (=release= commands,
738  assets over SSH stdin/stdout, web releases tab with downloads).
739- GitHub history import: =repo import-issues= brings issues and PRs
740  (as merged/closed MRs) with comments, labels, and state, attributed
741  inline and resumable.
742- Push and pull mirroring (=repo mirror=): background sync, read-only
743  pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
744- Web signup at =/register= for open and invite instances.
745- Audit log (=audit=, =gitbayd admin audit=): every mutating command
746  with source key fingerprint, registrations, force-pushes, auth
747  failures. Hardening: per-IP auth-failure throttling
748  (=ssh_auth_rate=), =max_pack_bytes= enforced, =admin user
749  disable/enable=.
750- Account migration: =gitbay migrate --from <host>= (bundle
751  export/replay + client-side git mirror); =gitbay auth export= as a
752  user-level backup.
753- Editable issues and MRs (=issue edit=, =mr edit=, web forms).
754- Commit references appear as system messages with linked shas.
755- Design: top nav, repo listing rows (topics, license, last updated),
756  file table headers, README relative-link resolution, branch
757  dropdown, web pinning, org owner picker, label filters, linked
758  usernames and commit parents, =/privacy= page, blue accent.
759
760Upgrade notes: migrations 0006–0019 apply on start. No config changes
761required; =[go_import]=, =[mirrors]=, =web.privacy_notice=, and
762=web.mode = "accounts"= are opt-in.
763
764* v0.1.0 — 2026-08-24
765
766First tagged release: the complete CLI-first forge. SSH control plane
767(bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues,
768merge requests (ff/merge/squash/rebase with signature policy), OpenPGP
769and SSHSIG verification with retroactive re-verification, orgs, repo
770import, web UI (view-only or accounts mode), registration with invites
771and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups,
772ACME TLS, systemd deployment.