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