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