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