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