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