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