CHANGELOG.org

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