CHANGELOG.org
545 lines · 28877 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.8.0 — 2026-09-03
8
9The tracker's lists narrow, labels have colours you set, and the CLI's
10help is the server's.
11
12- =issue list= takes =--label=, =--assignee=, =--author= and
13 =--milestone= (a title, or =none= for issues with no milestone);
14 =mr list= takes =--author= and =--milestone=. The store narrows in
15 SQL, and the web lists take the same names as query parameters and
16 show each active filter with a link that drops it and keeps the rest.
17 Both lists had taken =--state= and nothing else, so the web's
18 filtering could never match the CLI's. #84
19- =label list= shows a repository's labels with their colour and how
20 many issues carry each; =label set <label> [--color rrggbb|'']=
21 creates a label or sets its colour; =label remove= takes it off every
22 issue. The colour column had existed since labels did and nothing
23 wrote it. The hash is optional because over bare ssh a bare =#= starts
24 a comment for the tokenizer. =issue label --add= still creates a
25 colourless label on the fly. #85
26- =gitbay help= with a prefix or =--json= runs the server's help, the
27 only place flags are written down and whose JSON is the contract;
28 bare =gitbay help= is still the local tree. Cobra's built-in help had
29 owned the word, so =gitbay help --json= failed on an unknown flag. #86
30
31Replace the binary and restart, and reinstall the CLI for the help
32change. No migration.
33
34* v1.7.0 — 2026-09-02
35
36What an open instance needs before it is open: a cap on what one
37account can take, a way out of a browser session you no longer hold,
38and accounts that never verified do not stay forever.
39
40- =limits.max_repos_per_user= caps the repositories an account owns
41 directly; =repo create=, =fork= and =import= refuse past it with the
42 numbers. =limits.max_bytes_per_user= caps their disk: a push may be no
43 larger than what the owner has left, riding the same
44 =receive.maxInputSize= as the pack cap, and is refused outright when
45 nothing is left. Organizations are not capped. Migration 0031 adds
46 per-account overrides, set with =admin user limits <name> [--repos
47 n|default] [--bytes n|default]= and shown by =admin user show=. Both
48 default to 0, unlimited, so nothing changes until set. #82
49- =registration.pending_expiry=, a duration, removes self-registered
50 accounts still unverified after that long, hourly and once at start,
51 audited as =pending.expired=. Empty keeps them, as before. #82
52- =web sessions list= shows each unexpired browser session by a short id
53 with its creation and expiry; =web sessions revoke <id>= ends one and
54 =--all= ends every one. SSH-only, matching the token commands, and
55 scoped to the caller. #83
56- A step runs in its own process group and a cancel or timeout kills the
57 group. On a host whose =/bin/sh= is dash, killing the shell alone left
58 its child holding the log pipe, so a cancelled build held the runner
59 until the child finished on its own, minutes for a test suite. The
60 wait after a kill is capped at ten seconds besides.
61- A commit with a build still queued or running is not queued again
62 when a fast-forward lands it; the v1.6.0 skip counted only a finished
63 success. #90
64
65- =golang.org/x/crypto= v0.56.0: GO-2026-6354 and GO-2026-6355 in its
66 =ssh= package, both reached through =ssh.NewServerConn= in the
67 embedded SSH server; one is a denial of service on a deadlocked
68 undecided channel.
69
70Replace both binaries and restart: =make deploy= for the daemon
71(migration 0031 adds two columns to =users= on start), then
72=make deploy-runner= for the process-group kill.
73
74* v1.6.1 — 2026-09-02
75
76A cancel reaches a build in its clone.
77
78- The runner honoured a cancel only in its step loop; a build cancelled
79 during its clone or checkout ran git to completion first, which on a
80 loaded host was long enough for the v1.6.0 test to fail on the CI
81 host while passing locally. One =runStep= now drives the clone, the
82 checkout and each step with the cancel signal and the deadline, and
83 checks the signal before starting at all. The runner logs how its log
84 session ended when that was not a cancel.
85
86Replace the runner: =make deploy-runner=. The daemon is unchanged from
87v1.6.0.
88
89* v1.6.0 — 2026-09-02
90
91The v1.4.0 admin surface answered questions about accounts. This one
92answers questions about the machinery: which runner is alive, what is
93stuck, whether last night's backup exists, and it lets an operator stop
94a build instead of waiting it out.
95
96- A build a runner claimed and never reported is failed by the
97 scheduler's minute tick, with no runner involved. It used to happen
98 only when some runner polled again, so a dead sole runner left its
99 builds running forever. =GITBAY_STALE_BUILD_DEADLINE= shortens the
100 deadline for tests. #75
101- Runners are visible. Migration 0030 adds =runner_seen=: one row per
102 runner account with its last poll, the =-repos= scope it asked for,
103 and the build it holds. =admin runners= lists them, over SSH and on
104 the host. #76
105- =GET /healthz=: whether the database answers and which commit serves,
106 no auth, no repository data, 503 when the database does not answer.
107 =healthz= joins the reserved names. #77
108- The host monitor's hourly reading carries the age of the newest full
109 backup and database snapshot, alerting at 25 and 2 hours, and the
110 daemon's own =/healthz= answer read through =site_url=. Both ride the
111 journald line and the webhook body. #78
112- =admin stats= reports =lfs_bytes=. =admin gc --lfs= scans every
113 repository's objects for LFS pointers and removes stored objects none
114 names, keeping anything younger than a day since git lfs uploads
115 before it pushes. #79
116- =admin backup --verify <archive>= reads an archive back: SQLite's
117 integrity check on the snapshot, and the repositories it names against
118 the archive's. A database-only archive says so. Damage or a missing
119 repository exits non-zero. #80
120- A commit that already passed a job on another branch is not built
121 again when a fast-forward lands it. Merging the six-layer v1.6.0 stack
122 had queued eighteen jobs for commits that had each just gone green.
123 Failed or abandoned builds still re-queue. #90
124- =build cancel <owner/name> <n>= withdraws a queued build or ends a
125 running one. For a running build the server closes the runner's log
126 session, the runner kills the step within seconds, and its late report
127 changes nothing. The commit status goes back to the passed result from
128 another build of the same commit when one exists, else reads
129 =cancelled=. Needs write access.
130- Deploys copy with =rsync --partial=, so a transfer the host's load
131 stalled resumes, and =make deploy-runner= installs a systemd drop-in
132 (=Nice=10=, =CPUWeight=30=, =IOWeight=30=) so a build never starves the
133 host's sshd again.
134
135Replace both binaries and restart: =make deploy= for the daemon, then
136=make deploy-runner= for the runner, which carries its half of running-
137build cancellation and installs the drop-in. Migration 0030 adds the
138=runner_seen= table on start. The monitor change ships in
139=deploy/cloud-init.yaml=; an existing host takes it by hand.
140
141* v1.5.0 — 2026-09-02
142
143Merge requests stack.
144
145- A merge request whose target is the source branch of another open
146 merge request in the same repository is stacked on it. Nothing is
147 stored and no flag exists; the forge reads the stack from the
148 branches. =mr create= says =stacked on !A= when it applies, =mr show=
149 carries =stacked_on= and =stacked=, =mr list= rows carry =stacked_on=,
150 and the page says both directions in the header. #87
151- When the lower merge request merges, everything stacked on it is
152 retargeted onto what it merged into, with a system comment naming the
153 merge and its reviews kept: after a fast-forward or merge commit the
154 diff against the new target is the diff they were of. A squash or
155 rebase merge under a stack is refused, naming the stack, since it
156 would rewrite the commits the stack builds on.
157- The first stack merged on gitbay.org was the six merge requests of
158 v1.6.0, bottom-up, with no =mr retarget= typed. The wiki's
159 Stacked-MRs page walks through it.
160
161Replace the binary and restart. No migration.
162
163* v1.4.0 — 2026-09-01
164
165Until now the instance had one operator surface: root on the host. Every
166question about the instance itself — who is on it, what is stuck, what a
167spam repository is doing — needed a shell on port 2222. This release
168gives an instance admin the same answers over SSH, and one page on the
169web.
170
171- =admin user list= pages accounts by username with
172 =--state active|pending|disabled|admin=, each row carrying its state
173 and =last_seen=, the newest use of any of its SSH keys or API tokens.
174 =admin user show <name>= adds the keys with their last use, each
175 address with how it was verified, PGP keys, org roles, owned
176 repository count, API token names and live browser sessions. Both are
177 SSH-only and refused to non-admins, like =audit=. #69
178- =admin user promote|demote=. The only way to admin was
179 =admin user create --admin=; an existing account could not be raised
180 and an admin could not step down. Demoting the last admin is refused
181 inside the transaction that counts them. The host-local twin is the
182 recovery path when no admin key is reachable. #70
183- Repository overrides for moderation: =admin repo list= with size and
184 last push, and =admin repo archive|unarchive|visibility|delete=. Policy
185 still knows nothing about instance admin — a private repository
186 answers not-found to an admin as before — so each override skips the
187 access check explicitly and writes its own =admin repo.<action>= audit
188 row. #71
189- =gitbayd admin= dispatches into the registry. User create, disable,
190 enable and delete, email verify, invite and stats were reimplemented on
191 the host; they now live in the registry, SSH-only and admin-gated, and
192 the host binary runs them as the host — an admin context with no
193 account behind it, so its audit rows say =source: host= where a
194 session says the key fingerprint. Invite and stats gain an SSH twin by
195 the same move. =backup=, =gc= and the backfills stay host-local. #72
196- =audit= filters: =--actor <user>= or =--actor -= for actorless rows,
197 =--action <prefix>=, and =--since= as a duration (=30m=, =24h=, =7d=)
198 or a date. =gitbayd admin audit= takes the same flags and =--json=. #73
199- =dashboard= carries a =queues= block for admins: per worker —
200 webhooks, mail, mirrors, builds, dependency checks — the pending,
201 retrying and dead-lettered counts, the oldest pending age, and the
202 retrying or failed rows themselves, capped at twenty each. The mail
203 queue was readable nowhere before. =/admin= renders the block by
204 dispatching =dashboard=; non-admins get a 404 and no rail link. #74
205- =gitbayd admin config show= prints the configuration in effect as
206 TOML, defaults filled in and =smtp_pass= redacted, so a support
207 question starts from what runs rather than what was written. #81
208- Build badges are served as PNG at =badge/build.png= as well as SVG,
209 for places that will not render SVG.
210- Host monitoring writes its reading to journald on every run and exits
211 non-zero on an alert, so an unset webhook no longer looks like a
212 healthy host; it reads the ACME cache where it actually lives and
213 reports the soonest expiry. govulncheck runs as its own CI job. The
214 database is snapshotted hourly by =gitbay-db-backup.timer=, keeping 48,
215 alongside the nightly full archive; archives inherit the database's
216 mode rather than the umask default. #28
217- A runner whose log stream drops no longer fails the build it was
218 recording. #67
219- =go.yaml.in/yaml/v3= and =golang.org/x/net= bumped. #60
220
221Replace the binary and restart. No migration. The =gitbay-db-backup=
222timer and the monitor changes ship in =deploy/cloud-init.yaml= for new
223hosts; an existing host takes them from there by hand.
224
225* v1.3.0 — 2026-08-31
226
227A runner took every repository's work, which decided where you could run
228one.
229
230- =runner next= takes optional =owner/name= arguments and =gitbay-runner=
231 takes =-repos=, so a runner claims builds only for the repositories it
232 names. Naming none is the old behaviour, so an existing runner is
233 unaffected. This is what makes a runner outside the server practical: one
234 on a machine that should build a single project no longer picks up a
235 build belonging to someone else, which with open registration need not be
236 anyone the operator knows. The scoping is what the runner asks for rather
237 than an ACL the server holds over it — a runner account is admin by
238 necessity, so the boundary is the operator choosing how to start it. #66
239
240Replace the binary and restart. Runners want the new binary too, though an
241old one keeps working unscoped.
242
243* v1.2.1 — 2026-08-31
244
245Merging landed commits without running anything.
246
247- A merge moves the target ref with a direct ref update, so it never
248 reached post-receive and none of the ref-update work fired: no =push=
249 event for webhooks to subscribe to, and no builds. Pushing a commit to a
250 branch ran the whole =.gitbay/ci.yml=; merging the identical commit ran
251 nothing. Both now happen in the merge path, with the build queueing
252 shared between it and post-receive rather than living in one of them.
253 #65
254
255Replace the binary and restart.
256
257* v1.2.0 — 2026-08-31
258
259A merge request said what its state was and almost nothing about when it
260got there. It now keeps time.
261
262- Reviews and checks carry the moment they last said something, on the
263 merge request page and in =mr show=. A =ci/<job>= check also reports how
264 long its build ran, so the timing of a run is readable without opening
265 it. Checks posted through =status set= have no build and report only the
266 time. !137
267- A merged or closed merge request names who resolved it and when. The
268 header stated "X wants to merge" whatever the state; it now says "X
269 merged A into main on <date>", or "closed this without merging", and
270 drops the claim entirely for a row that carries no stamp rather than
271 inventing a time.
272- =mr show= gains =merged_at=/=merged_by= and =closed_at=/=closed_by=, a
273 =created_at= per review, and =updated_at= plus =duration= per check, in
274 both JSON and text. Additive: nothing existing changed shape.
275- The iOS client renders all of it as of krz/gitbay-ios!37.
276
277Replace the binary and restart. Migration 0029 adds four columns to
278=merge_requests= and backfills the merge stamp for merge requests already
279merged, reading the =mr.merged= events. A merge with no such event to read
280— an import, or a row older than its events — keeps no stamp, and every
281surface says nothing about when it happened rather than guessing.
282
283* v1.1.0 — 2026-08-31
284
285Every release until now answered questions. This one notices something
286on its own: that a repository's dependencies have moved, and says so
287without being asked.
288
289- Dependency update checks, opt-in per repository. A daemon worker reads
290 the manifests on the default branch, asks the ecosystem's registry what
291 the current release is, and maintains one issue per repository — opened
292 when something falls behind, rewritten when the set changes, closed once
293 nothing is behind. No package manager runs, so it needs no CI runner and
294 no configuration beyond turning it on. #58
295 - =go.mod= against proxy.golang.org, =package.json= with
296 =package-lock.json= against npm, =Cargo.toml= with =Cargo.lock=
297 against crates.io, =requirements.txt= and =pyproject.toml= against
298 PyPI. A lockfile wins where both exist. A requirement naming a set
299 rather than a release — a range, a wildcard, a git or path source — is
300 skipped, since a range that already admits the newest release is not
301 news.
302 - =repo deps enable|disable|status=, a toggle on the repository settings
303 page, and the same three over the JSON API.
304 - Off by default, because checking a private repository tells a public
305 registry what it depends on. That is the owner's disclosure to make.
306 =[deps] check_interval_hours= sets the cadence, default 24.
307 - The issue is authored by a =gitbay-bot= account, so the existing
308 notification mail reaches the repository's owner rather than excluding
309 them as the actor. Its table is padded to its columns, which a
310 renderer ignores and a mail client needs. #61
311- =help= takes a prefix — =help mr= narrows the registry to one noun — and
312 every command now documents its arguments, so the server answers "what
313 are the flags" instead of being guessed at. #57
314- Web: settings rows end in one column of controls, checkboxes drawn at
315 the height of the inputs and buttons they sit beside #59; an added line
316 keeps its leading dash in the diff; a contributor's several verified
317 addresses collapse to one row #56.
318
319Replace the binary and restart. Migration 0028 adds two tables and, when
320the name is free, the =gitbay-bot= account. An instance already using that
321name for a user or an org keeps what it has: the account is not created,
322and dependency checks report that as the reason they cannot open an issue
323rather than the migration failing and the daemon not starting. #64
324
325* v1.0.1 — 2026-08-30
326
327Two CI fixes found by running orgo's release pipeline on this instance.
328
329- A runner killed between claiming a build and reporting it left the build
330 =running= forever, and the commit's =ci/<job>= status pending with it.
331 =runner next= now fails builds past a 90-minute deadline — longer than the
332 runner's own =-timeout= — and resolves their commit status. #53
333- =gitbay keys add= and =gitbay repo deploy-key add= take stdin as a bare
334 =< key.pub=, but only forwarded it when =--file -= appeared in the
335 arguments, so both sent an empty body and rejected input the SSH API
336 accepts. #55
337
338Replace the binary and restart.
339
340* v1.0.0 — 2026-08-26
341
342The web finishes the job #35 set it: reading, reviewing and responding,
343with the CLI still the complete interface. Every capability exists over
344SSH, every web write dispatches the same control command, and anything
345whose input is a credential stays on the command line. The [[https://gitbay.org/krz/gitbay/wiki/Parity][Parity]] page in
346the wiki is the maintained matrix and says which rows are deliberately
347CLI-only.
348
349- Diff view: one foldable section per file with line-number gutters,
350 per-file stats, rename and binary handling, and syntax highlighting
351 run per hunk per side so multi-line constructs lex as real code.
352 Commit and merge request pages share it; review threads anchor
353 inline.
354- Repository facts on the code page: commit, branch and tag counts,
355 detected license, latest release, build status, a language census by
356 tracked bytes, and contributors resolved to accounts by verified
357 email. All derived from git at render time.
358- Account settings on the web: SSH keys with scope, OpenPGP keys, and
359 email addresses. Public keys are the only credential-shaped input the
360 web accepts — they are not secret, and a new user needs one
361 registered before the CLI is reachable to them. Token minting and
362 account export stay SSH-only.
363- Organizations are run from their page: membership and roles, teams,
364 team members, and team repository grants, for org admins.
365- Commit log shows each commit's combined check status and gains a path
366 filter, so per-file history is reachable without editing the URL.
367- Issue references from commit messages read "referenced in commit
368 <sha> by <author>", linking the author when their email is verified
369 here.
370- The rail's focus ring uses the shell's own mark: the light scheme's
371 accent was a dark blue ring on a black rail.
372
373No migrations. No new config.
374
375Upgrading from v0.5.0 is replace-the-binary-and-restart.
376
377* v0.5.0 — 2026-08-26
378
379A design pass and a parity pass. The web stops being a read-only
380mirror of the CLI without becoming the place you are expected to work.
381
382- New design: a black shell with a persistent left rail carrying
383 cross-repo state (pinned repos, review queue), the repo header
384 rendered identically on every tab so navigation never moves, sharp
385 lines, self-hosted IBM Plex, and code blocks that read against both
386 color schemes. Tree listings sort directories first and carry each
387 file's last commit; diffs, inputs and controls were reworked to
388 match.
389- Web parity with the CLI, dispatched through the same command
390 registry the CLI and JSON API use — every web write is the
391 equivalent =gitbay= command with =--source web=:
392 - merge requests: review, resolve threads, merge, close, and open a
393 new MR from the browser
394 - issues: state, labels, assignees, milestones
395 - repositories: settings, branch protection, visibility
396 - releases: create and edit; builds: trigger a job
397 Commands marked SSH-only still refuse over the web: build secrets,
398 mirror tokens, domain claims, token minting, deletion and transfer.
399- A dashboard that answers "what needs me": review queue, assigned
400 issues, pinned repos, and an activity feed. Author names resolve to
401 accounts and link to profiles wherever commits appear.
402- Build status badges at =/{owner}/{repo}/badge/build.svg= for public
403 repos.
404- =[web] title= sets the instance's display name, separate from the
405 hostname commands are pasted with.
406- =make build/test/deploy= targets.
407- Fixes: the mobile tab strip scrolls sideways only, long commit
408 subjects no longer overflow on narrow screens, the shell fills the
409 viewport with the line-length cap moved onto prose, and the account
410 cell lines up with the page footer.
411
412No migrations. New config: =[web] title=.
413
414* v0.4.0 — 2026-08-25
415
416- Git LFS: standard clients work over both transports.
417 =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
418 included; download needs read, upload write), minting stateless
419 repo- and operation-scoped tokens for the batch API and basic
420 transfers. Anonymous HTTPS downloads for public repos; uploads
421 verified against size and sha256 before landing. Storage is
422 content-addressed under =[lfs] root= behind a small interface an
423 S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
424 objects (512MB default).
425- Build failures mail the repo's notify targets with the log tail and
426 build link — failed scheduled jobs reach an inbox.
427- =release edit= updates a release's title and notes (absent flags
428 keep their field); omaha-style CI note rebuilds work again.
429- Syntax highlighting follows the color scheme: class-based chroma
430 with light and dark palettes, the light-pinned code background is
431 gone, and markdown fences and org src blocks highlight too. The UGC
432 sanitizer admits only chroma's token-code classes.
433
434No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
435
436* v0.3.0 — 2026-08-25
437
438- CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=
439 over SSH (admin-only runner protocol; statuses feed =require-checks=).
440 Per-repo secrets set over stdin and injected into build environments;
441 cron schedules (server-local time) and tag-glob triggers, mutually
442 exclusive per job; =build list/show/log/trigger= and a builds tab.
443- Pages: public repos' =pages= branches served on =<owner>.<domain>=
444 (=[pages] domain=), custom domains with DNS TXT ownership challenges
445 and 7-day expiry for pending claims, per-subdomain on-demand ACME.
446- Wikis (=.wiki= companion repos, access mirrors the parent) and teams
447 within orgs (members-role scoping, per-repo team grants).
448- Activity graphs on user and org pages, backfillable
449 (=admin backfill-activity=); commits attributed by verified author
450 email, deduped by sha.
451- MR pages list the commits the MR carries; =mr show= gains a commits
452 section.
453- Per-file history: =?path== on the web log, =--path= on =repo log=,
454 history link on blob pages.
455- Mirror status surfaced in =repo show= and the repo header
456 (admin-only), with sync errors visible; tag-only pushes now schedule
457 mirror syncs.
458- Rendering: GFM tables/strikethrough/autolinks/task lists, blob image
459 previews, raw serves images with real content types (README images
460 render under nosniff), 0BSD license recognition, repo website links,
461 compact dashboard pins.
462- =admin user delete= for accounts that anchor nothing, with named
463 blockers otherwise.
464- Fixes: wiki pages no longer overflow on mobile (iOS font-inflation
465 trigger), GHSA-free deps, secret values pipe correctly through the
466 CLI.
467
468Migrations 0020-0025 apply on start. New config: =[pages] domain=.
469The runner is a new binary (=gitbay-runner=); see the wiki's Admin
470guide for setup. Stress-tested against an import of git.git (82k
471commits): see the wiki's Performance page.
472
473* v0.2.0 — 2026-08-24
474
475- Deploy keys: repo-bound CI keys (=repo deploy-key=), ro/rw, rename- and
476 transfer-proof.
477- Commit statuses (=status set/list=), combined state on MR pages, and a
478 =require-checks= merge gate.
479- Email notifications for issue and MR activity (participants with
480 verified addresses; never the actor).
481- Inline review threads on MR diffs (=mr diff-comment/threads/resolve=),
482 stale on force-push, =require-resolved= merge gate.
483- Required approvals with CODEOWNERS (=require-approvals=; latest review
484 wins, author excluded) and a =require-resolved= gate; merge gate order
485 is checks → approvals → CODEOWNERS → resolved threads → signatures.
486- Web design revamp: token-based stylesheet (light+dark), wordmark and
487 favicon, aligned layout grid, card-based listings, designed 404,
488 mobile pass.
489- Cross-references and mentions: =#N=, =!N=, =owner/name#N=, =@user=
490 autolink in issue/MR text, viewer-aware for private repos.
491- Archived repositories (read-only with badge) and repo topics.
492- Blame view with signature-aware attribution and 1000-line pages.
493- Repository search (name/description/topic) and per-repo code search
494 (=repo grep=, web search tab); blob line anchors.
495- Homepage: dashboard for logged-in users (pinned repos via =repo pin=,
496 open MRs and issues involving you), landing page for visitors, full
497 public listing at =/explore=; MR diffs collapsed by default.
498- Milestones (=milestone create/list/close=, =issue/mr milestone=) with
499 web progress; issue templates from =.gitbay/issue-template*.md=
500 (CLI =$EDITOR= prefill and web form).
501- Issue actions from commit messages landing on the default branch:
502 =closes/fixes/resolves #N= closes, bare =#N= leaves a reference
503 comment; once per issue+commit.
504- Vanity Go imports: =[go_import]= config serves go-import meta tags, so
505 =go install gitbay.org/gitbay/cmd/...@latest= works.
506- Release script: =deploy/release.sh <tag>= builds reproducible
507 linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
508- Repository maintenance: =admin gc= (repack/prune, per-repo sizes),
509 =admin stats= (counts + disk usage), weekly =gitbay-gc.timer=.
510- Releases: tag-anchored notes and binary assets (=release= commands,
511 assets over SSH stdin/stdout, web releases tab with downloads).
512- GitHub history import: =repo import-issues= brings issues and PRs
513 (as merged/closed MRs) with comments, labels, and state, attributed
514 inline and resumable.
515- Push and pull mirroring (=repo mirror=): background sync, read-only
516 pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
517- Web signup at =/register= for open and invite instances.
518- Audit log (=audit=, =gitbayd admin audit=): every mutating command
519 with source key fingerprint, registrations, force-pushes, auth
520 failures. Hardening: per-IP auth-failure throttling
521 (=ssh_auth_rate=), =max_pack_bytes= enforced, =admin user
522 disable/enable=.
523- Account migration: =gitbay migrate --from <host>= (bundle
524 export/replay + client-side git mirror); =gitbay auth export= as a
525 user-level backup.
526- Editable issues and MRs (=issue edit=, =mr edit=, web forms).
527- Commit references appear as system messages with linked shas.
528- Design: top nav, repo listing rows (topics, license, last updated),
529 file table headers, README relative-link resolution, branch
530 dropdown, web pinning, org owner picker, label filters, linked
531 usernames and commit parents, =/privacy= page, blue accent.
532
533Upgrade notes: migrations 0006–0019 apply on start. No config changes
534required; =[go_import]=, =[mirrors]=, =web.privacy_notice=, and
535=web.mode = "accounts"= are opt-in.
536
537* v0.1.0 — 2026-08-24
538
539First tagged release: the complete CLI-first forge. SSH control plane
540(bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues,
541merge requests (ff/merge/squash/rebase with signature policy), OpenPGP
542and SSHSIG verification with retroactive re-verification, orgs, repo
543import, web UI (view-only or accounts mode), registration with invites
544and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups,
545ACME TLS, systemd deployment.