CHANGELOG.org
2507 lines · 132229 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.38.0 — 2026-09-29
8
9Merge when ready, build egress by trust class, and restore-drill
10tooling.
11
12*Upgrade note.* The runner's host needs the builds table: run =make
13deploy-runner= (or install =deploy/gitbay-runner-builds.nft= and the
14drop-in by hand), scoped to a scratch repository first, and run
15=deploy/runner-auth-flood-test.sh= before pointing it back at real
16repositories. A runner started with =-untrusted= or a loopback
17=-remote= refuses to start without build cgroups. Runners off the
18daemon's host and =-isolation none= are unaffected.
19
20- Marking notifications read from the web dispatches =notifications
21 read=, so it counts against the write budget and is audited (#261).
22- =gitbay <cli path> --help= for commands the CLI regroups (=auth keys
23 add=, =auth email list=, =repo topics list=) prints EXAMPLES under the
24 CLI's path instead of the registered one (#304).
25- =gitbayd admin backup --verify= also checks every release asset the
26 database names against its recorded size and sha256, and every
27 archived LFS object against its name (#259).
28- =gitbayd admin restore-drill <archive> --into <dir>= extracts a full
29 archive into an empty directory, runs the =--verify= checks on the
30 extracted copy, and prints the newest issue, comment and push it
31 recovered and the elapsed time. The Admin wiki's Restore drill
32 section lists what to restore, what to check and where to record it
33 (#259).
34- The runner starts each podman build under =builds/trusted= or
35 =builds/untrusted= in its service cgroup, and a second nftables
36 table (=deploy/gitbay-runner-builds.nft=) matches build traffic by
37 that cgroup: no build reaches the host's loopback beyond DNS, or a
38 private range; a trusted build keeps the internet and the forge's public 22,
39 80 and 443; an untrusted build gets TCP 80 and 443 and DNS, and not
40 the forge. The runner's drop-in creates the cgroups and loads the
41 table on every start, and the start fails without it. A runner
42 with =-untrusted= or a loopback =-remote= refuses to start without
43 build cgroups, which the table needs to match anything. =make
44 deploy-runner= installs it. =deploy/runner-auth-flood-test.sh= runs
45 the scratch-repository test: a build failing SSH logins must not
46 lock the runner out. Run it before pointing the runner back at real
47 repositories; the Admin page has the steps and the rollback. (#260)
48- =mr merge <n> --when-ready= queues a merge until the gates pass,
49 merging as the queuing user with their rights checked then; tried on
50 a status, a review, a resolved thread, =mr ready= and a push to the
51 source branch. A refusal the queuer can fix, such as a branch behind
52 a =require_signed_commits= target, keeps it queued with the reason
53 on =mr show= and the page. The queue is bound to the key or token it
54 was made with: removing, revoking, expiring or narrowing it
55 dequeues, as do losing write access, a push or retarget by someone
56 who cannot write to the target, deleting the source branch, and
57 closing. An expiring credential cannot queue. =--cancel= dequeues.
58 =mr show=, =mr list= and the dashboard carry =queued=. Migration
59 0067 (#289).
60
61* v1.37.0 — 2026-09-29
62
63Findings from the 2026-09-27 architecture review.
64
65- =webhook add= reads the signing secret from stdin with =--secret -=;
66 a value on the command line is refused, since argv shows in process
67 listings and shell history. A script that passed the value must pipe
68 it: =printf %s "$SECRET" | gitbay webhook add <repo> <url> --secret -=.
69 The iOS app's webhook add breaks until it sends the secret on stdin
70 (krz/gitbay-ios#21) (#284).
71- =repo import --from= takes http and https URLs only; =git://= is
72 refused, since its connection cannot be held to a checked address.
73 The host is resolved and checked like a mirror's, git connects only
74 to the checked addresses with redirects off, and the system and
75 global gitconfig are ignored. A source that redirects (a renamed
76 repository) fails; import from the URL it redirects to. Needs git
77 2.37 or later on the server (#298).
78- =repo import-issues= resolves and checks the API host and the git
79 host once and connects only to the checked addresses: the API client
80 dials them with no proxy from the environment and follows no
81 redirect, and the pull-head fetch runs git pinned, with redirects
82 off and without the system and global gitconfig. =--api-base= refuses
83 credentials, a query or a fragment. An API that redirects (a renamed
84 repository) fails; import under the new name (#301).
85- =repo mirror add= refuses a host written numerically (=127.1=,
86 =2130706433=, =0x7f.1=) when the mirror is added, rather than at its
87 first sync (#298).
88- A browser session creates credentials and grants access — keys, PGP
89 keys, tokens, verified addresses, org and repository roles, transfers,
90 repository visibility, webhooks, secrets, mirrors, and the admin
91 promote/enable and repository-visibility actions — only within 15
92 minutes of signing in. An
93 older session gets the form back with a "Sign in again" link, and the
94 login returns to it. SSH and API tokens are unaffected (#297).
95- The builds page's status badge section gives an org-mode snippet
96 beside the Markdown one, for a README.org (#299).
97- API tokens on the settings page: create with a scope and optional
98 expiry, shown once; list; revoke with the name typed back; the
99 registered page's next steps as a numbered list (#264).
100- A wiki link to an existing non-page file (an .svg, .txt, .pdf) now
101 resolves to the raw route instead of 404ing against the page route
102 (#283).
103- The new-issue form takes labels, milestone and assignee in one step
104 for writers; a Discussion heading sits before comment threads; the
105 build page's live note says the page updates itself; and the rail
106 and the phone More menu render from one list (#271).
107- The new-issue form keeps milestone and assignee through preview and
108 a refused create, the way it already kept title, body and labels;
109 a refused create re-renders the form with the draft and the
110 refusal instead of an error page (#271).
111- The merge request range-diff page renders a bad =from=/=to== query
112 parameter inline instead of 404ing; only an unknown merge request
113 404s (#271).
114- Empty states on the web state the fact instead of a CLI command, and
115 drop "yet" on a finished item; the merge request list offers a New
116 merge request link, a fork link, or a sign-in prompt depending on
117 what the visitor can do; and the search page's scope caption is
118 always visible, not only before a first search (#270).
119- Issues, milestones, org milestones and releases drop the CLI command
120 from their empty states too, matching the rest of the register: a
121 link to the web form that does the thing when one exists, otherwise
122 just the fact (#270).
123- The merge request list and compare page offer New merge request to a
124 reader who owns a writable fork of the repository, not only to a
125 writer (#270).
126
127Credentials and sessions: revocation, delegation, expiry and an idle
128timeout (#256, #257, #276, #277).
129
130*Upgrade note.* =token create= makes a =read= token unless given
131=--scope full=. A script that mints a token and then writes with it
132must add =--scope full=. Existing tokens keep their scope.
133
134*Upgrade note.* Upgrade the instance before the CLI: an older server
135refuses the CLI's leading =--path== argument as an unknown command,
136for the eighteen commands whose CLI path differs from the registry's
137(the =gitbay auth ...= commands and =repo topics list=).
138
139*Upgrade note.* gitbayd needs =server.secret_key_file= (default
140=/etc/gitbay/secret.key=) and refuses to start without it. Before
141replacing the binary, run =gitbayd admin secrets init= as root and
142=chown gitbay:gitbay /etc/gitbay/secret.key= (=deploy/install.sh= does
143both when the file is missing). The first start seals the stored
144secrets. Back the key file up separately: =admin backup= archives do
145not carry it (see the Admin wiki, "Secret key"). Downgrading to an
146earlier release after values are sealed is not supported: an older
147gitbayd reads a sealed value's =gbs1:...= prefix as the literal
148secret.
149
150*Upgrade note.* Archives now carry a directory entry for every
151directory, so a bare repository whose refs are all packed restores as
152a repository. An archive written before this release lacks those
153entries; if extracting one leaves a repository's =refs/= directory
154missing, =gitbayd admin backup --verify <archive>= names it, and
155=mkdir -p <root>/repos/<owner>/<name>.git/refs= fixes it.
156
157*Upgrade note.* =repo import= now refuses a =git://= source and a
158=--from= URL carrying a query or fragment. Mirrors and imports whose
159host is written numerically (=127.1=, =2130706433=, =0x7f.1=) rather
160than as a dotted address are refused too; rewrite the URL before
161upgrading (#298).
162
163- A token with a =--ttl= is refused on every command that creates a
164 credential: tokens, keys, deploy keys, runner keys, login links,
165 invites, accounts and verified addresses (#257).
166- Tokens and SSH keys record the token they were created through.
167 =token revoke <name>= lists what it created; =--created= revokes
168 those too (#257).
169- Removing an SSH key, a deploy key, or disabling an account closes the
170 connections the key opened, a push in flight included (#256).
171- =keys add= and =repo deploy-key add= take =--ttl=; an expired key is
172 refused at authentication, and an open connection on it closes within
173 15 seconds. An expiring key cannot create credentials, like an
174 expiring token. =keys list= and =repo deploy-key list= gain =USED= and
175 =EXPIRES= columns, after the label (#277).
176- =token list= at a terminal shows a future expiry as a time, not
177 "just now" (#286).
178- Browser sessions end after twelve hours without a request, and after
179 seven days as before. Sessions open at upgrade get a fresh twelve
180 hours. =web sessions list= shows when each was last used (#276).
181- =web login= over SSH refuses a sixth link in an hour, the same bound
182 the login page's mailed links have (#278).
183- The HTTPS listener refuses TLS below 1.2, in both certificate modes
184 (#281).
185- Mail to a non-local relay requires TLS by default; a relay that does
186 not offer STARTTLS gets no mail unless =mail.require_tls = false=
187 restores the old behaviour. =mail.tls = "implicit"= speaks TLS from
188 the first byte, for relays on port 465 (#280).
189- Mirror sync resolves the host, checks the addresses and connects git
190 only to them, with redirects off; a URL that now resolves to private
191 space, or is not http or https, fails the sync with the reason on
192 =repo mirror list=. A mirror of a renamed repository that redirects
193 fails until its URL is updated. Sync ignores the system and global
194 gitconfig. Needs git 2.37 or later: with an older git no mirror
195 syncs, and each records why (#279).
196- Webhook and mirror targets in 100.64.0.0/10 or on a multicast
197 address are refused, as private addresses are (#279).
198- The hook socket is mode 0600 and, on Linux, refuses a peer with
199 another uid; each receive-pack gets its own token from sshd, stored
200 hashed (migration 0063), and the hook must present it before the
201 daemon acts. *Operators:* deploy with no push in flight, since a
202 receive-pack started by the old daemon has no token and its
203 post-receive will be refused by the new one (#282).
204- Audit rows are hash-chained, each carrying the SHA-256 of the one
205 before it (migration 0064), and the daemon logs a copy of every row it
206 writes to its journal. =gitbayd admin audit verify= prints the row
207 count and the last id and hash, and exits 1 naming the first row that
208 was edited or whose predecessor was removed. The chain is unkeyed:
209 someone who can write the database can recompute the later hashes,
210 and verify catches an edit only when they were not recomputed.
211 Comparing verify's last id and hash with the journal is the check for
212 any change, including removing the newest rows (#275).
213- Refused mutating commands (exit 3 or 4) are audited as =refused
214 <command>=, and refused pushes as =refused git-receive-pack=, keeping
215 flag names and the target but no values; ten a minute per account and
216 600 across the instance, counted per process, past which one
217 =refused.throttled= row stands for the rest of the minute. Under
218 =ssh.mode = "system"= each =gitbayd shell= connection counts
219 separately (#275).
220- Pushes refused in pre-receive (a branch or tag rule, a release
221 anchor, an unsigned commit) are audited as =refused push= with the
222 repository and ref names, and hook socket requests failing the peer
223 or push-token check as =refused hook=, under the same caps (#275).
224- Audit retention deletes by id, up to the newest row older than the
225 retention, so a clock step back cannot leave a gap in the chain (#275).
226- =dashboard= and =feed= print activity as sentences
227 (=cmc opened issue krz/gitbay#12=) instead of raw event payloads,
228 and a labelled event names its labels there and on the web feed. An
229 issue assigned to you appears only under "assigned to you": the
230 =open_issues= field of =dashboard --json= no longer includes issues
231 assigned to the caller. =notifications list= names =--all= when only
232 read items remain (#265).
233- Help and usage print the command the way the caller typed it —
234 =usage: gitbay auth keys remove <fingerprint>=, not the registry's
235 own path. =auth --help= lists the email and API token commands
236 alongside keys and PGP. A bad-flag error prints the same prefixed
237 usage line a wrong-argument refusal does. Outside the CLI a usage
238 refusal reads =usage: ssh git@<host> ...= on every surface,
239 including the error text of the web UI and the JSON API (#267).
240- An unregistered SSH key is refused with its own fingerprint and the
241 real host, and both the web and ssh paths to register (#268).
242- =issue create= takes =--label= (repeatable), =--milestone= and
243 =--assignee= (repeatable), setting them in the same call instead of
244 a separate one per field (#268).
245- =mr show= pluralizes multi-row section headings with counts: =commits (7):=,
246 =checks (2):=, =reviews (3):= (#268).
247- =repo readme <owner/name> [--ref <ref>]= prints a repository's README,
248 picked the same way the web page picks one (#268).
249- =repo show='s mirror table truncates =LAST SYNC= to the second, like
250 every other timestamp in a view (#268).
251- A =-- foreign_keys: off= migration's =foreign_key_check= now runs
252 inside the migration's own transaction, before commit, so a
253 violation rolls the migration back instead of leaving the bad
254 schema and =user_version= already persisted; the web pin and watch
255 buttons dispatch through =repo pin=/=unpin= and =repo
256 watch=/=mute=/=unwatch= instead of writing the store directly, so a
257 refusal reaches the viewer as a message instead of being dropped,
258 and the watch button now cycles three states — default, watching,
259 muted — instead of two; the response that consumes a login link's
260 =?token== sends =Cache-Control: no-store=, so no intermediary keeps
261 a copy of the single-use URL; and wiki documentation fixes:
262 API.org clarifies token commands work on the API, Parity.org
263 documents batched review and web watch/pin dispatch, Threat-Model.org
264 documents the login-link URL exception (#261).
265- The account settings page quotes the CLI and SSH command forms that
266 actually resolve; a test runs every command a web page quotes against
267 the CLI and control registries so a renamed command fails CI instead
268 of shipping a dead instruction (#263).
269- The web merge request page lists all revisions with a "compare to
270 previous" link on each revision after the first, so a reviewer whose
271 approval a force-push staled can see what changed without leaving the
272 browser (#269).
273- CI secrets, webhook secrets, mirror tokens and push device tokens are
274 stored sealed with AES-256-GCM (#273). =gitbayd admin secrets
275 init|rotate|check=.
276- Untrusted builds (merge requests from forks) get a fresh HOME
277 removed after the build and no secrets; trusted builds keep a
278 per-repository home under =<workdir>/trusted-home=. Deploy gitbayd
279 before the runner; the old shared homes under the runner's workdir
280 can be deleted. (#255)
281- =status set= refuses =ci/= contexts, which belong to the instance's
282 builds. Build results are reused only from trusted builds on the
283 same image. =repo settings require-contexts= names status contexts
284 that must report green; setting any turns require-checks on, and one
285 not yet reported counts as pending. (#258)
286- A runner polling over loopback gives its podman builds =GITBAY_SSH=
287 at =169.254.1.2=, pasta's address for the host, with the port when
288 it is not 22, since under pasta the container holds the host's
289 public address. An nftables table limits what the runner's user
290 reaches on the host to =127.0.0.1:22=, DNS on loopback, and public
291 22, 80 and 443. The runner unit now requires the egress unit: run
292 =deploy/runner-podman-setup.sh= (it installs nftables) before =make
293 deploy-runner=. Deploy gitbayd, then the runner, after validating on
294 a scratch repository per the CI page. (#260)
295- =build show= names a failed build's step and duration; =build log
296 --step <n>|failed --tail <lines>= reads one step's output or the
297 last lines of the stored log. Deploy gitbayd before the runner: an
298 older server refuses the runner's =--step= and =--reason= (exit 2),
299 and its failed builds stay running until the reaper fails them.
300 (#266)
301- =gitbayd admin backup= encrypts archives to =[backup] age_recipients=
302 when set (#274); =--verify= takes =--identity <file>=. Archive names
303 gain =.age=; the shipped backup scripts and monitor match both.
304- A full backup holds =<root>/backup.lock= from its database snapshot
305 to its last repository; =repo delete=, =repo rename=, =repo
306 transfer=, =admin repo delete= and =org rename= refuse with "a
307 backup is running" while it runs. =--verify= now also runs =git
308 fsck --connectivity-only= on each archived repository and names any
309 that fail. (#259)
310- A full backup archives each repository's HEAD, =refs/= and
311 =packed-refs= before its objects, so a push during the backup cannot
312 leave an archived ref naming objects the archive lacks. The exception
313 is git's own automatic gc after a push repacking during the walk: the
314 archive can then miss objects, and =--verify= reports it. (#259)
315- =gitbayd admin gc= and =admin mr prune= refuse with "a backup is
316 running" during a full backup. A pack or loose object that git's
317 automatic gc removes while the backup walks is skipped instead of
318 failing the run; =--verify= reports it if a ref needed it. (#259)
319- =gitbayd admin backup= and =--verify= no longer need the secret key
320 file: sealed values are copied as they are. A missing database is
321 refused instead of created. (#259)
322- =gitbayd admin backup= refuses an =--out= inside =server.root=, and
323 removes the snapshot directories and temporary archives a killed run
324 left beside its archive once they are a day old. (#259)
325- =gitbayd admin backup --verify= runs fsck with =--git-dir=, so a
326 directory that is not a repository fails instead of git checking an
327 enclosing one, and does not extract =objects/info/alternates= or a
328 repository's =commondir=, so neither can point fsck at another
329 repository on the host. (#259)
330- =gitbayd admin secrets init= and =rotate= hold an flock on =<key
331 file>.lock=, so two runs at once serialize. (#273)
332- Git pack generation (clones, fetches, =git archive --remote=) over
333 SSH, smart HTTP and git:// now shares one concurrency budget:
334 =limits.pack_concurrency= (3), =pack_per_principal= (2), =pack_queue=
335 (32) and =pack_queue_wait= (60s). Past the queue an SSH client sees
336 "the server is busy…" and exits 1, HTTP gets 503 with
337 =Retry-After: 30=, and git:// gets an =ERR= line. *Operators:* the
338 defaults are tuned for a four-core host; set the three counts to -1
339 to turn the limit off. A running clone is killed when no write to
340 its client completes for two minutes: a client reading below about
341 550 B/s, or an HTTP request body that takes over two minutes with
342 nothing written back, is cut. Ref listings, pushes and =repo
343 download= are unaffected. Under =ssh.mode = "system"= SSH clones are not counted,
344 since each session is its own process (#262).
345- Anonymous clones are counted per IPv4 address or IPv6 /64, and
346 together hold at most =pack_concurrency= − 1 slots: an account can
347 take the last slot when it is free, and anonymous clients cannot hold
348 it (#262).
349- A request turned away by the pack limit logs a warning naming the
350 transport and whether the client was signed in, never its address,
351 at most once a minute per transport (#262).
352- Web archive downloads (=/{owner}/{repo}/archive/{ref}.tar.gz=) take
353 a pack slot, answer 503 with =Retry-After: 30= when none is free, and
354 are killed when the client leaves or stops reading (#262).
355- LFS transfer tokens name the SSH key that obtained them, deploy keys
356 included, and every LFS request checks that the key is still
357 registered, unexpired and on an enabled account: removing a key or
358 disabling an account ends its tokens at once instead of within the
359 hour (#285). *Operators:* tokens minted before the upgrade are
360 refused. git-lfs asks =git-lfs-authenticate= for a token each time
361 it runs, so only a transfer running across the restart fails, with
362 "repository not found"; running the command again fixes it. A
363 download from a public repository that presents a token issued
364 before the upgrade is refused the same way, not served anonymously,
365 and needs the same rerun.
366- Every LFS request also repeats the repository check for the token's
367 key: a collaborator whose access is revoked or reduced, or a reader
368 of a public repository made private, loses the token's use with the
369 access, and an upload token stops working once its repository is
370 archived (#285).
371- LFS transfer tokens carry a hash of their key's fingerprint beside
372 its id, and a token whose key id now belongs to another key is
373 refused, since SQLite gives a new key the id of the last deleted one.
374 The token format changed: tokens minted before the upgrade are
375 refused, and a transfer running across the restart needs running
376 again (#303).
377
378* v1.36.0 — 2026-09-23
379
380Terminal output for the CLI (#254).
381
382*Upgrade note.* Upgrade the instance before the CLI: an older server
383refuses the CLI's leading =--term= argument as an unknown command.
384Against an older instance, set =GITBAY_TERM=off= and the CLI sends no
385terminal size.
386
387- At a terminal, lists print under a header, fitted to the width, with
388 states in colour and relative ages; the next page is a command on
389 stderr. Piped output keeps the same tab-separated rows, with
390 timestamps as RFC3339 to the second; =repo log= rows are
391 tab-separated (were fixed-width) and =repo settings show= keys print
392 as fields (=require mr=, not =require_mr:=).
393- =show= commands print a title line, aligned fields, the body
394 rendered from markdown or org, events one per line and comments
395 under a rule, through a pager when longer than the screen.
396- Help describes every flag, with defaults and examples, and
397 =gitbay --help= groups the commands under WORK, REPOSITORIES, YOU
398 and INSTANCE. =help --json= adds =flags= and =examples=.
399- =release list= takes =--limit= and =--cursor=, and leaves the title
400 empty when it repeats the tag. =mr revisions='s one-revision note
401 moved to stderr. =notifications device add= prints =registered
402 device <n>=. =dashboard= prints =none= under an empty section.
403
404The CLI sends =--term=<cols>[,color]= as the first argument on the
405SSH command line, since OpenSSH's multiplexed sessions do not forward
406a session's =SetEnv=; the server reads it only there, and ignores it
407over HTTP. Stock ssh opts in with =ssh git@gitbay.org -- --term=120,color
408issue list krz/gitbay= (the =--= keeps ssh from reading it as its own
409option) or =-o SetEnv=GITBAY_TERM=120,color=. Operators running
410the system-sshd forced command add =AcceptEnv GITBAY_TERM= to
411=sshd_config= for the =SetEnv= form; the =--term= argument needs no
412sshd configuration.
413
414* v1.35.1 — 2026-09-23
415
416The landing page's recording (#253).
417
418- The landing page plays a recording of signup to release from a
419 terminal on gitbay.org, muted with controls, in place of the merged
420 merge request picture. The quickstart block drops its comment. The
421 tapes and the render script are in =docs/demo/=.
422- =/static/img/= serves gif, webm and mp4 with their own types and
423 answers Range requests, which Safari needs to play video.
424- The Quickstart wiki page shows the recording as a gif.
425- The footer's iOS link goes to the App Store listing.
426
427* v1.35.0 — 2026-09-23
428
429Following a running build (#250, #251), and the web interface
430guidelines review (#249).
431
432- =build log <owner/name> <n> --follow= prints the stored log, then
433 output as the runner sends it, then =build <n> <status>= on stderr
434 once the build ends; the exit code is 0 whatever the outcome. The
435 build page does the same without JavaScript while a build is queued
436 or running: the log streams into the page and ends with "build
437 finished: <status>". =?follow=0= and HEAD render it once.
438- A follow ends when its reader leaves: a closed SSH channel (Ctrl-C
439 over the CLI's shared connection included) or a closed page. A
440 follow of a build still queued after ten minutes ends and says so,
441 since nothing reaps a queued build. An account holds eight follows
442 at once; signed-out viewers share one account's eight.
443- A follow re-checks read access every two seconds by repository id,
444 reloading the account: a repository made private or an account
445 disabled ends it as not found; a rename does not.
446- A restart ends open follows before the drain, with "gitbay is
447 restarting; follow the build again in a moment" on every surface,
448 instead of holding the drain for 30 s. Other requests, git transport
449 included, drain as before.
450- Over the JSON API the command answers when the build ends, with the
451 whole log.
452- Typed-name confirmation on removing an org member, removing a team
453 member, revoking a team's repository grant, and promoting an account
454 to admin. The team forms are split so the confirm field sits beside
455 the removal only.
456- Registration's email field is an email input; email, username,
457 one-time-code, SSH key and identifier fields carry =autocomplete=,
458 =autocapitalize= and =spellcheck= as fits. The merge request close
459 field accepts the =!12= its placeholder shows.
460- The refs page's compare inputs are named by their visible labels;
461 the line-comment link names its line. =theme-color= matches the rail.
462- Behind a reverse proxy, turn response buffering off for the build
463 page (=X-Accel-Buffering: no= covers nginx), or the live log arrives
464 only when the build ends.
465
466* v1.34.1 — 2026-09-21
467
468Three findings from an external review of the web UI (#248).
469
470- Explore is a rail square at every width. It was =.railopt=, so it
471 dropped below 34rem into the More menu, which exists only for a
472 signed-in viewer: a signed-out phone had no route to the listing from
473 any page. Six squares and the mark are 308px, inside a 320px phone.
474- =/register= answers "no key yet?" in place, with the =ssh-keygen= and
475 =cat= lines behind a disclosure, instead of linking out to the wiki
476 over a half-filled form. The link also hardcoded =gitbay.org=.
477- An empty =/search= says what to do next — fewer words, the same query
478 across every kind, or the listing — rather than repeating the count
479 line's "no matches".
480
481* v1.34.0 — 2026-09-21
482
483The profile's tabs, reworked.
484
485- The bar reads About, Repositories, Bookmarks, Snippets, and People
486 for an organization's admins. =/{owner}= is About; the rest hang off
487 =/-/=. A tab nobody may open is not offered and its URL is a 404.
488- The activity graph moved inside About, with a log of the newest
489 thirty events under it. The log counts what the graph over it counts:
490 =UserPublicEvents= keys on the actor for a user, matching
491 =ActivityByDay=, while an organization keeps =OwnerPublicEvents=. Both
492 are public repositories only. =activity.atom= is still the feed that
493 goes back further.
494- Bookmarks are a tab on your own profile. =repo bookmarks= takes no
495 owner and lists the caller's, so the tab is not offered on anyone
496 else's and its URL is a 404 there. =/bookmarks= redirects to it.
497- The snippet list renders inside the profile rather than on a page of
498 its own, so it carries the header and the tab bar like every other
499 section. A snippet itself is still its own page.
500
501Eleven web findings, mostly alignment and affordance (#247).
502
503- Logging out asks first. =GET /logout= is the confirmation page the
504 rail's signout square and the More menu link to; the button on it
505 posts to the same path, which is still what ends the session.
506- Bookmarks and Snippets are gone from the rail and the More menu. Both
507 land on the profile, where they are tabs, and every square left in
508 the rail is an instance-level destination.
509- A repository tree marks a directory with a folder glyph and a file
510 with a file glyph. The trailing slash still says it in text and the
511 glyphs are =aria-hidden=, so the cue no longer rests on the link
512 colour alone. Per-filetype icons are deliberately not done.
513- A =/search= hit carries its kind in a chip, in the words =search=
514 prints, so the meta line no longer has to say "repository".
515- A settings row lines its control up on the right: a checkbox, a
516 number and a full-width text input all end on the same rule, with
517 Save in its own column. The label column keeps a 14rem floor so a
518 hint does not wrap a word to a line.
519- The email rows on =/settings= put their buttons and confirm field on
520 the right, so they line up however long an address is.
521- =/admin/users= draws a disabled Promote on an account that is not
522 active, rather than leaving the cell short, and the page is wide. At
523 48rem the Actions cell clipped the second form's button, which left
524 its confirm field looking like it belonged to the button before it —
525 an active row read as though Promote wanted the name typed. The cell
526 is now two fixed slots, each right-aligned, so the role button, the
527 confirm field and the access button each hold one column whichever
528 controls a row carries: an admin's row has a field on both forms, a
529 disabled account's enable form has none. The field is 14rem, which
530 fits "type <name> to confirm" for a name of ordinary length.
531- The profile's inactive tabs draw their underline in =--line=, so the
532 strip reads as a track the current tab is marked in.
533- =.listhead= sheds its children's block margins, which is what kept a
534 =p.meta= from sitting level with the heading beside it.
535- =nav.tabs= has a bottom margin.
536- The footer links the iOS client.
537
538The e2e suite runs in parallel (#246).
539
540- =startInstance= linked a byte-identical 35MB gitbayd for each of the
541 207 tests, about 0.8s apiece: go's build cache covers the compile,
542 not the link. Each binary is now built once per process, lazily, so
543 a =-run= of one test links only what it needs.
544- 202 of the 207 tests take =t.Parallel=; the five calling =t.Setenv=
545 stay serial. =freePorts= allocates from an atomic counter instead of
546 binding =:0= and closing it, which raced once tests overlapped —
547 =waitForPort= only asks whether something is listening, so the loser
548 talked to another test's server.
549- Locally on 12 cores the suite goes from 637s to two or three minutes.
550 The =-timeout= floor the harness enforced (#143) is gone with the
551 reason for it; =make test= and =.gitbay/ci.yml= still pass their own
552 as a ceiling for a real hang.
553
554* v1.33.0 — 2026-09-21
555
556Five findings from the outside review of the web UI (#241–#245).
557
558- A run row on the builds page led with a ten-character sha, so
559 recognising a build meant opening the commit or already knowing the
560 sha (#241). =build list= resolves each distinct commit's subject in
561 one =git log= and returns it as =subject= on every build, so the CLI,
562 the API and the web all name the commit. The row leads with the
563 subject and the sha follows as metadata; a build whose commit is gone
564 falls back to the sha.
565- =build list= takes =--limit <n>= and =--cursor <c>=, the keyset
566 cursor =issue list=, =mr list=, =repo list= and =feed= already have
567 (#244). Without the flags it returns the newest fifty matching builds
568 as before, so existing scripts are unchanged — the cursor is what
569 reaches past that window. The page asks for thirty, offers "older"
570 carrying every filter, and says its count is this page's when there
571 is another. Before, filtering to a sparse status reached much further
572 back within the same cap and appeared to raise the run count.
573- The profile is sections rather than one stack (#242). =/{owner}= is
574 the repository list; About, Activity and an organization's People are
575 tabs beside it at =/{owner}/-/about=, =/-/activity= and =/-/people=.
576 A tab with nothing on it is not offered and its URL is a 404. The
577 About text and the year of activity squares used to sit above the
578 repository list and push it below the fold. =profile show= is
579 unchanged.
580- Explore names its filter: the number of repositories, the active
581 query and a link that clears it, the line the builds page already
582 carried (#243). An empty filtered list says nothing matched rather
583 than that the instance has no public repositories.
584- The landing page's picture was !315, closed without merging, with an
585 empty review panel and alt text promising reviewers that were not
586 there (#245). It is !450: merged, two CI checks reporting success
587 with how long each ran, and an approval. The picture is a figure with
588 a caption saying what it shows.
589
590* v1.32.1 — 2026-09-20
591
592A push alert names the account it is for (#89).
593
594- The payload carried =path= and nothing else, so a device signed in to
595 more than one account could not tell which instance a notice came
596 from: two instances can hold the same =owner/name=. It now carries
597 =instance=, the instance's =site_url=, and =user=, the recipient's
598 username — together the account's identity.
599- =DuePush= joins =users= for the recipient; no schema change.
600- =notifications device add= now returns the row id, so a client that
601 wants to deregister does not have to list devices and match its own
602 token against the truncated display value.
603- The alert carries =aps.badge=, the recipient's unread inbox count.
604 =DuePush= counts it at send time, a subquery against =inbox=, so a
605 cleared inbox is reflected even though the row was queued earlier.
606
607* v1.32.0 — 2026-09-20
608
609Push notifications to iOS devices (#89): activity reaches a registered
610phone the way it already reaches the inbox and mail.
611
612- gitbayd talks to APNs directly over HTTP/2, authenticated by an
613 ES256 JWT signed with an operator-supplied =.p8= provider key. New
614 config section =[push]=: =enabled=, =key_file=, =key_id=, =team_id=,
615 =topic= (the app's bundle identifier) and =environment=
616 (=production= | =sandbox=), all validated at load when enabled — a
617 misconfigured =[push]= refuses to start rather than filling a queue
618 nobody is watching. An APNs key belongs to a bundle id: a self-hoster
619 ships their own build under their own =topic= to use this; the App
620 Store build talks to gitbay.org.
621- Migration 0059: =push_devices= and =push_queue=, and
622 =users.notify_push= (default on).
623- =notifications device add= (token on stdin), =device list= (token
624 shown truncated), =device remove <id>=, and =notifications settings
625 push on|off=. A device is dropped automatically when Apple reports
626 the token dead (410 Unregistered or BadDeviceToken). With =[push]
627 enabled = false= nothing is queued and =device add= refuses, rather
628 than registering a device nothing can deliver to.
629- =[retention] push= caps the delivery queue, beside =mail=.
630- =dashboard= reports the push queue for admins beside the other five,
631 by device id: a =key_id= or =team_id= Apple did not issue passes
632 config validation and then dead-letters every send.
633- =issue assign= now files a notice, so assignment reaches the inbox,
634 mail and push.
635- Notification text is sent in full, private repositories included: a
636 repository's name and item number reach Apple and can appear on a
637 lock screen.
638- Web: the notification settings page carries the push toggle and the
639 device list, with removal behind confirmation. No web page offers a
640 device-add form — only the app can mint an APNs token.
641
642* v1.31.1 — 2026-09-20
643
644The stylesheet URL carries the build's hash (#239).
645
646- =/static/style.css= was served with a day's cache lifetime at an
647 unversioned URL, and =must-revalidate= only forces a check once that
648 lifetime expires. For a day after a deploy a browser rendered the new
649 markup against its old stylesheet; the ETag was never consulted.
650- The layout stamps the served bytes' hash on the link. A deploy changes
651 the URL, so a cached copy cannot answer it, and a request carrying the
652 current hash names bytes that cannot change and is served without
653 revalidating at all.
654
655* v1.31.0 — 2026-09-20
656
657The desktop layout (#226): the web UI uses a wide screen.
658
659- One centered container at 100rem; the repository header, main and
660 footer align on it. Text keeps its measure.
661- The repository header is two rows: name, description and buttons,
662 then the tabs.
663- Issue, merge request, build, explore, search and notification rows
664 are one line above 64rem, and those pages render at the container
665 width.
666- The dashboard is three columns: pinned repositories with open issue,
667 merge request and last-build counts; a tile per queue with the queue
668 rows below; the activity feed.
669- A file navigator beside blob, blame and edit pages lists the file's
670 directory and marks the file.
671- Side columns: state, labels and open milestones on the issue and
672 merge request lists; status, jobs and branches on builds; topics on
673 explore; kinds on search; sections on repository settings, account
674 settings and admin. A label or milestone nothing is filed under is
675 left out, so the merge request list offers the labels that have
676 merge requests rather than every label the repository holds; the
677 branch group caps at ten, and the branch field below it still takes
678 any ref.
679- Below 62rem the facet and section columns become a closed disclosure
680 before their content, headed by the filters in force, and the
681 navigator hides, since the tree page is the navigator on a phone.
682 Below 80rem the dashboard's pinned repositories return to a chip row
683 above the queues.
684
685Three accessibility defects the wider scan found, on pages the
686sixteen-page one never covered (#226):
687
688- A label chip carries a tone per scheme. Chip text is 12px, which owes
689 4.5:1 against the ground mixed from the colour itself, and no single
690 colour clears that on both canvases; the stored hex still names the
691 label, and the page picks the tone. A page stamped light or dark now
692 sets =color-scheme= to match, so native controls follow the theme.
693- Every =pre= scrolls sideways, so every one takes =tabindex="0"=: a
694 keyboard reaches a blame view, a build log and a search match the way
695 it already reached the pre blocks of rendered markup.
696- A link that shares its line with other text is underlined — a path
697 crumb, a heading that names an owner, an empty-state note. Link and
698 muted text are 1.07:1 apart in dark.
699
700The profile about text is a file (#236).
701
702*Upgrade note.* Run =gitbayd admin migrate-profile-about= after
703upgrading. Migration 0058 parks each owner's about text in a holding
704table and drops the columns; that command writes it into a public
705=<owner>/.gitbay=. Until it runs, profiles that had an about show none.
706Nothing is lost in between — the table keeps the text.
707
708- The about text on a profile is =profile/README.md= or
709 =profile/README.org= on the default branch of =<owner>/.gitbay=,
710 read with that repository's own access. The extension picks the
711 renderer; =.md=, =.org= and =.markdown= resolve in that order.
712 =profile show= gains =about_path=, the file the text came from.
713- =profile set= and =org profile= lose =--about=, =--about-format= and
714 =--file=. The about is written by a push or =repo commit-file=, the
715 way a wiki page is. The settings page points at the file and offers
716 to create the repository that holds it.
717- Repository names may start with a dot; owner names may not. A
718 repository whose name starts with a dot stays out of =explore= and
719 off the profile's repository list, and remains in =repo list= and at
720 its own URL.
721- =repo commit-file= writes the first commit of a repository that has
722 never been pushed to. An unresolvable branch is still an error
723 anywhere the repository already has refs.
724
725A web UI sweep.
726
727- The rail's squares are 44px at every width, and its glyphs are 20px
728 on a phone. Below 34rem eleven squares no longer fit, so explore,
729 bookmarks, snippets, new repository, settings, admin and log out
730 move into a More menu and the strip keeps dashboard, search,
731 notifications, More and your account.
732- Snippets are on the rail. The link on a profile page stays.
733- =/new= creates an organization as well as a repository; the form
734 leaves the profile page.
735- =repo fork= takes =--owner=, and the web's Fork button opens a form
736 with an owner and a name. The owner is you or an organization you
737 administer, checked as =repo create= checks it; an organization's
738 fork is not counted against your repository quota. A name of your
739 own is how you fork the same repository twice.
740- The dashboard's pinned key reads above the list rather than under
741 it, its build dot sits on the row's centre line, and a pinned chip
742 on the second row has its bottom border back.
743- The activity feed drops its state dot.
744- The SSH key and account tables keep each row on one line and scroll
745 sideways, rather than wrapping a fingerprint or a timestamp.
746- =.pathbar= actions sit on the centre line with the ref and the
747 crumbs.
748
749The SonarCloud dashboard is at zero (#238). Four of its 38 findings were
750real; the rest are dismissed with their reasons recorded on the
751dashboard.
752
753- A trailing-slash redirect cannot leave the site. =net/http= fills
754 =URL.Scheme= and =URL.Host= from an absolute-form request line, which
755 RFC 7230 requires a server to accept, so =GET http://evil.example/cmc/=
756 answered =301 Location: http://evil.example/cmc=. A browser sends
757 absolute form only to a proxy, so nothing reached this through one
758 directly.
759- The global search, repository search and register forms no longer
760 carry =autofocus=, which moved focus past the heading, the result
761 count and the search page's filters. The diff line-comment box keeps
762 it: that form renders only after the reader asks for it on a line,
763 and with no JavaScript nothing else carries focus across the reload.
764
765* v1.30.0 — 2026-09-19
766
767Every command runs on every surface, markup previews before it is
768written, and the web findings from the forge comparison (#232, #233,
769#234, #235).
770
771*Upgrade note.* Dropping =SSHOnly= widens what a full-scope API token
772can do: it can now administer the instance and mint further tokens.
773Review the tokens you have issued and re-mint as =--scope read= any
774that only need to read.
775
776- *Every command now runs on every surface.* The registry's =SSHOnly=
777 flag is gone, and with it the refusal that met build secrets, mirror
778 credentials, API token minting, web sessions, deploy keys, the audit
779 log and instance administration when they arrived over HTTP. What a
780 caller may do is the account's rights narrowed by the scope of the
781 key or token the request came with, decided in one place. A
782 full-scope API token can now do anything its owner can, minting
783 another token included; a read-scoped one still cannot write.
784 Operators should review the tokens they have issued and re-mint as
785 =--scope read= any that only need to read (#234).
786- =/admin/users= lists every account with the state filter and cursor
787 =admin user list= takes, and runs promote, demote, disable and enable
788 per row. Demote and disable ask for the username to be typed (#234).
789- =[registration] notify_admin= mails the instance's admins when an
790 account becomes active: an invite redeemed, or an open-mode signup
791 that verified its address. Off by default, requires =[mail]=, and
792 queued like any other notice (#234).
793- Every web form that takes markup has a Preview button beside its own
794 submit: issue and merge request create, their edit and comment boxes,
795 release create and edit, the profile about text, and the file editor
796 on a path the forge renders. It renders the draft above the textarea
797 and writes nothing (#235).
798- Links inside running text are underlined: the meta lines on issues,
799 merge requests and releases no longer tell a link apart by colour
800 alone.
801- File view line numbers are 24px targets and keep the focus ring;
802 chroma's LineLink rule, which set =outline: none=, is dropped from the
803 served palette.
804- Every rendered =<pre>= and the landing page's quickstart block take
805 keyboard focus, so a block that scrolls sideways can be reached.
806- On one column the issue and merge request aside follows the thread
807 instead of preceding it.
808- The file tree at 320px keeps its last column inside the card.
809- A path no route matches renders the 404 page instead of a plain-text
810 body.
811- An org image link with no description gets its file name as alt text,
812 so a README badge is a named link.
813- Release titles are h2.
814- Text responses are gzipped for clients that accept it.
815- =web theme set system|light|dark= and an Appearance section on the
816 account page fix the colour scheme per account. Migration 0057 adds
817 =users.theme=.
818- A path that only misses because of a trailing slash redirects to the
819 path without it: =/cmc/= reaches =/cmc=, =/cmc/-/snippets/= reaches
820 =/cmc/-/snippets= (#233).
821
822* v1.29.0 — 2026-09-19
823
824The icon nav is a top bar at every width.
825
826- The 48px row of glyphs that narrow screens already used is now the
827 only shell layout; the left column is gone. The row keeps the same
828 order, labels and current-page mark, with settings, admin and the
829 account cell at the far right.
830- The landing picture is recaptured under the new shell.
831
832* v1.28.1 — 2026-09-19
833
834The newcomer route names its web path (#226).
835
836- After registering, the page and the verification mail say the code
837 can be pasted under Settings after signing in with an emailed link,
838 beside the terminal command.
839- The SSH keys wiki page names this instance instead of a placeholder;
840 the Quickstart leads with the browser route and Homebrew before
841 =go install=.
842
843* v1.28.0 — 2026-09-19
844
845Labels on merge requests (#231), and a one-column dashboard. Migration
8460056 adds =mr_labels=; the daemon migrates on start.
847
848- =mr label <owner/name> <n> --add <l> --remove <l>= attaches and
849 detaches labels the way =issue label= does, resolving an org's label
850 first and creating a repository label on the fly; =mr list --label=
851 filters; =mr show= carries them; the event is =mr.labeled=.
852- The merge request page has a Labels group with the same form as an
853 issue; list rows show label chips and =?label== filters the list.
854- =label list= and the labels pages count merge requests beside issues;
855 removing a label detaches it from every issue and merge request. An
856 org label folding repository rows moves merge request rows too.
857- The dashboard is one column: the activity feed is a section after
858 the queues, since the icon rail leaves no wide column to balance.
859
860* v1.27.0 — 2026-09-19
861
862The follow-ups from the forge benchmark (#226) and two profile fixes.
863
864- On a wide repository overview the About block (counts, licence, latest
865 release, build, contributors, languages) and the clone commands sit in
866 a column beside the file table; under 62rem the order is unchanged
867 (#228).
868- The landing page's Explore and Create an account routes sit above the
869 picture, and the picture is capped so the first screen carries a call
870 to action (#229).
871- Each row of the merge request list shows the combined check state of
872 its head, linking to the diff, and a comment count (#230). Labels on
873 merge requests do not exist yet (#231).
874- The profile page lists repositories after the activity graph, and a
875 table in rendered prose keeps its last row's bottom border (#225).
876
877* v1.26.0 — 2026-09-18
878
879A closed merge request can name the request that carried its change
880(#223). Migration 0055 adds the column; the daemon migrates on start.
881
882- =mr close <owner/name> <n> --by <m>= records, at close time, that !m
883 supersedes !n; =mr edit <n> --superseded-by <m>= sets it on a request
884 already closed and =--superseded-by none= clears it. Both refuse a
885 number that is not a request in the same repository, or the request
886 itself. =mr show= carries the field.
887- The web close form takes the number as an optional field. The closed
888 request's title line says "in favour of !m"; the request it names
889 says "supersedes !n". The state stays closed; nothing is inferred
890 from prose.
891- On a phone the dashboard's activity feed stacks after the queues; the
892 aside-first rule is for checks and reviewers on a merge request
893 (#222).
894
895* v1.25.0 — 2026-09-18
896
897The site rail is an icon column (#220).
898
899- At desktop the rail is a 3.5rem column of inline glyphs: dashboard,
900 explore, search, notifications with the unread count as a badge,
901 bookmarks, new repository, then settings and admin, then the account
902 and sign-out. The search field leaves the rail; =/search= has its own.
903- Under 52rem the rail is one 48px row that neither wraps nor scrolls.
904- Every icon link carries an accessible name (=aria-label=, a title and
905 visually hidden text) and hides its SVG from assistive tech; a test
906 enforces it.
907- Pinned repositories are a chip row under the dashboard heading; the
908 review queue is the dashboard's section. Neither is in the rail.
909
910* v1.24.1 — 2026-09-18
911
912The dashboard feed and the phone-width rail strip (#222, #220).
913
914- Build events record their commit; the dashboard's activity feed folds
915 a commit's jobs into one line per run with the combined state and a
916 state dot. A status outside the known set is never shown as success.
917- Feed times are relative, with the exact UTC time in a title, as the
918 tree listings already do.
919- Under 52rem the rail strip keeps the brand on its first row, shows
920 pinned repositories as a compact labelled sub-row, and New repository
921 is a =+= button at every width.
922
923* v1.24.0 — 2026-09-18
924
925The web follow-ups to the design foundation (#219, #220, #221, #222,
926#224, #225), and a repository maintenance command.
927
928- =build list= takes =--ref=, =--status= and =--job=, pushed down to the
929 store query; the builds page reads the same three as GET parameters
930 with shareable links, and groups a commit's jobs into one run showing
931 the combined state (#224).
932- The merge request page's "Files changed" view is wide; the
933 conversation and commits views stay at reading width (#219).
934- The profile page lists repositories above the biography; the
935 contribution grid carries month labels and a legend (#225).
936- The dashboard shows populated queues first, collapses empty ones to a
937 heading, and says what the two Open lists cover (#222, in part).
938- Under 52rem the rail strip keeps one scrolling row and shows pinned
939 repositories as a second row instead of hiding them (#220).
940- Polish from the v1.23.0 review: caption spans instead of dangling
941 labels, runner attach keeps a rejected key and reports success, the
942 tree root of the default branch is the repository home so the header
943 is identical within the code tab, the file editor is wide (#221).
944- =admin mr prune <owner/name> <n>... --yes= drops the named merged or
945 closed MRs' =refs/merge-requests/N/head= and runs =git gc --prune=now=
946 on the repository, for commits a history rewrite left reachable only
947 through them. Open and source-gone MRs are refused. Nothing drops a
948 head ref on its own. =mr diff= and the MR page say when a head is gone
949 (#227).
950
951* v1.23.0 — 2026-09-17
952
953The web design foundation (#218). Tokens measured in both schemes, one
954control family, content widths per page, and the landing, repository
955overview, merge request and settings pages recomposed. Set =[web]
956title= to =gitbay= in lower case; the templates already are.
957
958- =style.css= rewritten on tokens defined on =:root= and again for dark;
959 =TestTokenContrast= enforces the floors and
960 =TestEveryTemplateClassHasARule= that every template class has a rule.
961- Buttons are primary, secondary, quiet or destructive; one focus ring on
962 everything; success and error flashes share one shape.
963- Every page picks a width: wide for code, reading for lists and threads,
964 bounded for forms.
965- The repository header shows description and topics on the code tab
966 only; the overview leads with the file table and puts clone commands
967 and facts after the README; "Find file" is "Search code".
968- A merge request states who merged or closed it under its title and
969 explains an empty diff.
970- Repository settings are bounded rows with a consequence beside each
971 control, a saved flash, a rejected value kept, and topics as one field.
972- Landing copy says what the product is and where to go; the register
973 form says to paste the contents of the key file and links the SSH keys
974 wiki page.
975- The landing page shows the merge request page, light and dark,
976 captured from gitbay.org (two embedded PNGs under =/static/img/=).
977
978* v1.22.1 — 2026-09-13
979
980One merge gate fix.
981
982- =require-checks= no longer refuses a merge request head that carries
983 no statuses when nothing was going to report one: a repository with
984 no =.gitbay/ci.yml=, or one whose jobs all wait on a schedule or a
985 tag, had no mergeable merge request and no remedy but turning the
986 setting off. A head whose config carries a job a push runs, and a
987 head in a repository that has recorded a status before — which is
988 what reporting from outside through =status set= looks like — is
989 still refused (#216).
990
991* v1.22.0 — 2026-09-12
992
993The CLI output sweep (#183). The rules are on the wiki's Users page,
994under "Output rules".
995
996- A bad invocation prints the command's registered usage, the one
997 source of it; the hand-written copies are gone.
998- The =gitbay= CLI pads list rows into aligned columns at a terminal
999 and leaves the tabs alone when piped.
1000- An empty list prints nothing on stdout and =nothing to list= on
1001 stderr.
1002- Every refusal (exit 4) says what to do instead.
1003- =status list= and =repo topics= print rows.
1004- =admin runners remove=; =forget= stays as an alias until the next
1005 release.
1006- A missing positional argument prints the hint and the usage line
1007 (#215).
1008
1009* v1.21.0 — 2026-09-12
1010
1011The web UI/UX sweep (#182).
1012
1013- Destructive controls ask for the object's name typed beside the
1014 button: release delete, snippet delete and file remove, team delete,
1015 label remove, and SSH key, email and PGP key removal. Reversible
1016 controls keep a plain button.
1017- Login returns to the page that asked for it, and says so.
1018- One timestamp format everywhere, =2006-01-02 15:04 UTC=.
1019- Tags on the refs page and in the release form are in version order,
1020 newest first.
1021- The file editor explains up front when signed commits or
1022 merge-requests-only protection would refuse the commit, answers 404
1023 for a branch that does not exist, and says when a path is new.
1024- Merge refusals name the strategy rather than the flag; an issue
1025 closed by a commit reads "closed by <who> in commit <sha>".
1026- Repository settings: every Save names its field. Labels: the colour
1027 column appears only when it means something. Sidebars use one shape
1028 for empty. List rows show the state only under "all" and say "in
1029 <milestone>". Global search counts its results. A merged MR shows
1030 its merged head and a deleted source branch. The repository home
1031 shows the SSH clone URL beside HTTPS. The settings page names
1032 =auth token create=.
1033
1034* v1.20.1 — 2026-09-11
1035
1036One config check.
1037
1038- A negative =limits.max_snippets_per_user= is refused at config load,
1039 as =max_repos_per_user= and =max_bytes_per_user= already were; it
1040 used to pass validation and read as unlimited (#214).
1041
1042* v1.20.0 — 2026-09-11
1043
1044Snippets (#195): named text files a user owns outside any repository,
1045shared by URL and edited in place.
1046
1047- Migration 0054: =snippets= and =snippet_files=.
1048- =snippet create|show|list|edit|delete= and =snippet file
1049 set|get|remove=. Files are UTF-8 under =limits.max_snippet_bytes=
1050 (1MB), at most 64 per snippet; a snippet keeps at least one.
1051 =limits.max_snippets_per_user= (0, unlimited) caps how many an
1052 account may own, admins included. Visibility =public=, =unlisted=
1053 (default) or =private=; a private snippet is not found to everyone
1054 but its owner and admins.
1055- Web: =/<owner>/-/snippets= lists, each snippet page renders its
1056 files with a raw route per file, and the owner creates, edits and
1057 deletes from the page through the same commands. The owner page
1058 links to the list.
1059
1060* v1.19.0 — 2026-09-11
1061
1062Labels and milestones an org defines once for every repository under
1063it, and =Closes owner/name#N= acting across repositories (#203).
1064
1065** Org labels and milestones
1066
1067- Migration 0052: =labels= and =milestones= rows belong to a
1068 repository or to an org, exactly one, with a partial unique index
1069 per scope. Existing rows and their memberships keep their ids.
1070- A repository owned by an org sees the org's labels and milestones
1071 beside its own; =issue label --add=, =issue milestone= and =mr
1072 milestone= resolve the org's row first. A repository cannot create,
1073 recolour, remove, close or reopen a name its org holds; the refusal
1074 names the org command.
1075- =org label set|list|remove= and =org milestone
1076 create|list|close|reopen=, for org admins. Creating a name that
1077 repositories under the org already use folds them in: their issues
1078 and merge requests move to the org's row and the repository rows
1079 go. =repo transfer= into an org folds the same way. Counts on org
1080 rows span the repositories the caller can read.
1081- Web: read-only =/<org>/-/labels= and =/<org>/-/milestones=, linked
1082 from the org page; an "org" mark on repository label and milestone
1083 pages, whose forms act on repository rows only.
1084- =label list= and =milestone list= JSON carry =org: true= on an org
1085 row.
1086
1087** Cross-repository closes
1088
1089- =Closes owner/name#N= in a commit on the default branch, or in a
1090 merged merge request's title or body, closes that issue when the
1091 actor holds write on the target and the pushing key's scope allows
1092 it: a deploy key never acts outside its binding. An unknown or
1093 refused target does nothing and logs nothing; the text stays a
1094 plain autolink. An archived target is refused. Bare =owner/name#N=
1095 without a keyword stays display-only.
1096
1097** Store
1098
1099- A migration whose first line is =-- foreign_keys: off= runs on one
1100 pinned connection with foreign keys off, re-enabled afterwards and
1101 =foreign_key_check= required empty. Rebuilding a table other tables
1102 reference loses the children's rows otherwise, even under
1103 =legacy_alter_table=.
1104
1105** Behaviour changes
1106
1107- =milestone create= exits 1 on a duplicate title, as =org milestone
1108 create= does; it exited 2 before.
1109
1110Upgrade: replace the binary and restart; migration 0052 runs on
1111start and copies every label and milestone row once.
1112
1113* v1.18.1 — 2026-09-11
1114
1115A runner that cannot hang on a dead connection, SSH keys with names,
1116and dependency updates.
1117
1118** CI runner
1119
1120- Every ssh invocation carries =ConnectTimeout=10=,
1121 =ServerAliveInterval=15= and =ServerAliveCountMax=3=, placed after
1122 the identity and the operator's =-ssh-opts= so an operator's value
1123 wins. A claim whose TCP session had died under it blocked a laptop
1124 runner's poll loop for thirteen hours; it now fails within a minute
1125 and the loop resumes.
1126- The build comment in =deploy/Containerfile.ci= stages the file in
1127 the runner user's home before =podman build=: a login shell under
1128 =su= cannot read root's stdin and does not share root's =/tmp=.
1129
1130** Keys
1131
1132- SSH keys carry a label (migration 0051). =keys add --label= defaults
1133 to the authorized_keys comment; =keys label <fingerprint> [<text>]=
1134 renames or clears it. =keys list=, =admin user show=, =repo
1135 deploy-key list= and the settings page show it. Deploy, runner and
1136 admin-created keys take the comment as their label. Closes #208.
1137
1138** Web
1139
1140- Org autolinks stop before trailing punctuation: a bare URL closing a
1141 sentence or a parenthesis no longer takes the =.=, =,= or =)= into
1142 the href. Closes #209.
1143
1144** Dependencies
1145
1146- golang.org/x/crypto 0.57, x/image 0.46, x/net 0.59, x/term 0.46.
1147 Closes #205.
1148
1149* v1.18.0 — 2026-09-10
1150
1151What the first real job on a user's runner needed. A twice-daily
1152archive pull that had run on the server's host moved into a container
1153and then onto a laptop, and each hop found a gap.
1154
1155** CI runner
1156
1157- A secret with newlines — a private key — reaches the build. An env
1158 file has no escape for one, so such values are named on podman's
1159 command line with =--env NAME= and valued in the podman process's own
1160 environment; the value touches neither argv nor the file.
1161- =GITBAY_SSH= in every build's environment: the instance's ssh
1162 destination as the build reaches it. Under podman the host's own
1163 addresses belong to the container (pasta), so a loopback remote is
1164 rewritten to the address pasta exposes the host at. A job that
1165 publishes back to the instance uses the variable rather than
1166 guessing. Inside a container =ssh= expands =~= from the passwd entry,
1167 not =$HOME=; keep a build's ssh config in the workspace and pass =-F=.
1168- =-identity= drops the user's =~/.ssh/config= (=-F /dev/null=):
1169 =IdentitiesOnly= kept identities the config named, so a laptop runner
1170 authenticated as the user's own full-scope key and, on an admin's
1171 machine, could claim every repository's builds. A first-seen host key
1172 is accepted, since a service cannot answer a prompt.
1173- A schedule tick queues nothing while the job's last build is pending
1174 or running, matching the push path. A repository no runner served
1175 gained one row per tick forever. A finished build does not suppress
1176 the tick; a schedule re-runs an unchanged commit on purpose. #206
1177- =admin runners forget <fingerprint>= drops a key's heartbeat row; the
1178 key stays. =admin runners= rows are the repositories a key may claim.
1179- The bay1 unit names no =-repos=: the runner key's attachments are the
1180 boundary. =gitbay-ci:2= carries =python3-venv= and =sqlite3=, since
1181 it is also the default image for every repository the runner is
1182 attached to.
1183
1184** Decisions
1185
1186- Claim order stays oldest-first across everything a key may claim; a
1187 repository that must never wait on another gets a runner of its own.
1188 #207
1189- No per-account cap on queued builds and no schedule floor: with the
1190 tick dedupe a repository with no runner holds one row per scheduled
1191 job, and a busy schedule spends its owner's compute. #206
1192- Attaching a runner is =n/a= on iOS: the key lives on the machine that
1193 runs builds.
1194
1195** Documentation
1196
1197- Users: =GITBAY_SSH=, ssh's home inside a container, the =ci.yml= caps
1198 (ten jobs, fifty steps, 4096 bytes a step, 64 KiB a file) and where a
1199 broken config shows up. Admin, CI and Threat-Model follow the changes
1200 above.
1201
1202** Upgrading
1203
1204Replace the binaries and reinstall the CLI. No migration. A runner
1205started with =-identity= (every runner =gitbay-runner init= set up) now
1206ignores =~/.ssh/config=; a runner that relied on it for a =ProxyJump=
1207or an alias passes the equivalent in =-ssh-opts=. Homebrew:
1208=brew upgrade krz/tap/gitbay-runner=.
1209
1210* v1.17.0 — 2026-09-09
1211
1212CI without the operator's compute: a runner anyone installs and
1213attaches to their own repositories, and the server rule that makes
1214that safe. The rest of the #184 list besides.
1215
1216** CI
1217
1218- A runner key claims builds only for the repositories it is attached
1219 to. =repo runner add <owner/name> < key.pub= attaches one; a key the
1220 server has not seen lands on the caller's account with scope
1221 =runner=. =repo runner list= shows each attached key with its last
1222 poll and the build it holds; =repo runner remove <fingerprint>=
1223 detaches it. All three on the settings page. A runner-scoped key
1224 with nothing attached claims nothing, whoever owns it; a full-scope
1225 admin key still claims any repository. =runner log= and =runner
1226 done= refuse a build outside the key's attachments. #184
1227- Closed: any account could add a runner-scoped key, and =runner next=
1228 with no arguments handed it the oldest pending build on the
1229 instance, secrets included.
1230- =runner next --untrusted=: without it a merge request head from a
1231 fork is never claimed. The runner passes it when started with
1232 =-untrusted=; the bay1 unit does, because it isolates in podman.
1233- =gitbay-runner init= generates a key under =~/.config/gitbay-runner/=,
1234 writes =config.toml= beside it, and prints the public key with the
1235 command that attaches it. The runner reads that file when present
1236 and flags override it. =-identity=, defaulting to the generated key,
1237 makes ssh and git use the runner's own key and no other. Homebrew:
1238 =brew install krz/tap/gitbay-runner=, then =brew services start
1239 krz/tap/gitbay-runner=. Releases ship =gitbay-runner= binaries.
1240- =admin runners= heads its output with the queue: builds pending now,
1241 and over the last day the builds claimed, the wait to claim (average
1242 and worst) and the builds the reaper ended instead of a runner
1243 reporting them. Rows are per key, with the fingerprint and the
1244 repositories the key may claim. Migration 0049. #184
1245- Stop tests for the runner's drain: a signal mid-step, the drop-in's
1246 =KillMode= and =TimeoutStopSec=, and a transient systemd user unit
1247 where one exists. #179
1248- The CI wiki page carries every push shape against every job kind and
1249 what dedupe, path filters, schedules and the reaper make of it, with
1250 a test per row. #176, #177
1251
1252** Importing
1253
1254- =import-issues --api-base= reads Forgejo instances: paging by =limit=,
1255 oldest first, comments read once, attribution and pull heads taken
1256 from the API base rather than github.com. #191
1257
1258** Documentation
1259
1260- Users: "Your own runner". Admin, Threat-Model, CI, FAQ and Parity
1261 follow the attachment rule.
1262
1263** Upgrading
1264
1265Replace the binaries and reinstall the CLI. Migration 0050 (runner
1266attachments; the runner heartbeat table is rekeyed by key and
1267emptied), applied on start. One behaviour change: a runner polling
1268with a key of scope =runner= claims nothing until a repository admin
1269attaches it with =repo runner add=. Do that right after the restart.
1270A full-scope admin key is unaffected. Merge request heads from forks
1271are built only by a runner started with =-untrusted=.
1272
1273* v1.16.0 — 2026-09-08
1274
1275What stops a stranger from moving here: the repository plumbing and
1276the team gates the #185 walk found missing, twelve merge requests
1277merged as one stack.
1278
1279** Repositories
1280
1281- =repo settings default-branch <owner/name> <branch>= moves HEAD and
1282 the record; a branch that does not exist is refused. A first push of
1283 =master= or =trunk= into a fresh repository moves the unborn HEAD to
1284 the branch that arrived, so the clone checks something out. Settings
1285 page select. #189
1286- =repo rename <owner/name> <new-name>=: the row and the directory move
1287 together, with transfer's revert on a failed move. Clone URLs change.
1288 #190
1289- =repo settings require-mr on=: an existing protected branch refuses
1290 every direct push in pre-receive, =repo commit-file= and the web
1291 editor included; =mr merge= is its only writer. Creating the branch
1292 is still a push. #197
1293- =repo settings protect-tag <glob>= (and =unprotect-tag=): matching
1294 tags are created once and refuse moves and deletion. Separately, a
1295 tag a release is anchored to refuses both while the release exists,
1296 protected or not; delete the release first. #201
1297- =repo access list= reports effective access: one row per account
1298 with the highest role and where it comes from (owner, direct, org
1299 admin, org member, team). It used to list direct grants only, so a
1300 repository reached through teams answered with nothing. #200
1301- Removing an org member drops their team memberships in the same
1302 transaction. They kept every grant their teams carried, and re-adding
1303 them to the org restored nothing because nothing had gone. #196
1304- An outsider gets one answer about an org: its existence and members
1305 are public, its teams are for members, and =org team list= and =show=
1306 refuse a non-member rather than say the org does not exist. Ref #200
1307- A repository name may not end in =.atom=, as it may not end in
1308 =.git=. Ref #192
1309
1310** Merge requests
1311
1312- A push that leaves the merge request's diff unchanged keeps its fresh
1313 reviews: the patch-id of each revision against its own merge base is
1314 compared, and a rebase onto a target that moved on no longer stales
1315 every approval. A push that changes the diff stales them as before.
1316 #198
1317- The merge gates are one computation shared by =mr show= (a =gates=
1318 block: approvals counted and required, owners outstanding per file,
1319 open threads, checks, whether a fast-forward is possible), the merge
1320 request page, and =mr merge=, which names every unmet gate in one
1321 refusal rather than the first. =mr review= reports =counts= and says
1322 when a verdict is advisory because the reviewer cannot write. #199
1323
1324** Notifications
1325
1326- =@name= in an issue, merge request, comment or diff comment files
1327 "mentioned you" in that account's inbox and makes them a participant
1328 of the thread, provided they can read the repository and have not
1329 muted it. Watchers are not told about a mention addressed to someone
1330 else. Migration 0047. #202
1331- =notifications settings mail on|off= (and =show=): inbox rows are
1332 filed either way, this is the mail half. Login links are not activity
1333 and still arrive. The account page carries the same switch.
1334 Migration 0048. Ref #194
1335
1336** Web
1337
1338- Atom feeds: =/{owner}/{repo}/releases.atom=,
1339 =/{owner}/{repo}/log.atom[/{ref}]= and =/{owner}/activity.atom=,
1340 rendered over the rows the pages already serve. The owner feed covers
1341 public repositories only, since a reader carries no session; a
1342 private repository answers 404. The releases, log and owner pages
1343 carry the discovery link. #192
1344
1345** Documentation
1346
1347- The Users page says what differs over stock ssh: a multi-word value
1348 needs a second layer of quotes, and =help <noun>= replaces =--help=.
1349 The companion-wiki paragraph #170 made stale now points at
1350 =.gitbay/wiki/=. #204
1351
1352** Upgrading
1353
1354Replace the binary and reinstall the CLI. Two migrations (0047, the
1355mentions table; 0048, the per-account mail switch), applied on start.
1356Nothing changes behaviour until a setting is turned on: =require-mr=,
1357=protect-tag= and =mail off= are all opt-in.
1358
1359* v1.15.0 — 2026-09-07
1360
1361Builds run in containers, a rebase is not rebuilt, and a runner restart
1362no longer strands the build it was running.
1363
1364** CI
1365
1366- A build's steps run in a rootless podman container, one per job. The
1367 runner clones outside the container with its key and bind-mounts the
1368 workspace in, so a step cannot reach the key, the runner's environment,
1369 or another build's workspace. =image:= is required per job and is
1370 validated as a reference, never pulled: an operator provisions images
1371 on the host. A runner configured for podman that has none refuses to
1372 start rather than fall back to the host. =-isolation none= is the
1373 explicit host-execution mode. =-cpus= and =-memory= cap a build's
1374 container. #144
1375- Builds have a home directory that outlives the build, so the Go module
1376 cache and the sonar scanner survive between runs. It is mounted into
1377 the container at the same path, and only that directory. Ref #144
1378- The host preparation script, the unit drop-in and the weekly image
1379 prune ship with =make deploy-runner=; each hardening flag the drop-in
1380 relaxes carries the reason in place. Ref #144
1381- A nightly canary on the runner host proves the boundary holds:
1382 =cmc/ci-smoke= runs a job that tries to read the key and list sibling
1383 workspaces, and fails if either succeeds. Ref #144
1384- Dedupe keys on the commit's tree, not its sha. A rebase that changes
1385 nothing is not rebuilt: the new commit gets the earlier success as its
1386 status, naming the build. Scheduled and tag builds carry no tree and
1387 are never reused. #177
1388- =vuln= and =sonar= run nightly on =main= rather than on every push;
1389 neither could inform a merge. Branches run =build= and =test=. #177
1390- A rewritten branch is filtered against the merge base rather than the
1391 old tip, so a rebased branch whose own commits change code no longer
1392 reads as a docs-only push and skips its jobs. #176
1393- A build whose runner's log stream ended with no outcome is failed two
1394 minutes later, instead of sitting =running= until a fixed deadline.
1395 Migration 0046. Ref #179
1396- The runner retries reporting a finished build's outcome, four times
1397 over about thirty seconds, when the server is unreachable. A gitbayd
1398 restart at that moment used to lose the result. Ref #179
1399- The runner drains on SIGTERM: it claims nothing more, finishes and
1400 reports the build in flight, then exits. A second signal exits at once.
1401 The unit allows fifty minutes. #179
1402
1403** Repositories
1404
1405- =repo show= reports the caller's watch and bookmark state, and the
1406 parent of a fork when the caller can read it. #178
1407- =repo unwatch= clears the row from either state; =repo mute= is the
1408 explicit silence. Watch then unwatch used to leave an account below
1409 the default with no way back. The web header toggle follows. #180
1410
1411** Upgrading
1412
1413Replace the binary and reinstall the CLI. One migration (0046, the
1414build log's close time), applied on start.
1415
1416The runner now defaults to =-isolation podman= and refuses to start
1417without a working podman and a named image. Prepare the host with
1418=deploy/runner-podman-setup.sh= and build =localhost/gitbay-ci:1= from
1419=deploy/Containerfile.ci= before deploying it, or pass =-isolation
1420none= to keep running steps on the host. Validate on a scratch
1421repository with =-repos= scoped to it first; the wiki's Admin page has
1422the procedure.
1423
1424The runner's unit gains =TimeoutStopSec=50min= and =KillMode=mixed= so
1425a stop reaches the runner alone and it can drain; under the default
1426kill mode systemd ends the build's container with the runner.
1427=make deploy-runner= therefore waits for a build in flight.
1428
1429* v1.14.0 — 2026-09-06
1430
1431Logging into the web without an SSH key, wikis inside the repository,
1432CI that skips what a change does not touch, and the browser catching up
1433with the command line on nine capabilities.
1434
1435** Accounts and the web
1436
1437- A browser session can be requested by mail: the login page takes a
1438 username or a verified address and sends a link that works once and
1439 expires in fifteen minutes. An account with no SSH key had no way into
1440 the web at all. The response never says whether the account exists, and
1441 the form appears only when the instance has SMTP. #155
1442- A login link resolves to any verified address on the account, not only
1443 the primary. #158
1444- Login mail is queued rather than sent from a goroutine, so a link in
1445 flight survives a restart. #159
1446- A suspended account cannot mail itself a session, and a link minted
1447 before suspension opens nothing. #156
1448- The session cookie is =SameSite=Lax=, and a test now walks every
1449 mutating route to assert it carries the origin check. #157
1450- =POST /register= is reachable on an open instance again.
1451
1452** Wikis
1453
1454- A wiki lives at =.gitbay/wiki/= on the default branch, so editing one
1455 is editing a file in the repository — a push, or the web editor — and
1456 it is cloned, diffed and reviewed like anything else. The companion
1457 =<repo>.wiki= is gone. #170
1458
1459** CI
1460
1461- Path filters: =paths= and =paths-ignore= per job, so a docs commit
1462 does not run the whole suite. #169
1463- A branch's first push derives its diff base from the merge base
1464 rather than treating every file as changed. #171
1465- A job filtered out records a skipped status instead of nothing, so
1466 =require_checks= cannot wait forever for a check that will never
1467 arrive. #172
1468- A force-push no longer leaves queued builds pointing at an object
1469 that is gone; the orphan is cancelled when a runner claims it. #152
1470- A build step's environment is constructed rather than inherited. It
1471 was =os.Environ()= plus the build's variables, which handed repository
1472 content everything set on the runner service. A step now gets =PATH=,
1473 =HOME=, =LANG=, =CI=, its =GITBAY_*= variables and its secrets. =HOME=
1474 is the workspace, so a build cannot read the runner's =.netrc=,
1475 =.npmrc= or =.gitconfig=, where tools keep credentials. Ref #144
1476- A runner host can be prepared for rootless podman:
1477 =deploy/runner-podman-setup.sh=, the systemd changes it needs, and
1478 weekly image pruning. Nothing reads them yet; the preparation ships
1479 before the runner that requires it, on purpose. Ref #144
1480
1481** Collaboration
1482
1483- =mr review request --add <user>= asks a particular person for a
1484 review, who then carries it in their queue and is notified;
1485 =--remove= withdraws the ask. The queue was computed from involvement
1486 alone, so a collaborator who had not touched a thread heard nothing.
1487 #145
1488- Bookmarks save someone else's repository to come back to, and the
1489 count is the instance's only popularity signal. Separate from pins
1490 rather than a flag on them: a pin is private quick access to your own
1491 work and drives the rail, a bookmark is public and counted. =repo
1492 bookmark=, =repo unbookmark=, =repo bookmarks=, a control on the
1493 repository header, the count in the facts bar, and =/bookmarks=. Read
1494 access is all a bookmark needs, and one made while a repository was
1495 public drops out of the listing if it goes private. #146
1496
1497** The browser catches up
1498
1499Nine capabilities that were CLI-only and had no reason to be:
1500
1501- label management — list, create, colour, remove #163
1502- dependency status under the toggle that turns checks on #164
1503- release delete #165
1504- the account export bundle, as a download #166
1505- organization create and rename; delete stays CLI-only, wanting a
1506 typed confirmation, and the page says so #167
1507- opening a merge request from a fork, with a source picker offering
1508 the branches of every fork you can push to #168
1509- forking a repository #174
1510- cancelling a queued or running build #162
1511- the profile form #161, and a markup picker on issue and merge
1512 request create #160
1513- admin table headers align with their columns #151
1514
1515** CLI
1516
1517- =gitbay mr rebase <n>= replays a merge request's branch onto its
1518 target and re-pushes it. A repository requiring signed commits accepts
1519 only fast-forward merges, so a merge request whose target moved had to
1520 be rebased by hand; the refusal already named the procedure and this
1521 runs it. The git work is local, so the replayed commits carry your
1522 signature — the server still holds no key. A branch in a fork is
1523 refused, naming the repository to run it in. #175
1524
1525** Security
1526
1527- Mutating commands are bounded per account in the dispatcher, so SSH,
1528 the JSON API and the web spend one budget and a caller cannot refresh
1529 it by changing surface. Authentication failures were throttled;
1530 commands were not. #148
1531- A dead-lettered mail is logged by its queue row id, not the recipient
1532 address, and the relay's error is redacted before logging because a
1533 rejection quotes the address it rejected. The address stays on the
1534 row, where =/admin= shows it. One rule for every mail type. #173
1535- The 2026-09 sweep's coverage — and what it did not reach — is recorded
1536 in the wiki's Threat-Model rather than in a closed issue. #149
1537
1538** Dependencies
1539
1540- goldmark 1.8.6, sqlite 1.58.0. #140
1541
1542** Upgrading
1543
1544Replace the binary and reinstall the CLI. One migration (0043,
1545bookmarks), applied on start.
1546
1547=limits.write_rate= defaults to 60 mutating commands a minute per
1548account. A script that writes faster will be refused with exit 4 and a
1549retry time; raise it in =[limits]=, or slow the script. Read-only
1550commands, the runner protocol and the host CLI are not counted.
1551
1552A companion =<repo>.wiki= repository is no longer read. Move its pages
1553to =.gitbay/wiki/= on the default branch.
1554
1555Runner isolation is half done. Builds still run as the runner's user
1556with no container: the step environment no longer leaks the service's,
1557and a host can be prepared for podman, but nothing yet executes a build
1558in one. Do not enable CI for repositories you do not trust. #144 stays
1559open for the execution half.
1560
1561* v1.13.3 — 2026-09-05
1562
1563Only a writer's review decides a merge gate, and a scan of one branch
1564stops overwriting another's results.
1565
1566- =mr review= resolves with =CanRead= and applied no further check, and
1567 the merge gates counted every fresh verdict. On a public repository
1568 that let anyone with an account satisfy =require_approvals= — defeating
1569 four-eyes review by holding two accounts, which on an instance with
1570 open registration means defeating it outright — and equally let a
1571 passer-by block a merge the owner wanted, with no override and only a
1572 force-push to clear it. Both were confirmed against a running instance.
1573 Reviewing stays open to every reader, because an outside opinion on a
1574 public change is worth having; it no longer decides the gate. What
1575 does is write access, the same question the gates already answer. An
1576 uncounted review is marked advisory by =mr show= and by the merge
1577 request page, both reading the same rule, so the page cannot show an
1578 approval the gate ignores. #147
1579- The two =git upload-pack= spawns behind the smart HTTP transport now
1580 resolve git at start-up like everything else. The v1.13.2 rewrite
1581 matched a plain identifier for the context and these pass
1582 =r.Context()=, so it skipped them. #153
1583- CI analyses each branch as itself. Every scan was recorded against the
1584 project's main branch whatever branch produced it, so a feature branch
1585 replaced main's results — a branch that removes findings made main look
1586 clean before the fix merged, and one that added them made main look
1587 broken when it was not. #154
1588
1589Replace the binary and reinstall the CLI. No migration.
1590
1591A repository relying on approvals from accounts without write access
1592will find those merges now refused. That was the defect: such an approval
1593never meant the repository accepted the change. Grant write, or name the
1594reviewer in CODEOWNERS and grant write, if their approval is meant to
1595count.
1596
1597* v1.13.2 — 2026-09-04
1598
1599The first SonarCloud scan's findings: eight fixed, the rest triaged and
1600dismissed with reasons.
1601
1602- A pages directory redirect could leave the site. Both redirects passed
1603 the raw request path to =http.Redirect= while the cleaned path sat a
1604 line above; =net/url= keeps a leading =//=, and Go emits
1605 =Location: //evil.example/= unchanged, which a browser reads as
1606 protocol-relative. Reaching it needed a public repository named like a
1607 host under the subdomain's own owner — repository names permit dots —
1608 so it was narrow rather than impossible. The destination is built from
1609 the cleaned path through =url.URL= now, which also settles the two
1610 spellings the first fix missed: a =..= that escapes to the root, and a
1611 backslash, which browsers following the WHATWG rules treat as a
1612 separator. #153
1613- The runner's default workspace was =<tmp>/gitbay-runner=: a fixed name
1614 in a world-writable directory, created with =MkdirAll=, which succeeds
1615 against a directory whoever already owns it. bay1 was never exposed —
1616 its unit names a workspace — but the default is what anyone running the
1617 binary by hand gets, and this is the process that clones repositories
1618 and exports build secrets. The default moves under the user's cache
1619 directory, the workspace is created 0700, and a symlink or a directory
1620 owned by someone else is refused. One we own that is merely too
1621 permissive is tightened rather than refused, since every runner before
1622 this one made it 0755 and refusing would take the runner down on
1623 upgrade. #153
1624- Logout and flash consumption expire their cookies with the attributes
1625 the setting calls used. Deletion worked either way; the difference was
1626 a reviewer's puzzle, and four findings. #153
1627- The topics-remove field has a label. A placeholder is not an accessible
1628 name. TestEveryInputHasAnAccessibleName is the guard that was missing,
1629 and it knows both associations — six inputs use
1630 =<label>Name <input></label>=, which is as good as for/id. #153
1631- git and ssh are resolved once at start-up rather than searched on every
1632 spawn, and gitbayd refuses to start when one is absent instead of
1633 failing on whichever request first needed it. This was 74 of the 118
1634 findings; a dashboard that is mostly permanent noise is one nobody
1635 reads. #153
1636
1637Also: SQLite migrations are excluded from analysis. They were read as
1638PL/SQL, where ='' is NULL=, so =WHERE col = ''= on a =NOT NULL DEFAULT ''=
1639column — correct SQLite, and the shape used throughout — read as a
1640null-comparison bug.
1641
1642Replace the binary and reinstall the CLI. No migration. A runner whose
1643workspace is group- or world-readable will have it tightened to 0700 on
1644next start, and will refuse to start if that workspace is a symlink or
1645belongs to another user.
1646
1647* v1.13.1 — 2026-09-04
1648
1649A command that reads its payload from stdin says so, and SonarCloud runs
1650alongside the vulnerability scan.
1651
1652- =repo secret set= blocked with nothing printed, which is
1653 indistinguishable from a hung connection, and pressing Enter did not
1654 end it because the server reads to EOF — so it looked the same before
1655 and after the value had been typed, and the secret echoed into the
1656 scrollback on the way. A terminal is now told what is wanted and that
1657 Ctrl-D ends it; a secret is read without echo and takes one line, so
1658 Enter is enough. Piped input is unchanged, byte for byte: =printf %s
1659 "$TOKEN" | gitbay repo secret set ...= still sends exactly the token.
1660 Applies to =keys add=, =auth pgp add=, =repo deploy-key add= and
1661 =release asset add= as well; public keys keep echoing, since they are
1662 public. #150
1663- A =sonar= CI job reports to SonarCloud, alongside =vuln=. Report-only:
1664 it does not gate a build, unlike the vulnerability scan. A merge
1665 request from a fork builds without secrets by design, so the job says
1666 why it is skipping there rather than failing on a missing credential.
1667 Only =SONAR_TOKEN= is secret and it is a build secret; the
1668 organization, project key and host are checked in. Ref #149
1669
1670Replace the binary and reinstall the CLI. No migration.
1671
1672* v1.13.0 — 2026-09-04
1673
1674Collaboration. A review is composed and submitted as one thing, a merge
1675request can say it is not asking yet and can show what changed since you
1676last looked, issues are searched by their text, and the events half the
1677mutations never recorded now exist.
1678
1679- A review is composed as a unit. =mr diff-comment --pending= holds a
1680 comment back; =mr review= publishes the batch with the verdict and says
1681 how many went with it; =mr review --discard= throws away what was never
1682 submitted. A pending comment notifies nobody when written — the review
1683 is the announcement, and it names its own size — and does not gate a
1684 merge, since a thread only its author can see is one nobody else could
1685 resolve. #111
1686- =mr create --draft=, =mr draft=, =mr ready=. A draft does not merge and
1687 does not appear in anyone's review queue; marking it ready is the
1688 request for review. Draft is a flag rather than a fifth state, so every
1689 =state = 'open'= rule still means what it did, and the merge refusal is
1690 unconditional: every other gate is a setting an admin turns on, and
1691 this one is the author's own statement about their own work. #111
1692- =mr range-diff= shows what changed between two revisions of a merge
1693 request, and =mr revisions= lists them. A push stales every review and
1694 nothing said what had moved; a diff of the two heads cannot answer it,
1695 and the previous head was overwritten in place. Each side of the
1696 comparison carries the merge base it had at the time, since measuring
1697 both against today's would attribute every commit that landed on the
1698 target in between to this merge request's author. #111
1699- Issues and merge requests are searched by their title and body, over
1700 FTS5. =issue list --search= and =mr list --search= narrow one
1701 repository; the instance-wide =search= reaches bodies now, and both
1702 list pages carry a search box. What someone types is quoted term by
1703 term, so an FTS5 operator — =c++=, =AND=, a lone quote — is a word to
1704 match rather than a syntax error. #114
1705- Ten mutations that changed a repository silently now record an event:
1706 =mr.closed=, =mr.reviewed=, =mr.edited=, =mr.retargeted=, =mr.draft=,
1707 =issue.edited=, =issue.labeled=, =issue.assigned=, =issue.milestoned=,
1708 =mr.milestoned=, =release.deleted=. =mr close= and =issue edit= also
1709 notify participants, which they did not. The full list is on the API
1710 wiki page and =webhook add --events= refuses a name that is not on it,
1711 since a subscription to a typo would never fire and nothing would say
1712 so. #112
1713- =gitbay-runner -jobs N= runs N builds at once. Claiming was always a
1714 single transaction that selects and updates, and each build already
1715 worked in its own directory, so several workers were safe the whole
1716 time; the runner never used more than one. #115
1717- A merge request replayed from a migration bundle has a diff. The bundle
1718 carried no head at all, and =mr diff= resolves through the head ref, so
1719 a merged merge request — which has no source branch left — could only
1720 fail. Re-running an import after the git push sets the head it could
1721 not set the first time. The GitHub import fetches =refs/pull/*/head=,
1722 which a mirror made with the default refspecs does not carry. #128
1723- The review loop is driven end to end by three accounts in the test
1724 suite: draft, ready, thread, approval, resolve, merge, with approvals,
1725 CODEOWNERS and require-resolved all on at once. Every one of those had
1726 its own test and none of them met. #139
1727- A bare =go test ./...= says the timeout is too short instead of
1728 panicking eleven minutes in and blaming whichever test was running.
1729 =make test= is what CONTRIBUTING asks for now. #143
1730
1731Migrations 0036 through 0039 add the search index, the draft flag,
1732pending review comments and merge request head history; 0036 and 0039
1733backfill from what is already there. They run on daemon start.
1734
1735Two things this does not do. There is still no way to ask a particular
1736person for a review — the queue is computed from involvement, so a
1737collaborator with write access who has not touched a thread hears nothing
1738(krz/gitbay#145). And a CI build still runs as the runner's own user with
1739no container; the runner on this instance is scoped to one repository,
1740which is what keeps that narrow (krz/gitbay#144). Both are v1.14.0.
1741
1742* v1.12.0 — 2026-09-04
1743
1744The store and the push path. Dashboard queries walk an index instead of
1745sorting the table, concurrent writers wait instead of failing, expired
1746rows are swept, and a large first push no longer forks a process per
1747commit.
1748
1749- Every dashboard list scanned its table and sorted the result to take
1750 fifty rows. Reachability is correlated subqueries and cannot be
1751 indexed; the index supplies the =ORDER BY= instead, so the walk stops
1752 at =LIMIT=. On 20k issues and 20k merge requests: open issues 11.8ms
1753 to 0.8ms, open merge requests 12.1ms to 0.8ms, the review queue 15.5ms
1754 to 0.3ms, assigned issues 10.6ms to 0.04ms. The last of those also
1755 drives from =issue_assignees= rather than testing =EXISTS= against
1756 every issue. #137
1757- Concurrent writers serialise rather than failing. Every transaction in
1758 the store writes, and a deferred one takes the write lock at its first
1759 write, by which point another may hold it; SQLite answers
1760 =SQLITE_BUSY= and does not run the busy handler for that case, so
1761 =busy_timeout= could not help. Measured with eight concurrent
1762 read-then-write transactions, 44% of them failed. Beginning immediate
1763 takes the lock up front, where the timeout applies. #121
1764- =repo settings= updates no longer overwrite each other.
1765 =settings_json= is one blob, and every caller read it off a repository
1766 loaded earlier, changed a field and wrote it all back; two admins at
1767 once and the later write put back what it had read for the other's
1768 field. The read and the write happen together now, under one
1769 immediate transaction. #123
1770- Expired sessions and tokens are swept, and =[retention]= caps how long
1771 the audit log, the activity feed, webhook deliveries and the mail
1772 queue keep a row. Unset means forever, which is what every existing
1773 instance gets. #122
1774- The audit entry records flag names without their values. Secrets never
1775 reached argv — they travel on stdin — but prose did: =--body <the
1776 whole issue>= was stored verbatim, in a table nothing pruned, for a
1777 repository that may be private. Identifiers are positional and
1778 survive. #122
1779- pre-receive on a require-signed repository forked a =cat-file= per
1780 incoming commit and built one JSON message holding the whole push. A
1781 50k-commit first push forked 50k processes and held the history in
1782 memory twice. One =cat-file --batch= serves the push now, and the
1783 daemon verifies each commit as it arrives. #100
1784- The payloads other surfaces decode are named types in =control=. httpd
1785 had its own copies of what the build, profile and dashboard commands
1786 emit, so a field added to a command was silently absent on the page.
1787 #126
1788
1789Migration 0035 adds three indexes; it runs on daemon start.
1790
1791Two changes in behaviour rather than configuration. A heavily contended
1792write now blocks for up to =busy_timeout= (five seconds) instead of
1793returning an error immediately — waiting is the point, but a caller that
1794treated the error as normal will see a pause instead. And anything
1795parsing =audit --json= for command arguments will find flag values gone;
1796the flag names and the positional arguments are still there.
1797
1798* v1.11.0 — 2026-09-04
1799
1800The web catches up with the rest of the forge: search across the
1801instance, a notification inbox, a compare view, linkable diff lines,
1802and a pass over contrast, heading structure and the stylesheet.
1803
1804- Notifications are no longer mail or nothing. An =inbox= table holds a
1805 row per recipient whether or not the instance has SMTP;
1806 =notifications list= reads it, unread by default, and =notifications
1807 read <id>... | --all= clears it. =repo watch= adds you to a
1808 repository's notifications and =repo unwatch= mutes it, with a mute
1809 beating every other reason to be told, including owning the
1810 repository or having written the thread. The unread count rides on
1811 =dashboard= and in the web rail. #113
1812- =search= matches repository paths, descriptions and topics, and issue
1813 and merge request titles, across everything the caller can read;
1814 =/search= renders it with a field in the rail on every page, and an
1815 anonymous visitor gets the public rows from the same query. Titles
1816 only — body search is #114. #118
1817- =/{owner}/{repo}/compare/{a}...{b}= shows what one ref adds on top of
1818 another. Diff rows, files and review threads carry ids, so a line can
1819 be linked to. The issue and merge request lists page at fifty with
1820 the cursors the commands already emit. #118
1821- CODEOWNERS gating is a setting rather than a file that happens to
1822 exist: =repo settings require-codeowners <owner/name> on|off=, off by
1823 default, still independent of =require-approvals=. A repository can
1824 carry the file as documentation of who to ask without it gating
1825 merges. #142
1826- A failed form action's reason rides a one-shot cookie instead of
1827 =?e=<message>=, so it no longer survives a reload or lands in
1828 history. #119
1829- A diff cut at 4 MiB cuts on a line boundary and says so, the
1830 diffstat says its counts are partial, and a merge request's commit
1831 list says "first 100 of N". #117
1832- Page templates parse once with the layout at start-up, so a template
1833 that does not parse fails the process rather than the first visit to
1834 its page. #116
1835- Markdown headings carry ids, matching org pages, and the stylesheet
1836 serves a hash ETag with a day's lifetime and answers a matching
1837 =If-None-Match= with 304. #132
1838- Dark-mode buttons carry a visible edge (a 1 px border was 1.3:1
1839 against the 3:1 non-text contrast floor), and a stored label colour
1840 is held between 0.12 and 0.28 relative luminance so it clears 3:1 on
1841 both grounds while keeping its hue. #120
1842- Accessibility: the pin star is decoration and the word carries the
1843 meaning, the refs and release asset tables have scoped column
1844 headers, state filters carry =aria-current= rather than marking the
1845 active one by colour alone, and a rendered README or wiki page's
1846 headings move down one level so they sit under the page's own. #133
1847- The stylesheet drops rules no template reaches, folds two off-scale
1848 values onto the type scale, and resolves the classes templates asked
1849 for and it never defined. #131
1850- On a phone the tab bar wraps to a second row instead of scrolling
1851 sideways with its scrollbar hidden, and the landing page says in
1852 three sections what a reader, a writer and a reviewer can do. #134
1853
1854Migration 0034 adds =inbox= and =repo_watchers=; it runs on daemon
1855start. Reinstall the CLI for =search=, =notifications= and =repo
1856watch/unwatch=.
1857
1858Two upgrade notes beyond replacing the binary. A repository that
1859relied on a CODEOWNERS file gating merges by its presence alone loses
1860that gate until =require-codeowners= is set: nothing back-fills it,
1861since the database cannot say which branches carry the file. And
1862=search= and =notifications= are now reserved top-level routes, so a
1863user or organization already holding either name keeps it but its
1864profile page is shadowed by the route.
1865
1866* v1.10.0 — 2026-09-04
1867
1868Every command parses its arguments the same way, the web answers by
1869exit code, and a restart no longer waits on idle connections.
1870
1871- One flag parser for every command: an unknown flag, a missing value or
1872 too many arguments is exit 2 with the command's usage, everywhere.
1873 =mr review --approve --bogus= used to report repository =--bogus= as
1874 not found. #96
1875- =--json= is honoured by the dispatcher's own refusals, so a script told
1876 no gets the envelope. #109
1877- A store failure is exit 1 and not-found is exit 3; both used to be
1878 usage errors. #107
1879- Web form actions answer by exit code: the 404 page for a thing that
1880 does not exist, the page with the message for anything else. #106
1881- Inside a clone, =gitbay mr create= takes the checked-out branch as
1882 =--source=; =gitbay <noun> --help= is the server's reference for the
1883 noun, flags included. #101 #130
1884- Shutdown closes idle SSH connections at once and drains only sessions
1885 mid-command; a store failure during key lookup no longer counts as a
1886 bad key against the auth limiter; the CLI says on ssh's exit 255 that
1887 a burst may have tripped it. #141
1888- A merge request head the target already contains is recorded as
1889 merged instead of refused; a fork is created with its parent in one
1890 insert; a failed transfer revert is reported; the repository quota is
1891 checked under a lock. #108
1892- Issues and merge requests share their comment, reference and
1893 author-or-write code. #110
1894- The payloads the web and clients decode are named types: =Created=,
1895 =MRCreated=, =IssueShow=, =MRShow=. JSON unchanged. #126
1896- Tests: parse failures per command, non-ASCII paths (which found
1897 =ls-tree= returning octal escapes, fixed with =core.quotepath=off= for
1898 every git the server runs), concurrent pushes. #129
1899
1900Replace the binary and restart, and reinstall the CLI. No migration.
1901
1902* v1.9.0 — 2026-09-03
1903
1904The runner is no longer an admin, the web no longer reaches around the
1905registry, and the CLI stops paying a handshake per command.
1906
1907- =keys add --scope runner= confines a key to =runner next/log/done= and
1908 read-only git; the runner commands accept that scope or an admin. The
1909 systemd drop-in sandboxes the runner process. gitbay.org's runner now
1910 polls as a non-admin =ci= account scoped to one repository. #92
1911- The web's repo create, issue create and edit, MR edit and both comment
1912 forms dispatch the command the CLI runs, so the repository quota, the
1913 archived-repository refusal, notifications, the body format and the
1914 audit entry hold from a browser. #93
1915- The CLI shares one SSH connection per instance (=ControlMaster=, five
1916 minutes idle): a command costs a round trip instead of a handshake,
1917 0.4 s instead of 4 s from a distant laptop. =no_multiplex = true= on
1918 an instance opts out. #94
1919- A disabled account is refused on every surface, and disabling revokes
1920 its API tokens along with its sessions. #95
1921- CODEOWNERS gates whenever the file exists on the target branch, not
1922 only under =require-approvals=. #99
1923- The HTTP listeners have header and idle timeouts, and SIGTERM drains
1924 in-flight requests and SSH sessions before exit. #104 #105
1925- =git archive= runs under a two-minute deadline and a 512 MiB cap. #124
1926- Every git invocation ends option parsing before the ref, so a ref
1927 shaped like an option is a bad revision and never a flag. #135
1928- The admin noun is gated in the dispatcher as well as in each handler;
1929 registry tests cover that and =ReadsStdin=. #127
1930- An e2e test runs every =ReadOnly= command against a populated instance
1931 and fails on any row it changes. #97
1932- =http.trusted_proxies= attributes proxied API requests to the last
1933 untrusted =X-Forwarded-For= hop for rate limiting; =email add= is
1934 capped at five codes an hour per account. #136
1935- A merge request head is built in the target repository, at
1936 =refs/merge-requests/<n>/head=, so a fork's merge request has
1937 =ci/<job>= statuses for =require-checks= to gate on. A head from
1938 another repository is built without the target's secrets. #98
1939- Triggers refuse deleting a user or organization that still owns
1940 repositories, whatever path the delete takes. #136
1941- The stylesheet's fonts are served again, and directory crumbs on blob
1942 and blame pages link to the tree. #102 #103
1943- The Threat-Model wiki page covers the runner. #138
1944
1945Replace the binary and restart, reinstall the CLI, and =make
1946deploy-runner=: the runner fetches merge request refs before checkout.
1947Migrations 0032 and 0033 run on start. The daemon host needs git 2.24
1948or newer for =--end-of-options=.
1949Operators running =gitbay-runner=: give it a non-admin account with a
1950key added by =keys add --scope runner=, remove the admin key it held,
1951and =make deploy-runner= to install the sandboxed unit drop-in; an
1952admin key keeps working meanwhile.
1953
1954* v1.8.1 — 2026-09-03
1955
1956Markdown and org files render when opened.
1957
1958- A =.md=, =.markdown= or =.org= file renders on its page the way a
1959 README does on the directory page, through the same renderer with
1960 relative links resolved against the file's directory. =source= in the
1961 action bar, or =?view=source=, shows the text as before. Every other
1962 file is unchanged. #88
1963- The e2e harness waits for the HTTP and git listeners as well as SSH
1964 before a test starts; a test whose first act was an HTTP request could
1965 be refused, which failed two otherwise green runs. #91
1966
1967Replace the binary and restart. No migration.
1968
1969* v1.8.0 — 2026-09-03
1970
1971The tracker's lists narrow, labels have colours you set, and the CLI's
1972help is the server's.
1973
1974- =issue list= takes =--label=, =--assignee=, =--author= and
1975 =--milestone= (a title, or =none= for issues with no milestone);
1976 =mr list= takes =--author= and =--milestone=. The store narrows in
1977 SQL, and the web lists take the same names as query parameters and
1978 show each active filter with a link that drops it and keeps the rest.
1979 Both lists had taken =--state= and nothing else, so the web's
1980 filtering could never match the CLI's. #84
1981- =label list= shows a repository's labels with their colour and how
1982 many issues carry each; =label set <label> [--color rrggbb|'']=
1983 creates a label or sets its colour; =label remove= takes it off every
1984 issue. The colour column had existed since labels did and nothing
1985 wrote it. The hash is optional because over bare ssh a bare =#= starts
1986 a comment for the tokenizer. =issue label --add= still creates a
1987 colourless label on the fly. #85
1988- =gitbay help= with a prefix or =--json= runs the server's help, the
1989 only place flags are written down and whose JSON is the contract;
1990 bare =gitbay help= is still the local tree. Cobra's built-in help had
1991 owned the word, so =gitbay help --json= failed on an unknown flag. #86
1992
1993Replace the binary and restart, and reinstall the CLI for the help
1994change. No migration.
1995
1996* v1.7.0 — 2026-09-02
1997
1998What an open instance needs before it is open: a cap on what one
1999account can take, a way out of a browser session you no longer hold,
2000and accounts that never verified do not stay forever.
2001
2002- =limits.max_repos_per_user= caps the repositories an account owns
2003 directly; =repo create=, =fork= and =import= refuse past it with the
2004 numbers. =limits.max_bytes_per_user= caps their disk: a push may be no
2005 larger than what the owner has left, riding the same
2006 =receive.maxInputSize= as the pack cap, and is refused outright when
2007 nothing is left. Organizations are not capped. Migration 0031 adds
2008 per-account overrides, set with =admin user limits <name> [--repos
2009 n|default] [--bytes n|default]= and shown by =admin user show=. Both
2010 default to 0, unlimited, so nothing changes until set. #82
2011- =registration.pending_expiry=, a duration, removes self-registered
2012 accounts still unverified after that long, hourly and once at start,
2013 audited as =pending.expired=. Empty keeps them, as before. #82
2014- =web sessions list= shows each unexpired browser session by a short id
2015 with its creation and expiry; =web sessions revoke <id>= ends one and
2016 =--all= ends every one. SSH-only, matching the token commands, and
2017 scoped to the caller. #83
2018- A step runs in its own process group and a cancel or timeout kills the
2019 group. On a host whose =/bin/sh= is dash, killing the shell alone left
2020 its child holding the log pipe, so a cancelled build held the runner
2021 until the child finished on its own, minutes for a test suite. The
2022 wait after a kill is capped at ten seconds besides.
2023- A commit with a build still queued or running is not queued again
2024 when a fast-forward lands it; the v1.6.0 skip counted only a finished
2025 success. #90
2026
2027- =golang.org/x/crypto= v0.56.0: GO-2026-6354 and GO-2026-6355 in its
2028 =ssh= package, both reached through =ssh.NewServerConn= in the
2029 embedded SSH server; one is a denial of service on a deadlocked
2030 undecided channel.
2031
2032Replace both binaries and restart: =make deploy= for the daemon
2033(migration 0031 adds two columns to =users= on start), then
2034=make deploy-runner= for the process-group kill.
2035
2036* v1.6.1 — 2026-09-02
2037
2038A cancel reaches a build in its clone.
2039
2040- The runner honoured a cancel only in its step loop; a build cancelled
2041 during its clone or checkout ran git to completion first, which on a
2042 loaded host was long enough for the v1.6.0 test to fail on the CI
2043 host while passing locally. One =runStep= now drives the clone, the
2044 checkout and each step with the cancel signal and the deadline, and
2045 checks the signal before starting at all. The runner logs how its log
2046 session ended when that was not a cancel.
2047
2048Replace the runner: =make deploy-runner=. The daemon is unchanged from
2049v1.6.0.
2050
2051* v1.6.0 — 2026-09-02
2052
2053The v1.4.0 admin surface answered questions about accounts. This one
2054answers questions about the machinery: which runner is alive, what is
2055stuck, whether last night's backup exists, and it lets an operator stop
2056a build instead of waiting it out.
2057
2058- A build a runner claimed and never reported is failed by the
2059 scheduler's minute tick, with no runner involved. It used to happen
2060 only when some runner polled again, so a dead sole runner left its
2061 builds running forever. =GITBAY_STALE_BUILD_DEADLINE= shortens the
2062 deadline for tests. #75
2063- Runners are visible. Migration 0030 adds =runner_seen=: one row per
2064 runner account with its last poll, the =-repos= scope it asked for,
2065 and the build it holds. =admin runners= lists them, over SSH and on
2066 the host. #76
2067- =GET /healthz=: whether the database answers and which commit serves,
2068 no auth, no repository data, 503 when the database does not answer.
2069 =healthz= joins the reserved names. #77
2070- The host monitor's hourly reading carries the age of the newest full
2071 backup and database snapshot, alerting at 25 and 2 hours, and the
2072 daemon's own =/healthz= answer read through =site_url=. Both ride the
2073 journald line and the webhook body. #78
2074- =admin stats= reports =lfs_bytes=. =admin gc --lfs= scans every
2075 repository's objects for LFS pointers and removes stored objects none
2076 names, keeping anything younger than a day since git lfs uploads
2077 before it pushes. #79
2078- =admin backup --verify <archive>= reads an archive back: SQLite's
2079 integrity check on the snapshot, and the repositories it names against
2080 the archive's. A database-only archive says so. Damage or a missing
2081 repository exits non-zero. #80
2082- A commit that already passed a job on another branch is not built
2083 again when a fast-forward lands it. Merging the six-layer v1.6.0 stack
2084 had queued eighteen jobs for commits that had each just gone green.
2085 Failed or abandoned builds still re-queue. #90
2086- =build cancel <owner/name> <n>= withdraws a queued build or ends a
2087 running one. For a running build the server closes the runner's log
2088 session, the runner kills the step within seconds, and its late report
2089 changes nothing. The commit status goes back to the passed result from
2090 another build of the same commit when one exists, else reads
2091 =cancelled=. Needs write access.
2092- Deploys copy with =rsync --partial=, so a transfer the host's load
2093 stalled resumes, and =make deploy-runner= installs a systemd drop-in
2094 (=Nice=10=, =CPUWeight=30=, =IOWeight=30=) so a build never starves the
2095 host's sshd again.
2096
2097Replace both binaries and restart: =make deploy= for the daemon, then
2098=make deploy-runner= for the runner, which carries its half of running-
2099build cancellation and installs the drop-in. Migration 0030 adds the
2100=runner_seen= table on start. The monitor change ships in
2101=deploy/cloud-init.yaml=; an existing host takes it by hand.
2102
2103* v1.5.0 — 2026-09-02
2104
2105Merge requests stack.
2106
2107- A merge request whose target is the source branch of another open
2108 merge request in the same repository is stacked on it. Nothing is
2109 stored and no flag exists; the forge reads the stack from the
2110 branches. =mr create= says =stacked on !A= when it applies, =mr show=
2111 carries =stacked_on= and =stacked=, =mr list= rows carry =stacked_on=,
2112 and the page says both directions in the header. #87
2113- When the lower merge request merges, everything stacked on it is
2114 retargeted onto what it merged into, with a system comment naming the
2115 merge and its reviews kept: after a fast-forward or merge commit the
2116 diff against the new target is the diff they were of. A squash or
2117 rebase merge under a stack is refused, naming the stack, since it
2118 would rewrite the commits the stack builds on.
2119- The first stack merged on gitbay.org was the six merge requests of
2120 v1.6.0, bottom-up, with no =mr retarget= typed. The wiki's
2121 Stacked-MRs page walks through it.
2122
2123Replace the binary and restart. No migration.
2124
2125* v1.4.0 — 2026-09-01
2126
2127Until now the instance had one operator surface: root on the host. Every
2128question about the instance itself — who is on it, what is stuck, what a
2129spam repository is doing — needed a shell on port 2222. This release
2130gives an instance admin the same answers over SSH, and one page on the
2131web.
2132
2133- =admin user list= pages accounts by username with
2134 =--state active|pending|disabled|admin=, each row carrying its state
2135 and =last_seen=, the newest use of any of its SSH keys or API tokens.
2136 =admin user show <name>= adds the keys with their last use, each
2137 address with how it was verified, PGP keys, org roles, owned
2138 repository count, API token names and live browser sessions. Both are
2139 SSH-only and refused to non-admins, like =audit=. #69
2140- =admin user promote|demote=. The only way to admin was
2141 =admin user create --admin=; an existing account could not be raised
2142 and an admin could not step down. Demoting the last admin is refused
2143 inside the transaction that counts them. The host-local twin is the
2144 recovery path when no admin key is reachable. #70
2145- Repository overrides for moderation: =admin repo list= with size and
2146 last push, and =admin repo archive|unarchive|visibility|delete=. Policy
2147 still knows nothing about instance admin — a private repository
2148 answers not-found to an admin as before — so each override skips the
2149 access check explicitly and writes its own =admin repo.<action>= audit
2150 row. #71
2151- =gitbayd admin= dispatches into the registry. User create, disable,
2152 enable and delete, email verify, invite and stats were reimplemented on
2153 the host; they now live in the registry, SSH-only and admin-gated, and
2154 the host binary runs them as the host — an admin context with no
2155 account behind it, so its audit rows say =source: host= where a
2156 session says the key fingerprint. Invite and stats gain an SSH twin by
2157 the same move. =backup=, =gc= and the backfills stay host-local. #72
2158- =audit= filters: =--actor <user>= or =--actor -= for actorless rows,
2159 =--action <prefix>=, and =--since= as a duration (=30m=, =24h=, =7d=)
2160 or a date. =gitbayd admin audit= takes the same flags and =--json=. #73
2161- =dashboard= carries a =queues= block for admins: per worker —
2162 webhooks, mail, mirrors, builds, dependency checks — the pending,
2163 retrying and dead-lettered counts, the oldest pending age, and the
2164 retrying or failed rows themselves, capped at twenty each. The mail
2165 queue was readable nowhere before. =/admin= renders the block by
2166 dispatching =dashboard=; non-admins get a 404 and no rail link. #74
2167- =gitbayd admin config show= prints the configuration in effect as
2168 TOML, defaults filled in and =smtp_pass= redacted, so a support
2169 question starts from what runs rather than what was written. #81
2170- Build badges are served as PNG at =badge/build.png= as well as SVG,
2171 for places that will not render SVG.
2172- Host monitoring writes its reading to journald on every run and exits
2173 non-zero on an alert, so an unset webhook no longer looks like a
2174 healthy host; it reads the ACME cache where it actually lives and
2175 reports the soonest expiry. govulncheck runs as its own CI job. The
2176 database is snapshotted hourly by =gitbay-db-backup.timer=, keeping 48,
2177 alongside the nightly full archive; archives inherit the database's
2178 mode rather than the umask default. #28
2179- A runner whose log stream drops no longer fails the build it was
2180 recording. #67
2181- =go.yaml.in/yaml/v3= and =golang.org/x/net= bumped. #60
2182
2183Replace the binary and restart. No migration. The =gitbay-db-backup=
2184timer and the monitor changes ship in =deploy/cloud-init.yaml= for new
2185hosts; an existing host takes them from there by hand.
2186
2187* v1.3.0 — 2026-08-31
2188
2189A runner took every repository's work, which decided where you could run
2190one.
2191
2192- =runner next= takes optional =owner/name= arguments and =gitbay-runner=
2193 takes =-repos=, so a runner claims builds only for the repositories it
2194 names. Naming none is the old behaviour, so an existing runner is
2195 unaffected. This is what makes a runner outside the server practical: one
2196 on a machine that should build a single project no longer picks up a
2197 build belonging to someone else, which with open registration need not be
2198 anyone the operator knows. The scoping is what the runner asks for rather
2199 than an ACL the server holds over it — a runner account is admin by
2200 necessity, so the boundary is the operator choosing how to start it. #66
2201
2202Replace the binary and restart. Runners want the new binary too, though an
2203old one keeps working unscoped.
2204
2205* v1.2.1 — 2026-08-31
2206
2207Merging landed commits without running anything.
2208
2209- A merge moves the target ref with a direct ref update, so it never
2210 reached post-receive and none of the ref-update work fired: no =push=
2211 event for webhooks to subscribe to, and no builds. Pushing a commit to a
2212 branch ran the whole =.gitbay/ci.yml=; merging the identical commit ran
2213 nothing. Both now happen in the merge path, with the build queueing
2214 shared between it and post-receive rather than living in one of them.
2215 #65
2216
2217Replace the binary and restart.
2218
2219* v1.2.0 — 2026-08-31
2220
2221A merge request said what its state was and almost nothing about when it
2222got there. It now keeps time.
2223
2224- Reviews and checks carry the moment they last said something, on the
2225 merge request page and in =mr show=. A =ci/<job>= check also reports how
2226 long its build ran, so the timing of a run is readable without opening
2227 it. Checks posted through =status set= have no build and report only the
2228 time. !137
2229- A merged or closed merge request names who resolved it and when. The
2230 header stated "X wants to merge" whatever the state; it now says "X
2231 merged A into main on <date>", or "closed this without merging", and
2232 drops the claim entirely for a row that carries no stamp rather than
2233 inventing a time.
2234- =mr show= gains =merged_at=/=merged_by= and =closed_at=/=closed_by=, a
2235 =created_at= per review, and =updated_at= plus =duration= per check, in
2236 both JSON and text. Additive: nothing existing changed shape.
2237- The iOS client renders all of it as of krz/gitbay-ios!37.
2238
2239Replace the binary and restart. Migration 0029 adds four columns to
2240=merge_requests= and backfills the merge stamp for merge requests already
2241merged, reading the =mr.merged= events. A merge with no such event to read
2242— an import, or a row older than its events — keeps no stamp, and every
2243surface says nothing about when it happened rather than guessing.
2244
2245* v1.1.0 — 2026-08-31
2246
2247Every release until now answered questions. This one notices something
2248on its own: that a repository's dependencies have moved, and says so
2249without being asked.
2250
2251- Dependency update checks, opt-in per repository. A daemon worker reads
2252 the manifests on the default branch, asks the ecosystem's registry what
2253 the current release is, and maintains one issue per repository — opened
2254 when something falls behind, rewritten when the set changes, closed once
2255 nothing is behind. No package manager runs, so it needs no CI runner and
2256 no configuration beyond turning it on. #58
2257 - =go.mod= against proxy.golang.org, =package.json= with
2258 =package-lock.json= against npm, =Cargo.toml= with =Cargo.lock=
2259 against crates.io, =requirements.txt= and =pyproject.toml= against
2260 PyPI. A lockfile wins where both exist. A requirement naming a set
2261 rather than a release — a range, a wildcard, a git or path source — is
2262 skipped, since a range that already admits the newest release is not
2263 news.
2264 - =repo deps enable|disable|status=, a toggle on the repository settings
2265 page, and the same three over the JSON API.
2266 - Off by default, because checking a private repository tells a public
2267 registry what it depends on. That is the owner's disclosure to make.
2268 =[deps] check_interval_hours= sets the cadence, default 24.
2269 - The issue is authored by a =gitbay-bot= account, so the existing
2270 notification mail reaches the repository's owner rather than excluding
2271 them as the actor. Its table is padded to its columns, which a
2272 renderer ignores and a mail client needs. #61
2273- =help= takes a prefix — =help mr= narrows the registry to one noun — and
2274 every command now documents its arguments, so the server answers "what
2275 are the flags" instead of being guessed at. #57
2276- Web: settings rows end in one column of controls, checkboxes drawn at
2277 the height of the inputs and buttons they sit beside #59; an added line
2278 keeps its leading dash in the diff; a contributor's several verified
2279 addresses collapse to one row #56.
2280
2281Replace the binary and restart. Migration 0028 adds two tables and, when
2282the name is free, the =gitbay-bot= account. An instance already using that
2283name for a user or an org keeps what it has: the account is not created,
2284and dependency checks report that as the reason they cannot open an issue
2285rather than the migration failing and the daemon not starting. #64
2286
2287* v1.0.1 — 2026-08-30
2288
2289Two CI fixes found by running orgo's release pipeline on this instance.
2290
2291- A runner killed between claiming a build and reporting it left the build
2292 =running= forever, and the commit's =ci/<job>= status pending with it.
2293 =runner next= now fails builds past a 90-minute deadline — longer than the
2294 runner's own =-timeout= — and resolves their commit status. #53
2295- =gitbay keys add= and =gitbay repo deploy-key add= take stdin as a bare
2296 =< key.pub=, but only forwarded it when =--file -= appeared in the
2297 arguments, so both sent an empty body and rejected input the SSH API
2298 accepts. #55
2299
2300Replace the binary and restart.
2301
2302* v1.0.0 — 2026-08-26
2303
2304The web finishes the job #35 set it: reading, reviewing and responding,
2305with the CLI still the complete interface. Every capability exists over
2306SSH, every web write dispatches the same control command, and anything
2307whose input is a credential stays on the command line. The [[https://gitbay.org/krz/gitbay/wiki/Parity][Parity]] page in
2308the wiki is the maintained matrix and says which rows are deliberately
2309CLI-only.
2310
2311- Diff view: one foldable section per file with line-number gutters,
2312 per-file stats, rename and binary handling, and syntax highlighting
2313 run per hunk per side so multi-line constructs lex as real code.
2314 Commit and merge request pages share it; review threads anchor
2315 inline.
2316- Repository facts on the code page: commit, branch and tag counts,
2317 detected license, latest release, build status, a language census by
2318 tracked bytes, and contributors resolved to accounts by verified
2319 email. All derived from git at render time.
2320- Account settings on the web: SSH keys with scope, OpenPGP keys, and
2321 email addresses. Public keys are the only credential-shaped input the
2322 web accepts — they are not secret, and a new user needs one
2323 registered before the CLI is reachable to them. Token minting and
2324 account export stay SSH-only.
2325- Organizations are run from their page: membership and roles, teams,
2326 team members, and team repository grants, for org admins.
2327- Commit log shows each commit's combined check status and gains a path
2328 filter, so per-file history is reachable without editing the URL.
2329- Issue references from commit messages read "referenced in commit
2330 <sha> by <author>", linking the author when their email is verified
2331 here.
2332- The rail's focus ring uses the shell's own mark: the light scheme's
2333 accent was a dark blue ring on a black rail.
2334
2335No migrations. No new config.
2336
2337Upgrading from v0.5.0 is replace-the-binary-and-restart.
2338
2339* v0.5.0 — 2026-08-26
2340
2341A design pass and a parity pass. The web stops being a read-only
2342mirror of the CLI without becoming the place you are expected to work.
2343
2344- New design: a black shell with a persistent left rail carrying
2345 cross-repo state (pinned repos, review queue), the repo header
2346 rendered identically on every tab so navigation never moves, sharp
2347 lines, self-hosted IBM Plex, and code blocks that read against both
2348 color schemes. Tree listings sort directories first and carry each
2349 file's last commit; diffs, inputs and controls were reworked to
2350 match.
2351- Web parity with the CLI, dispatched through the same command
2352 registry the CLI and JSON API use — every web write is the
2353 equivalent =gitbay= command with =--source web=:
2354 - merge requests: review, resolve threads, merge, close, and open a
2355 new MR from the browser
2356 - issues: state, labels, assignees, milestones
2357 - repositories: settings, branch protection, visibility
2358 - releases: create and edit; builds: trigger a job
2359 Commands marked SSH-only still refuse over the web: build secrets,
2360 mirror tokens, domain claims, token minting, deletion and transfer.
2361- A dashboard that answers "what needs me": review queue, assigned
2362 issues, pinned repos, and an activity feed. Author names resolve to
2363 accounts and link to profiles wherever commits appear.
2364- Build status badges at =/{owner}/{repo}/badge/build.svg= for public
2365 repos.
2366- =[web] title= sets the instance's display name, separate from the
2367 hostname commands are pasted with.
2368- =make build/test/deploy= targets.
2369- Fixes: the mobile tab strip scrolls sideways only, long commit
2370 subjects no longer overflow on narrow screens, the shell fills the
2371 viewport with the line-length cap moved onto prose, and the account
2372 cell lines up with the page footer.
2373
2374No migrations. New config: =[web] title=.
2375
2376* v0.4.0 — 2026-08-25
2377
2378- Git LFS: standard clients work over both transports.
2379 =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
2380 included; download needs read, upload write), minting stateless
2381 repo- and operation-scoped tokens for the batch API and basic
2382 transfers. Anonymous HTTPS downloads for public repos; uploads
2383 verified against size and sha256 before landing. Storage is
2384 content-addressed under =[lfs] root= behind a small interface an
2385 S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
2386 objects (512MB default).
2387- Build failures mail the repo's notify targets with the log tail and
2388 build link — failed scheduled jobs reach an inbox.
2389- =release edit= updates a release's title and notes (absent flags
2390 keep their field); omaha-style CI note rebuilds work again.
2391- Syntax highlighting follows the color scheme: class-based chroma
2392 with light and dark palettes, the light-pinned code background is
2393 gone, and markdown fences and org src blocks highlight too. The UGC
2394 sanitizer admits only chroma's token-code classes.
2395
2396No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
2397
2398* v0.3.0 — 2026-08-25
2399
2400- CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=
2401 over SSH (admin-only runner protocol; statuses feed =require-checks=).
2402 Per-repo secrets set over stdin and injected into build environments;
2403 cron schedules (server-local time) and tag-glob triggers, mutually
2404 exclusive per job; =build list/show/log/trigger= and a builds tab.
2405- Pages: public repos' =pages= branches served on =<owner>.<domain>=
2406 (=[pages] domain=), custom domains with DNS TXT ownership challenges
2407 and 7-day expiry for pending claims, per-subdomain on-demand ACME.
2408- Wikis (=.wiki= companion repos, access mirrors the parent) and teams
2409 within orgs (members-role scoping, per-repo team grants).
2410- Activity graphs on user and org pages, backfillable
2411 (=admin backfill-activity=); commits attributed by verified author
2412 email, deduped by sha.
2413- MR pages list the commits the MR carries; =mr show= gains a commits
2414 section.
2415- Per-file history: =?path== on the web log, =--path= on =repo log=,
2416 history link on blob pages.
2417- Mirror status surfaced in =repo show= and the repo header
2418 (admin-only), with sync errors visible; tag-only pushes now schedule
2419 mirror syncs.
2420- Rendering: GFM tables/strikethrough/autolinks/task lists, blob image
2421 previews, raw serves images with real content types (README images
2422 render under nosniff), 0BSD license recognition, repo website links,
2423 compact dashboard pins.
2424- =admin user delete= for accounts that anchor nothing, with named
2425 blockers otherwise.
2426- Fixes: wiki pages no longer overflow on mobile (iOS font-inflation
2427 trigger), GHSA-free deps, secret values pipe correctly through the
2428 CLI.
2429
2430Migrations 0020-0025 apply on start. New config: =[pages] domain=.
2431The runner is a new binary (=gitbay-runner=); see the wiki's Admin
2432guide for setup. Stress-tested against an import of git.git (82k
2433commits): see the wiki's Performance page.
2434
2435* v0.2.0 — 2026-08-24
2436
2437- Deploy keys: repo-bound CI keys (=repo deploy-key=), ro/rw, rename- and
2438 transfer-proof.
2439- Commit statuses (=status set/list=), combined state on MR pages, and a
2440 =require-checks= merge gate.
2441- Email notifications for issue and MR activity (participants with
2442 verified addresses; never the actor).
2443- Inline review threads on MR diffs (=mr diff-comment/threads/resolve=),
2444 stale on force-push, =require-resolved= merge gate.
2445- Required approvals with CODEOWNERS (=require-approvals=; latest review
2446 wins, author excluded) and a =require-resolved= gate; merge gate order
2447 is checks → approvals → CODEOWNERS → resolved threads → signatures.
2448- Web design revamp: token-based stylesheet (light+dark), wordmark and
2449 favicon, aligned layout grid, card-based listings, designed 404,
2450 mobile pass.
2451- Cross-references and mentions: =#N=, =!N=, =owner/name#N=, =@user=
2452 autolink in issue/MR text, viewer-aware for private repos.
2453- Archived repositories (read-only with badge) and repo topics.
2454- Blame view with signature-aware attribution and 1000-line pages.
2455- Repository search (name/description/topic) and per-repo code search
2456 (=repo grep=, web search tab); blob line anchors.
2457- Homepage: dashboard for logged-in users (pinned repos via =repo pin=,
2458 open MRs and issues involving you), landing page for visitors, full
2459 public listing at =/explore=; MR diffs collapsed by default.
2460- Milestones (=milestone create/list/close=, =issue/mr milestone=) with
2461 web progress; issue templates from =.gitbay/issue-template*.md=
2462 (CLI =$EDITOR= prefill and web form).
2463- Issue actions from commit messages landing on the default branch:
2464 =closes/fixes/resolves #N= closes, bare =#N= leaves a reference
2465 comment; once per issue+commit.
2466- Vanity Go imports: =[go_import]= config serves go-import meta tags, so
2467 =go install gitbay.org/gitbay/cmd/...@latest= works.
2468- Release script: =deploy/release.sh <tag>= builds reproducible
2469 linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
2470- Repository maintenance: =admin gc= (repack/prune, per-repo sizes),
2471 =admin stats= (counts + disk usage), weekly =gitbay-gc.timer=.
2472- Releases: tag-anchored notes and binary assets (=release= commands,
2473 assets over SSH stdin/stdout, web releases tab with downloads).
2474- GitHub history import: =repo import-issues= brings issues and PRs
2475 (as merged/closed MRs) with comments, labels, and state, attributed
2476 inline and resumable.
2477- Push and pull mirroring (=repo mirror=): background sync, read-only
2478 pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
2479- Web signup at =/register= for open and invite instances.
2480- Audit log (=audit=, =gitbayd admin audit=): every mutating command
2481 with source key fingerprint, registrations, force-pushes, auth
2482 failures. Hardening: per-IP auth-failure throttling
2483 (=ssh_auth_rate=), =max_pack_bytes= enforced, =admin user
2484 disable/enable=.
2485- Account migration: =gitbay migrate --from <host>= (bundle
2486 export/replay + client-side git mirror); =gitbay auth export= as a
2487 user-level backup.
2488- Editable issues and MRs (=issue edit=, =mr edit=, web forms).
2489- Commit references appear as system messages with linked shas.
2490- Design: top nav, repo listing rows (topics, license, last updated),
2491 file table headers, README relative-link resolution, branch
2492 dropdown, web pinning, org owner picker, label filters, linked
2493 usernames and commit parents, =/privacy= page, blue accent.
2494
2495Upgrade notes: migrations 0006–0019 apply on start. No config changes
2496required; =[go_import]=, =[mirrors]=, =web.privacy_notice=, and
2497=web.mode = "accounts"= are opt-in.
2498
2499* v0.1.0 — 2026-08-24
2500
2501First tagged release: the complete CLI-first forge. SSH control plane
2502(bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues,
2503merge requests (ff/merge/squash/rebase with signature policy), OpenPGP
2504and SSHSIG verification with retroactive re-verification, orgs, repo
2505import, web UI (view-only or accounts mode), registration with invites
2506and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups,
2507ACME TLS, systemd deployment.