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