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