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