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