CHANGELOG.org

v1.0.0
gitbay/CHANGELOG.org rendered · source · history · blame · raw

212 lines · 11139 bytes

  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.0.0 — 2026-08-26
  8
  9The web finishes the job #35 set it: reading, reviewing and responding,
 10with the CLI still the complete interface. Every capability exists over
 11SSH, every web write dispatches the same control command, and anything
 12whose input is a credential stays on the command line. The [[https://gitbay.org/krz/gitbay/wiki/Parity][Parity]] page in
 13the wiki is the maintained matrix and says which rows are deliberately
 14CLI-only.
 15
 16- Diff view: one foldable section per file with line-number gutters,
 17  per-file stats, rename and binary handling, and syntax highlighting
 18  run per hunk per side so multi-line constructs lex as real code.
 19  Commit and merge request pages share it; review threads anchor
 20  inline.
 21- Repository facts on the code page: commit, branch and tag counts,
 22  detected license, latest release, build status, a language census by
 23  tracked bytes, and contributors resolved to accounts by verified
 24  email. All derived from git at render time.
 25- Account settings on the web: SSH keys with scope, OpenPGP keys, and
 26  email addresses. Public keys are the only credential-shaped input the
 27  web accepts — they are not secret, and a new user needs one
 28  registered before the CLI is reachable to them. Token minting and
 29  account export stay SSH-only.
 30- Organizations are run from their page: membership and roles, teams,
 31  team members, and team repository grants, for org admins.
 32- Commit log shows each commit's combined check status and gains a path
 33  filter, so per-file history is reachable without editing the URL.
 34- Issue references from commit messages read "referenced in commit
 35  <sha> by <author>", linking the author when their email is verified
 36  here.
 37- The rail's focus ring uses the shell's own mark: the light scheme's
 38  accent was a dark blue ring on a black rail.
 39
 40No migrations. No new config.
 41
 42Upgrading from v0.5.0 is replace-the-binary-and-restart.
 43
 44* v0.5.0 — 2026-08-26
 45
 46A design pass and a parity pass. The web stops being a read-only
 47mirror of the CLI without becoming the place you are expected to work.
 48
 49- New design: a black shell with a persistent left rail carrying
 50  cross-repo state (pinned repos, review queue), the repo header
 51  rendered identically on every tab so navigation never moves, sharp
 52  lines, self-hosted IBM Plex, and code blocks that read against both
 53  color schemes. Tree listings sort directories first and carry each
 54  file's last commit; diffs, inputs and controls were reworked to
 55  match.
 56- Web parity with the CLI, dispatched through the same command
 57  registry the CLI and JSON API use — every web write is the
 58  equivalent =gitbay= command with =--source web=:
 59  - merge requests: review, resolve threads, merge, close, and open a
 60    new MR from the browser
 61  - issues: state, labels, assignees, milestones
 62  - repositories: settings, branch protection, visibility
 63  - releases: create and edit; builds: trigger a job
 64  Commands marked SSH-only still refuse over the web: build secrets,
 65  mirror tokens, domain claims, token minting, deletion and transfer.
 66- A dashboard that answers "what needs me": review queue, assigned
 67  issues, pinned repos, and an activity feed. Author names resolve to
 68  accounts and link to profiles wherever commits appear.
 69- Build status badges at =/{owner}/{repo}/badge/build.svg= for public
 70  repos.
 71- =[web] title= sets the instance's display name, separate from the
 72  hostname commands are pasted with.
 73- =make build/test/deploy= targets.
 74- Fixes: the mobile tab strip scrolls sideways only, long commit
 75  subjects no longer overflow on narrow screens, the shell fills the
 76  viewport with the line-length cap moved onto prose, and the account
 77  cell lines up with the page footer.
 78
 79No migrations. New config: =[web] title=.
 80
 81* v0.4.0 — 2026-08-25
 82
 83- Git LFS: standard clients work over both transports.
 84  =git-lfs-authenticate= joins the SSH dispatcher (deploy keys
 85  included; download needs read, upload write), minting stateless
 86  repo- and operation-scoped tokens for the batch API and basic
 87  transfers. Anonymous HTTPS downloads for public repos; uploads
 88  verified against size and sha256 before landing. Storage is
 89  content-addressed under =[lfs] root= behind a small interface an
 90  S3-compatible backend can drop into; =[lfs] max_object_bytes= caps
 91  objects (512MB default).
 92- Build failures mail the repo's notify targets with the log tail and
 93  build link — failed scheduled jobs reach an inbox.
 94- =release edit= updates a release's title and notes (absent flags
 95  keep their field); omaha-style CI note rebuilds work again.
 96- Syntax highlighting follows the color scheme: class-based chroma
 97  with light and dark palettes, the light-pinned code background is
 98  gone, and markdown fences and org src blocks highlight too. The UGC
 99  sanitizer admits only chroma's token-code classes.
100
101No migrations. New config: =[lfs] root=, =[lfs] max_object_bytes=.
102
103* v0.3.0 — 2026-08-25
104
105- CI: =.gitbay/ci.yml= jobs run as builds claimed by =gitbay-runner=
106  over SSH (admin-only runner protocol; statuses feed =require-checks=).
107  Per-repo secrets set over stdin and injected into build environments;
108  cron schedules (server-local time) and tag-glob triggers, mutually
109  exclusive per job; =build list/show/log/trigger= and a builds tab.
110- Pages: public repos' =pages= branches served on =<owner>.<domain>=
111  (=[pages] domain=), custom domains with DNS TXT ownership challenges
112  and 7-day expiry for pending claims, per-subdomain on-demand ACME.
113- Wikis (=.wiki= companion repos, access mirrors the parent) and teams
114  within orgs (members-role scoping, per-repo team grants).
115- Activity graphs on user and org pages, backfillable
116  (=admin backfill-activity=); commits attributed by verified author
117  email, deduped by sha.
118- MR pages list the commits the MR carries; =mr show= gains a commits
119  section.
120- Per-file history: =?path== on the web log, =--path= on =repo log=,
121  history link on blob pages.
122- Mirror status surfaced in =repo show= and the repo header
123  (admin-only), with sync errors visible; tag-only pushes now schedule
124  mirror syncs.
125- Rendering: GFM tables/strikethrough/autolinks/task lists, blob image
126  previews, raw serves images with real content types (README images
127  render under nosniff), 0BSD license recognition, repo website links,
128  compact dashboard pins.
129- =admin user delete= for accounts that anchor nothing, with named
130  blockers otherwise.
131- Fixes: wiki pages no longer overflow on mobile (iOS font-inflation
132  trigger), GHSA-free deps, secret values pipe correctly through the
133  CLI.
134
135Migrations 0020-0025 apply on start. New config: =[pages] domain=.
136The runner is a new binary (=gitbay-runner=); see the wiki's Admin
137guide for setup. Stress-tested against an import of git.git (82k
138commits): see the wiki's Performance page.
139
140* v0.2.0 — 2026-08-24
141
142- Deploy keys: repo-bound CI keys (=repo deploy-key=), ro/rw, rename- and
143  transfer-proof.
144- Commit statuses (=status set/list=), combined state on MR pages, and a
145  =require-checks= merge gate.
146- Email notifications for issue and MR activity (participants with
147  verified addresses; never the actor).
148- Inline review threads on MR diffs (=mr diff-comment/threads/resolve=),
149  stale on force-push, =require-resolved= merge gate.
150- Required approvals with CODEOWNERS (=require-approvals=; latest review
151  wins, author excluded) and a =require-resolved= gate; merge gate order
152  is checks → approvals → CODEOWNERS → resolved threads → signatures.
153- Web design revamp: token-based stylesheet (light+dark), wordmark and
154  favicon, aligned layout grid, card-based listings, designed 404,
155  mobile pass.
156- Cross-references and mentions: =#N=, =!N=, =owner/name#N=, =@user=
157  autolink in issue/MR text, viewer-aware for private repos.
158- Archived repositories (read-only with badge) and repo topics.
159- Blame view with signature-aware attribution and 1000-line pages.
160- Repository search (name/description/topic) and per-repo code search
161  (=repo grep=, web search tab); blob line anchors.
162- Homepage: dashboard for logged-in users (pinned repos via =repo pin=,
163  open MRs and issues involving you), landing page for visitors, full
164  public listing at =/explore=; MR diffs collapsed by default.
165- Milestones (=milestone create/list/close=, =issue/mr milestone=) with
166  web progress; issue templates from =.gitbay/issue-template*.md=
167  (CLI =$EDITOR= prefill and web form).
168- Issue actions from commit messages landing on the default branch:
169  =closes/fixes/resolves #N= closes, bare =#N= leaves a reference
170  comment; once per issue+commit.
171- Vanity Go imports: =[go_import]= config serves go-import meta tags, so
172  =go install gitbay.org/gitbay/cmd/...@latest= works.
173- Release script: =deploy/release.sh <tag>= builds reproducible
174  linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
175- Repository maintenance: =admin gc= (repack/prune, per-repo sizes),
176  =admin stats= (counts + disk usage), weekly =gitbay-gc.timer=.
177- Releases: tag-anchored notes and binary assets (=release= commands,
178  assets over SSH stdin/stdout, web releases tab with downloads).
179- GitHub history import: =repo import-issues= brings issues and PRs
180  (as merged/closed MRs) with comments, labels, and state, attributed
181  inline and resumable.
182- Push and pull mirroring (=repo mirror=): background sync, read-only
183  pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
184- Web signup at =/register= for open and invite instances.
185- Audit log (=audit=, =gitbayd admin audit=): every mutating command
186  with source key fingerprint, registrations, force-pushes, auth
187  failures. Hardening: per-IP auth-failure throttling
188  (=ssh_auth_rate=), =max_pack_bytes= enforced, =admin user
189  disable/enable=.
190- Account migration: =gitbay migrate --from <host>= (bundle
191  export/replay + client-side git mirror); =gitbay auth export= as a
192  user-level backup.
193- Editable issues and MRs (=issue edit=, =mr edit=, web forms).
194- Commit references appear as system messages with linked shas.
195- Design: top nav, repo listing rows (topics, license, last updated),
196  file table headers, README relative-link resolution, branch
197  dropdown, web pinning, org owner picker, label filters, linked
198  usernames and commit parents, =/privacy= page, blue accent.
199
200Upgrade notes: migrations 0006–0019 apply on start. No config changes
201required; =[go_import]=, =[mirrors]=, =web.privacy_notice=, and
202=web.mode = "accounts"= are opt-in.
203
204* v0.1.0 — 2026-08-24
205
206First tagged release: the complete CLI-first forge. SSH control plane
207(bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues,
208merge requests (ff/merge/squash/rebase with signature policy), OpenPGP
209and SSHSIG verification with retroactive re-verification, orgs, repo
210import, web UI (view-only or accounts mode), registration with invites
211and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups,
212ACME TLS, systemd deployment.