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