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