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