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