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