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