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