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