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