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