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