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