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