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