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