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