CHANGELOG.org

• /explore lists public repositories by latest activity, builds not counted, 20 to a page (#326). The explore command keeps its order.
• A profile's repositories tab uses the one-line rows of /explore.
• The footer no longer shows the commit hash.

What an instance owes the people who host on it: accounts delete themselves, organizations have quotas, and the footer links the operator's abuse and terms pages.

Upgrade note. Migrations run on start. The new limits default to unlimited and the footer links to none, so nothing changes until the config sets them. Set an override on any large organization (admin org limits <org> --repos 0 --bytes 0) before setting max_bytes_per_org. The username ghost is now reserved: an instance with a real account of that name must rename it before an account can be deleted.

• account delete --confirm <username> (gitbay auth delete, and the bottom of /settings) mails a link to the primary verified address (#322). Opening it disables the account; seven days later it is purged. Signing in on the web, or any command over SSH with a full-scope key, cancels; other key scopes and API tokens are refused. The purge deletes the account's repositories, snippets, keys, addresses and tokens, and moves the issues, merge requests, comments and reviews it wrote elsewhere to a reserved ghost account. Pending draft comments go, and its reviews no longer count toward a merge. The only admin of an organization, or of the instance, is refused. admin user show reports a scheduled deletion; an admin's disable or enable replaces it.
• Quotas for organizations (#325): limits.max_orgs_per_user caps the organizations an account creates; max_repos_per_org and max_bytes_per_org cap each one as the per-user limits cap an account. admin org limits sets per-org overrides and admin user limits takes --orgs. repo transfer now applies the receiving owner's caps, user or organization.
• [web] abuse_url and terms_url add "Report abuse" and "Terms" to every page's footer (#323, #324). gitbay.org's are the wiki's Abuse and Terms pages.
• Dashboard rows with the same update time keep their order between calls (#320).
• Release binaries are gzipped, with SHA256SUMS over the archives (#321).

Every list and show at a terminal is a screen (#316–#319): a header block of labelled fields, the description, counted sections in bold blue, and a legend of the commands that apply now, chosen from the item's state and your access. Rows lead with a state glyph, references are dim, and nothing else is coloured. Piped and --json output are unchanged.

Upgrade note. The instance draws the screens, so any CLI from v1.41.0 shows them once the instance runs this release. The CLI from this release sends here= in --term; an older instance ignores it.

• Lists at a terminal drop their header row unless a column is a number or a size, and references are dim instead of cyan (#317). The next page is a Next page line with the command. Inside a clone, the CLI sends the repository it inferred as here= in --term, so suggested commands leave it out; an older instance ignores the option. Piped and --json output are unchanged.
• mr show, issue show, repo show and build show at a terminal are screens (#318): a header block, the description, counted sections, and a legend of the commands that apply, chosen from the item's state (mr rebase when behind, mr merge only when the gates pass, issue close only for the author or a writer). mr show adds the files with their line counts; repo show its open merge requests, open issues and latest commits; system events sit in their own Events section. Pending checks lead with ◐.
• mr list, issue list, build list and dashboard at a terminal are screens (#318). Rows that wait on you lead with ●. The terminal dashboard drops the server build and queue tables (admin stats has them; --json is unchanged) and shows a job's failed build only while it is that job's latest.
• Every repository command at a terminal is a screen (#319): repo log, tree, refs, symbols, list, search, bookmarks, topics, the secret, deploy-key, domain, access, mirror and runner lists, repo settings show (now with approvals, resolved threads, code owners and website), repo deps status, and repo commit, whose diff follows the screen.
• Account, notification, webhook and organisation commands at a terminal are screens (#319): keys, email, pgp, token and web sessions lists, whoami, profile show=/=set, org profile, notifications list and settings, notifications device list, webhook list and deliveries, org list=/=show, label and milestone lists (repo and org), org team list=/=show. The session's own key leads with ●; pgp list shows user IDs rather than their JSON; a webhook URL on screen is its scheme and host only.
• The remaining commands at a terminal are screens (#319): saved queries (and issue list=/=mr list with --query=/–q=), search (a section per kind), feed, mr revisions, issue templates, build jobs, status list, releases, snippets, wiki, explore, audit, and the admin commands (admin stats lists the 20 largest repositories). Every list and show is now a screen; the piped layout is the only other one.

Terminal output that reads at a glance (#312–#315): colour by meaning, coloured diffs, lists that show what needs you, and label swatches and hyperlinks where the terminal has them. Piped and --json output are unchanged apart from the items noted below.

Upgrade note. The CLI from this release sends truecolor and links in --term when the terminal supports them; an instance older than v1.41.0 turns those into plain output. Upgrade the instance first, or set GITBAY_TERM=basic until it is.

• [web] apple_app_ids serves /.well-known/apple-app-site-association as JSON, so links to this instance open in the listed iOS apps (TEAMID.bundle.id). The file names owners, repositories and the repository pages the gitbay iOS app has screens for; settings, forms, downloads, raw files, feeds and the API stay in the browser. Empty, the default, leaves the path a 404. (#310)
• The web shows an issue's Close/Reopen and a merge request's Close and draft controls to its author as well as to writers, matching the commands: an author without write access could do it over SSH but had no button. (#311)
• Terminal output reads at a glance (#312): colour by meaning across every list and view (private red, signature states, references in cyan, yellow only for what waits on you), future times as in 5h, sizes and durations humanized, no unnamed trailing column or trailing whitespace, a mostly blank title column held to a third of the width, section headings in one style with empty dashboard sections left out, and errors after a red error: with did you mean for a mistyped flag and the usage wrapped. Piped and --json output are unchanged, except that profile show's section labels are plural (links:, orgs:, members:, repos:) and an unknown flag's message names the nearest flag. The server ignores --term options it does not know.
• Diffs at a terminal are coloured (repo commit, repo diff, mr diff, mr range-diff) and made safe like other user text. repo commit is a view with the signature state, signer, checks and a link; piped, it no longer prints the subject twice. build log at a terminal drops the tools' own colour codes, makes the rest safe, and marks step lines, the failed step in red. (#313)
• At a terminal, lists and views say what to do next (#314). mr list adds checks, review state (the merge gates' rule; review requested in yellow when it is yours) and age; issue list adds labels, assignee (yellow when it is you), comments and age, each from one query per page. dashboard opens with what needs you and shows eight lines of activity; feed splits who, what and where so outcomes carry their colours. repo show adds the clone URL, open counts, the latest release and the default branch's checks; repo log shows the author's name, age and signature; repo refs lists tags newest version first (piped too) and the default branch first; repo tree leads with the name; release list drops the tag from titles and adds the date; build show lists steps with their outcome, the open merge request and the log command; milestone list marks overdue and shows progress; audit data reads as key=value; whoami shows instance, key and scope; auth keys list marks this session's key; issue, merge request and release creation print the page's URL. A column empty on every row is left out.
• The CLI tells the server what the terminal can show (#315): truecolor when COLORTERM is truecolor or 24bit, for a dot in each label's own colour in label list, and links in iTerm2, WezTerm, Ghostty, VS Code, kitty and VTE terminals, or with GITBAY_LINKS=1 (0 turns it off), for references that open their page (OSC 8). Checks read ✓ 3/3, ✗ 1 failed, • 2 pending.

A concurrency limit for pushes, and repo download under the pack limit (#308).

Upgrade note. Pushes now queue past two at once instance-wide and one per account or deploy key; a push idle for a minute after its pack starts, or not at pre-receive within fifteen minutes, is cut. Raise the [limits] push_* settings on an instance with heavier push traffic.

• Pushes have a concurrency limit of their own, separate from the pack budget: [limits] push_concurrency (2), push_per_principal (1), push_queue (16) and push_queue_wait ("60s"), read like the pack_* settings. One principal may have up to half of push_queue waiting, so parallel pushes from one account queue. A deploy key counts apart from the account that registered it. The slot is held until receive-pack and its post-receive hook have finished; a busy push exits 1 with "the server is busy: it is at its limit of concurrent pushes…", and the daemon logs a push limit warning at most once a minute. (#308)
• A push holding a slot is killed when its pre-receive has not started [limits] push_receive_timeout ("15m") after it took the slot, or, once its pack has begun or pre-receive has started, when nothing has moved either way for push_idle ("60s"). receive-pack runs with receive.keepAlive set from push_idle, so long hooks do not trip it. (#308)
• repo download over SSH and the API takes a slot from the pack limit, released once git archive exits; busy is exit 1 with the clone message, and 503 with Retry-After: 60 on both API endpoints. (#308)

DKIM verification for reply mail, and ids that are not reused after a delete (#306, #307).

Upgrade note. Migration 0074 rebuilds the users, orgs, repos, ssh_keys, api_tokens, webhook_deliveries and push_queue tables in one transaction; take a backup first (gitbayd admin backup). Migration 0075 removes grants, deploy keys and profile about rows that name a deleted account, organization or repository, and the daemon logs the counts with the "schema migrated" line. To authenticate reply mail without the mail host's Authentication-Results, set [mail.inbound] require_dkim = true.

• [mail.inbound] require_dkim makes gitbayd verify a reply's DKIM signature itself: one of the first five signatures must verify (rsa-sha256 with a key of 1024 bits or more, or ed25519-sha256), have a d= in relaxed alignment with the From domain, and cover From, the To or Cc holding the reply address, Content-Type, and Message-ID when present; an unsigned Content-Transfer-Encoding must be 7bit, 8bit or binary. The reply address is then read only from To or Cc. l=, rsa-sha1, an expired x= and a t= in the future are refused; a temporary DNS failure retries on the next poll; keys are cached for fifteen minutes; a passing signature is recorded so a copy posts once. Off by default; either it or trusted_authserv_id passing is enough. The start-up warning and admin mail inbound check now warn only when neither is set, and the check reports both settings. (#307)
• A reply whose header has a field name outside RFC 5322 ftext (From : x), no single From, or a repeated To, Cc, Message-ID, Content-Type or Content-Transfer-Encoding is refused. (#307)
• Ids of accounts, organizations, repositories, SSH keys, API tokens, webhook deliveries, queued pushes and builds are no longer handed out again after a delete. Before, the next row took the id of the newest deleted one, with anything that still named it: a deleted account's repository grants, a deleted repository's deploy keys, signed LFS and reply-by-mail tokens, a runner's claimed build. The migration rebuilds those tables and starts each sequence above every id still named (#306).
• Deleting an account or organization removes its repository grants and its parked profile about text, and deleting a repository removes its deploy keys. On upgrade, rows of these kinds left by earlier deletes are removed, and the "schema migrated" log line gives how many (#306).

Suggested changes, split diffs, reactions, saved queries, TeX math, code navigation, reply by mail, and web pages for the repository rows Parity listed as no.

Upgrade note. Migrations 0068–0073 run on start. Existing repositories have no symbol index until their next push to the default branch; gitbay admin symbols reindex <owner/name> builds one. Reply by mail is off until [mail.inbound] is configured; set trusted_authserv_id for any instance reachable from the internet (Admin wiki). On the web, repo delete and repo rename now need a recent sign-in, like transfer.

• The releases page uploads and removes release assets (the file is streamed to release asset add; removal asks for the name). The repository milestones page creates, closes and reopens milestones, and the org labels and milestones pages give org admins set, remove, create, close and reopen (#296).
• The repository settings page gains access grants and effective access, webhooks (add, remove, deliveries, redeliver; the secret is a form field passed on stdin and never shown again), rename, transfer and delete with typed confirmation. /new gains an import form for repo import (#296).
• Reply to notification mail to comment. With [mail.inbound] configured (an IMAP mailbox over TLS or STARTTLS, polled; password from password_file) and notifications settings reply on (per account, off by default; also on the account page), issue and merge request mail carries Reply-To: reply+<token>@<domain>. The token names the recipient, repository and thread, expires after thirty days, and is an HMAC under a key derived from the secret key file. A reply is posted as issue comment or mr comment by that account when it comes from one of the account's verified addresses and the account may still comment; quoted text and signatures are removed, HTML-only mail and automatic replies are refused, and a Message-ID posts once. Refusals mail nothing back and are audited as refused mail reply with the reason. admin mail inbound check tests the mailbox read-only. trusted_authserv_id makes a reply also need the mail host's DMARC pass or aligned DKIM pass in its topmost Authentication-Results header; unset, the daemon warns. A reply is refused when its account or repository was created after the token (a reused id). A migration adds users.notify_reply, notifications.reply_to and mail_replies. (#295)
• web diff set unified|split and a Diff layout control on the account page choose how the merge request, commit and compare pages draw a diff; ?layout=split|unified overrides it per request. The split layout puts old and new side by side, each column's line numbers comment on their own side, and a narrow window stacks the rows as a unified diff. Migration 0068 adds users.diff_layout. (#290)
• Suggested changes in review threads: a fenced suggestion block in an mr diff-comment body proposes replacement lines for the anchored range, and --start-line anchors a thread to a range. mr threads and the page show it as a diff, marked outdated once the lines change at the head or the file is renamed or deleted; the JSON carries it as suggestion. mr apply-suggestion and the page's button commit it to the source branch as the applier, under the branch's push policy and write rules; a queued merge sees it as a push. The thread is resolved when the applier could resolve it by hand, and otherwise stays open with the output saying so. On a repository requiring signed commits the CLI commits and signs it in the clone instead. repo commit-file and applying a suggestion refuse once the owner's storage quota is used up, as a push does. Migration 0069 (#288).
• Reactions on issues, merge requests and their comments: issue react and mr react with a fixed set of eight, counts and your own in show, comment ids in show, and buttons on the web pages (#291).
• Saved queries: query save|list|show|run|remove|pin|unpin keep a named query over issues and merge requests across every repository the caller can read (repo:, owner:, is:, label:, no:, milestone:, assignee:, author:, free text). issue list --query and mr list --query run one, --q takes one written out, both paged with {items, next}. dashboard gains queries for pinned ones; the web shows them on the dashboard and at /<you>/-/queries. An account keeps at most 50 saved queries, 10 pinned (#292).
• TeX math renders server-side as MathML in markdown ($…$, $$…$$) and org ($…$, \(…\), \[…\], LaTeX environments) wherever markup renders, through a subset converter in internal/texmath. Its output is cleaned by a policy admitting exactly the elements and attributes it emits; MathML written as raw HTML is still stripped. Anything outside the subset, and math past 1000 expressions or 256 KiB of TeX in one document, shows as source (#294).
• Code navigation. A push or merge to the default branch queues a symbol index of its tree, built by a background worker and keyed by the tree id, so an unchanged tree is not indexed again. repo symbols <owner/name> <query> finds definitions by name or prefix, and the blob view links names to their definitions, with a results page at /{owner}/{repo}/symbols and a per-file symbol list. Go is parsed; Swift, Rust, Python, JavaScript/TypeScript, C headers, shell, org and Markdown are matched by line. admin symbols reindex forces a rebuild. Migration: symbol_indexes, symbols and symbol_requests. (#293)

Merge when ready, build egress by trust class, and restore-drill tooling.

Upgrade note. The runner's host needs the builds table: run make deploy-runner (or install deploy/gitbay-runner-builds.nft and the drop-in by hand), scoped to a scratch repository first, and run deploy/runner-auth-flood-test.sh before pointing it back at real repositories. A runner started with -untrusted or a loopback -remote refuses to start without build cgroups. Runners off the daemon's host and -isolation none are unaffected.

• Marking notifications read from the web dispatches notifications read, so it counts against the write budget and is audited (#261).
• gitbay <cli path> --help for commands the CLI regroups (auth keys add, auth email list, repo topics list) prints EXAMPLES under the CLI's path instead of the registered one (#304).
• gitbayd admin backup --verify also checks every release asset the database names against its recorded size and sha256, and every archived LFS object against its name (#259).
• gitbayd admin restore-drill <archive> --into <dir> extracts a full archive into an empty directory, runs the --verify checks on the extracted copy, and prints the newest issue, comment and push it recovered and the elapsed time. The Admin wiki's Restore drill section lists what to restore, what to check and where to record it (#259).
• The runner starts each podman build under builds/trusted or builds/untrusted in its service cgroup, and a second nftables table (deploy/gitbay-runner-builds.nft) matches build traffic by that cgroup: no build reaches the host's loopback beyond DNS, or a private range; a trusted build keeps the internet and the forge's public 22, 80 and 443; an untrusted build gets TCP 80 and 443 and DNS, and not the forge. The runner's drop-in creates the cgroups and loads the table on every start, and the start fails without it. A runner with -untrusted or a loopback -remote refuses to start without build cgroups, which the table needs to match anything. make deploy-runner installs it. deploy/runner-auth-flood-test.sh runs the scratch-repository test: a build failing SSH logins must not lock the runner out. Run it before pointing the runner back at real repositories; the Admin page has the steps and the rollback. (#260)
• mr merge <n> --when-ready queues a merge until the gates pass, merging as the queuing user with their rights checked then; tried on a status, a review, a resolved thread, mr ready and a push to the source branch. A refusal the queuer can fix, such as a branch behind a require_signed_commits target, keeps it queued with the reason on mr show and the page. The queue is bound to the key or token it was made with: removing, revoking, expiring or narrowing it dequeues, as do losing write access, a push or retarget by someone who cannot write to the target, deleting the source branch, and closing. An expiring credential cannot queue. --cancel dequeues. mr show, mr list and the dashboard carry queued. Migration 0067 (#289).

Findings from the 2026-09-27 architecture review.

• webhook add reads the signing secret from stdin with --secret -; a value on the command line is refused, since argv shows in process listings and shell history. A script that passed the value must pipe it: printf %s "$SECRET" | gitbay webhook add <repo> <url> --secret -. The iOS app's webhook add breaks until it sends the secret on stdin (krz/gitbay-ios#21) (#284).
• repo import --from takes http and https URLs only; git:// is refused, since its connection cannot be held to a checked address. The host is resolved and checked like a mirror's, git connects only to the checked addresses with redirects off, and the system and global gitconfig are ignored. A source that redirects (a renamed repository) fails; import from the URL it redirects to. Needs git 2.37 or later on the server (#298).
• repo import-issues resolves and checks the API host and the git host once and connects only to the checked addresses: the API client dials them with no proxy from the environment and follows no redirect, and the pull-head fetch runs git pinned, with redirects off and without the system and global gitconfig. --api-base refuses credentials, a query or a fragment. An API that redirects (a renamed repository) fails; import under the new name (#301).
• repo mirror add refuses a host written numerically (127.1, 2130706433, 0x7f.1) when the mirror is added, rather than at its first sync (#298).
• A browser session creates credentials and grants access — keys, PGP keys, tokens, verified addresses, org and repository roles, transfers, repository visibility, webhooks, secrets, mirrors, and the admin promote/enable and repository-visibility actions — only within 15 minutes of signing in. An older session gets the form back with a "Sign in again" link, and the login returns to it. SSH and API tokens are unaffected (#297).
• The builds page's status badge section gives an org-mode snippet beside the Markdown one, for a README.org (#299).
• API tokens on the settings page: create with a scope and optional expiry, shown once; list; revoke with the name typed back; the registered page's next steps as a numbered list (#264).
• A wiki link to an existing non-page file (an .svg, .txt, .pdf) now resolves to the raw route instead of 404ing against the page route (#283).
• The new-issue form takes labels, milestone and assignee in one step for writers; a Discussion heading sits before comment threads; the build page's live note says the page updates itself; and the rail and the phone More menu render from one list (#271).
• The new-issue form keeps milestone and assignee through preview and a refused create, the way it already kept title, body and labels; a refused create re-renders the form with the draft and the refusal instead of an error page (#271).
• The merge request range-diff page renders a bad from=/=to= query parameter inline instead of 404ing; only an unknown merge request 404s (#271).
• Empty states on the web state the fact instead of a CLI command, and drop "yet" on a finished item; the merge request list offers a New merge request link, a fork link, or a sign-in prompt depending on what the visitor can do; and the search page's scope caption is always visible, not only before a first search (#270).
• Issues, milestones, org milestones and releases drop the CLI command from their empty states too, matching the rest of the register: a link to the web form that does the thing when one exists, otherwise just the fact (#270).
• The merge request list and compare page offer New merge request to a reader who owns a writable fork of the repository, not only to a writer (#270).

Credentials and sessions: revocation, delegation, expiry and an idle timeout (#256, #257, #276, #277).

Upgrade note. token create makes a read token unless given --scope full. A script that mints a token and then writes with it must add --scope full. Existing tokens keep their scope.

Upgrade note. Upgrade the instance before the CLI: an older server refuses the CLI's leading --path= argument as an unknown command, for the eighteen commands whose CLI path differs from the registry's (the gitbay auth ... commands and repo topics list).

Upgrade note. gitbayd needs server.secret_key_file (default /etc/gitbay/secret.key) and refuses to start without it. Before replacing the binary, run gitbayd admin secrets init as root and chown gitbay:gitbay /etc/gitbay/secret.key (deploy/install.sh does both when the file is missing). The first start seals the stored secrets. Back the key file up separately: admin backup archives do not carry it (see the Admin wiki, "Secret key"). Downgrading to an earlier release after values are sealed is not supported: an older gitbayd reads a sealed value's gbs1:... prefix as the literal secret.

Upgrade note. Archives now carry a directory entry for every directory, so a bare repository whose refs are all packed restores as a repository. An archive written before this release lacks those entries; if extracting one leaves a repository's refs/ directory missing, gitbayd admin backup --verify <archive> names it, and mkdir -p <root>/repos/<owner>/<name>.git/refs fixes it.

Upgrade note. repo import now refuses a git:// source and a --from URL carrying a query or fragment. Mirrors and imports whose host is written numerically (127.1, 2130706433, 0x7f.1) rather than as a dotted address are refused too; rewrite the URL before upgrading (#298).

• A token with a --ttl is refused on every command that creates a credential: tokens, keys, deploy keys, runner keys, login links, invites, accounts and verified addresses (#257).
• Tokens and SSH keys record the token they were created through. token revoke <name> lists what it created; --created revokes those too (#257).
• Removing an SSH key, a deploy key, or disabling an account closes the connections the key opened, a push in flight included (#256).
• keys add and repo deploy-key add take --ttl; an expired key is refused at authentication, and an open connection on it closes within 15 seconds. An expiring key cannot create credentials, like an expiring token. keys list and repo deploy-key list gain USED and EXPIRES columns, after the label (#277).
• token list at a terminal shows a future expiry as a time, not "just now" (#286).
• Browser sessions end after twelve hours without a request, and after seven days as before. Sessions open at upgrade get a fresh twelve hours. web sessions list shows when each was last used (#276).
• web login over SSH refuses a sixth link in an hour, the same bound the login page's mailed links have (#278).
• The HTTPS listener refuses TLS below 1.2, in both certificate modes (#281).
• Mail to a non-local relay requires TLS by default; a relay that does not offer STARTTLS gets no mail unless mail.require_tls = false restores the old behaviour. mail.tls = "implicit" speaks TLS from the first byte, for relays on port 465 (#280).
• Mirror sync resolves the host, checks the addresses and connects git only to them, with redirects off; a URL that now resolves to private space, or is not http or https, fails the sync with the reason on repo mirror list. A mirror of a renamed repository that redirects fails until its URL is updated. Sync ignores the system and global gitconfig. Needs git 2.37 or later: with an older git no mirror syncs, and each records why (#279).
• Webhook and mirror targets in 100.64.0.0/10 or on a multicast address are refused, as private addresses are (#279).
• The hook socket is mode 0600 and, on Linux, refuses a peer with another uid; each receive-pack gets its own token from sshd, stored hashed (migration 0063), and the hook must present it before the daemon acts. Operators: deploy with no push in flight, since a receive-pack started by the old daemon has no token and its post-receive will be refused by the new one (#282).
• Audit rows are hash-chained, each carrying the SHA-256 of the one before it (migration 0064), and the daemon logs a copy of every row it writes to its journal. gitbayd admin audit verify prints the row count and the last id and hash, and exits 1 naming the first row that was edited or whose predecessor was removed. The chain is unkeyed: someone who can write the database can recompute the later hashes, and verify catches an edit only when they were not recomputed. Comparing verify's last id and hash with the journal is the check for any change, including removing the newest rows (#275).
• Refused mutating commands (exit 3 or 4) are audited as refused <command>, and refused pushes as refused git-receive-pack, keeping flag names and the target but no values; ten a minute per account and 600 across the instance, counted per process, past which one refused.throttled row stands for the rest of the minute. Under ssh.mode = "system" each gitbayd shell connection counts separately (#275).
• Pushes refused in pre-receive (a branch or tag rule, a release anchor, an unsigned commit) are audited as refused push with the repository and ref names, and hook socket requests failing the peer or push-token check as refused hook, under the same caps (#275).
• Audit retention deletes by id, up to the newest row older than the retention, so a clock step back cannot leave a gap in the chain (#275).
• dashboard and feed print activity as sentences (cmc opened issue krz/gitbay#12) instead of raw event payloads, and a labelled event names its labels there and on the web feed. An issue assigned to you appears only under "assigned to you": the open_issues field of dashboard --json no longer includes issues assigned to the caller. notifications list names --all when only read items remain (#265).
• Help and usage print the command the way the caller typed it — usage: gitbay auth keys remove <fingerprint>, not the registry's own path. auth --help lists the email and API token commands alongside keys and PGP. A bad-flag error prints the same prefixed usage line a wrong-argument refusal does. Outside the CLI a usage refusal reads usage: ssh git@<host> ... on every surface, including the error text of the web UI and the JSON API (#267).
• An unregistered SSH key is refused with its own fingerprint and the real host, and both the web and ssh paths to register (#268).
• issue create takes --label (repeatable), --milestone and --assignee (repeatable), setting them in the same call instead of a separate one per field (#268).
• mr show pluralizes multi-row section headings with counts: commits (7):, checks (2):, reviews (3): (#268).
• repo readme <owner/name> [--ref <ref>] prints a repository's README, picked the same way the web page picks one (#268).
• repo show's mirror table truncates LAST SYNC to the second, like every other timestamp in a view (#268).
• A -- foreign_keys: off migration's foreign_key_check now runs inside the migration's own transaction, before commit, so a violation rolls the migration back instead of leaving the bad schema and user_version already persisted; the web pin and watch buttons dispatch through repo pin=/=unpin and repo watch=/=mute=/=unwatch instead of writing the store directly, so a refusal reaches the viewer as a message instead of being dropped, and the watch button now cycles three states — default, watching, muted — instead of two; the response that consumes a login link's ?token= sends Cache-Control: no-store, so no intermediary keeps a copy of the single-use URL; and wiki documentation fixes: API.org clarifies token commands work on the API, Parity.org documents batched review and web watch/pin dispatch, Threat-Model.org documents the login-link URL exception (#261).
• The account settings page quotes the CLI and SSH command forms that actually resolve; a test runs every command a web page quotes against the CLI and control registries so a renamed command fails CI instead of shipping a dead instruction (#263).
• The web merge request page lists all revisions with a "compare to previous" link on each revision after the first, so a reviewer whose approval a force-push staled can see what changed without leaving the browser (#269).
• CI secrets, webhook secrets, mirror tokens and push device tokens are stored sealed with AES-256-GCM (#273). gitbayd admin secrets init|rotate|check.
• Untrusted builds (merge requests from forks) get a fresh HOME removed after the build and no secrets; trusted builds keep a per-repository home under <workdir>/trusted-home. Deploy gitbayd before the runner; the old shared homes under the runner's workdir can be deleted. (#255)
• status set refuses ci/ contexts, which belong to the instance's builds. Build results are reused only from trusted builds on the same image. repo settings require-contexts names status contexts that must report green; setting any turns require-checks on, and one not yet reported counts as pending. (#258)
• A runner polling over loopback gives its podman builds GITBAY_SSH at 169.254.1.2, pasta's address for the host, with the port when it is not 22, since under pasta the container holds the host's public address. An nftables table limits what the runner's user reaches on the host to 127.0.0.1:22, DNS on loopback, and public 22, 80 and 443. The runner unit now requires the egress unit: run deploy/runner-podman-setup.sh (it installs nftables) before make deploy-runner. Deploy gitbayd, then the runner, after validating on a scratch repository per the CI page. (#260)
• build show names a failed build's step and duration; build log --step <n>|failed --tail <lines> reads one step's output or the last lines of the stored log. Deploy gitbayd before the runner: an older server refuses the runner's --step and --reason (exit 2), and its failed builds stay running until the reaper fails them. (#266)
• gitbayd admin backup encrypts archives to [backup] age_recipients when set (#274); --verify takes --identity <file>. Archive names gain .age; the shipped backup scripts and monitor match both.
• A full backup holds <root>/backup.lock from its database snapshot to its last repository; repo delete, repo rename, repo transfer, admin repo delete and org rename refuse with "a backup is running" while it runs. --verify now also runs git fsck --connectivity-only on each archived repository and names any that fail. (#259)
• A full backup archives each repository's HEAD, refs/ and packed-refs before its objects, so a push during the backup cannot leave an archived ref naming objects the archive lacks. The exception is git's own automatic gc after a push repacking during the walk: the archive can then miss objects, and --verify reports it. (#259)
• gitbayd admin gc and admin mr prune refuse with "a backup is running" during a full backup. A pack or loose object that git's automatic gc removes while the backup walks is skipped instead of failing the run; --verify reports it if a ref needed it. (#259)
• gitbayd admin backup and --verify no longer need the secret key file: sealed values are copied as they are. A missing database is refused instead of created. (#259)
• gitbayd admin backup refuses an --out inside server.root, and removes the snapshot directories and temporary archives a killed run left beside its archive once they are a day old. (#259)
• gitbayd admin backup --verify runs fsck with --git-dir, so a directory that is not a repository fails instead of git checking an enclosing one, and does not extract objects/info/alternates or a repository's commondir, so neither can point fsck at another repository on the host. (#259)
• gitbayd admin secrets init and rotate hold an flock on <key file>.lock, so two runs at once serialize. (#273)
• Git pack generation (clones, fetches, git archive --remote) over SSH, smart HTTP and git:// now shares one concurrency budget: limits.pack_concurrency (3), pack_per_principal (2), pack_queue (32) and pack_queue_wait (60s). Past the queue an SSH client sees "the server is busy…" and exits 1, HTTP gets 503 with Retry-After: 30, and git:// gets an ERR line. Operators: the defaults are tuned for a four-core host; set the three counts to -1 to turn the limit off. A running clone is killed when no write to its client completes for two minutes: a client reading below about 550 B/s, or an HTTP request body that takes over two minutes with nothing written back, is cut. Ref listings, pushes and repo download are unaffected. Under ssh.mode = "system" SSH clones are not counted, since each session is its own process (#262).
• Anonymous clones are counted per IPv4 address or IPv6 /64, and together hold at most pack_concurrency − 1 slots: an account can take the last slot when it is free, and anonymous clients cannot hold it (#262).
• A request turned away by the pack limit logs a warning naming the transport and whether the client was signed in, never its address, at most once a minute per transport (#262).
• Web archive downloads (/{owner}/{repo}/archive/{ref}.tar.gz) take a pack slot, answer 503 with Retry-After: 30 when none is free, and are killed when the client leaves or stops reading (#262).
• LFS transfer tokens name the SSH key that obtained them, deploy keys included, and every LFS request checks that the key is still registered, unexpired and on an enabled account: removing a key or disabling an account ends its tokens at once instead of within the hour (#285). Operators: tokens minted before the upgrade are refused. git-lfs asks git-lfs-authenticate for a token each time it runs, so only a transfer running across the restart fails, with "repository not found"; running the command again fixes it. A download from a public repository that presents a token issued before the upgrade is refused the same way, not served anonymously, and needs the same rerun.
• Every LFS request also repeats the repository check for the token's key: a collaborator whose access is revoked or reduced, or a reader of a public repository made private, loses the token's use with the access, and an upload token stops working once its repository is archived (#285).
• LFS transfer tokens carry a hash of their key's fingerprint beside its id, and a token whose key id now belongs to another key is refused, since SQLite gives a new key the id of the last deleted one. The token format changed: tokens minted before the upgrade are refused, and a transfer running across the restart needs running again (#303).

Terminal output for the CLI (#254).

Upgrade note. Upgrade the instance before the CLI: an older server refuses the CLI's leading --term argument as an unknown command. Against an older instance, set GITBAY_TERM=off and the CLI sends no terminal size.

• At a terminal, lists print under a header, fitted to the width, with states in colour and relative ages; the next page is a command on stderr. Piped output keeps the same tab-separated rows, with timestamps as RFC3339 to the second; repo log rows are tab-separated (were fixed-width) and repo settings show keys print as fields (require mr, not require_mr:).
• show commands print a title line, aligned fields, the body rendered from markdown or org, events one per line and comments under a rule, through a pager when longer than the screen.
• Help describes every flag, with defaults and examples, and gitbay --help groups the commands under WORK, REPOSITORIES, YOU and INSTANCE. help --json adds flags and examples.
• release list takes --limit and --cursor, and leaves the title empty when it repeats the tag. mr revisions's one-revision note moved to stderr. notifications device add prints registered device <n>. dashboard prints none under an empty section.

The CLI sends --term=<cols>[,color] as the first argument on the SSH command line, since OpenSSH's multiplexed sessions do not forward a session's SetEnv; the server reads it only there, and ignores it over HTTP. Stock ssh opts in with ssh git@gitbay.org -- --term=120,color issue list krz/gitbay (the -- keeps ssh from reading it as its own option) or -o SetEnv=GITBAY_TERM=120,color. Operators running the system-sshd forced command add AcceptEnv GITBAY_TERM to sshd_config for the SetEnv form; the --term argument needs no sshd configuration.

The landing page's recording (#253).

• The landing page plays a recording of signup to release from a terminal on gitbay.org, muted with controls, in place of the merged merge request picture. The quickstart block drops its comment. The tapes and the render script are in docs/demo/.
• /static/img/ serves gif, webm and mp4 with their own types and answers Range requests, which Safari needs to play video.
• The Quickstart wiki page shows the recording as a gif.
• The footer's iOS link goes to the App Store listing.

Following a running build (#250, #251), and the web interface guidelines review (#249).

• build log <owner/name> <n> --follow prints the stored log, then output as the runner sends it, then build <n> <status> on stderr once the build ends; the exit code is 0 whatever the outcome. The build page does the same without JavaScript while a build is queued or running: the log streams into the page and ends with "build finished: <status>". ?follow=0 and HEAD render it once.
• A follow ends when its reader leaves: a closed SSH channel (Ctrl-C over the CLI's shared connection included) or a closed page. A follow of a build still queued after ten minutes ends and says so, since nothing reaps a queued build. An account holds eight follows at once; signed-out viewers share one account's eight.
• A follow re-checks read access every two seconds by repository id, reloading the account: a repository made private or an account disabled ends it as not found; a rename does not.
• A restart ends open follows before the drain, with "gitbay is restarting; follow the build again in a moment" on every surface, instead of holding the drain for 30 s. Other requests, git transport included, drain as before.
• Over the JSON API the command answers when the build ends, with the whole log.
• Typed-name confirmation on removing an org member, removing a team member, revoking a team's repository grant, and promoting an account to admin. The team forms are split so the confirm field sits beside the removal only.
• Registration's email field is an email input; email, username, one-time-code, SSH key and identifier fields carry autocomplete, autocapitalize and spellcheck as fits. The merge request close field accepts the !12 its placeholder shows.
• The refs page's compare inputs are named by their visible labels; the line-comment link names its line. theme-color matches the rail.
• Behind a reverse proxy, turn response buffering off for the build page (X-Accel-Buffering: no covers nginx), or the live log arrives only when the build ends.

Three findings from an external review of the web UI (#248).

• Explore is a rail square at every width. It was .railopt, so it dropped below 34rem into the More menu, which exists only for a signed-in viewer: a signed-out phone had no route to the listing from any page. Six squares and the mark are 308px, inside a 320px phone.
• /register answers "no key yet?" in place, with the ssh-keygen and cat lines behind a disclosure, instead of linking out to the wiki over a half-filled form. The link also hardcoded gitbay.org.
• An empty /search says what to do next — fewer words, the same query across every kind, or the listing — rather than repeating the count line's "no matches".

The profile's tabs, reworked.

• The bar reads About, Repositories, Bookmarks, Snippets, and People for an organization's admins. /{owner} is About; the rest hang off /-/. A tab nobody may open is not offered and its URL is a 404.
• The activity graph moved inside About, with a log of the newest thirty events under it. The log counts what the graph over it counts: UserPublicEvents keys on the actor for a user, matching ActivityByDay, while an organization keeps OwnerPublicEvents. Both are public repositories only. activity.atom is still the feed that goes back further.
• Bookmarks are a tab on your own profile. repo bookmarks takes no owner and lists the caller's, so the tab is not offered on anyone else's and its URL is a 404 there. /bookmarks redirects to it.
• The snippet list renders inside the profile rather than on a page of its own, so it carries the header and the tab bar like every other section. A snippet itself is still its own page.

Eleven web findings, mostly alignment and affordance (#247).

• Logging out asks first. GET /logout is the confirmation page the rail's signout square and the More menu link to; the button on it posts to the same path, which is still what ends the session.
• Bookmarks and Snippets are gone from the rail and the More menu. Both land on the profile, where they are tabs, and every square left in the rail is an instance-level destination.
• A repository tree marks a directory with a folder glyph and a file with a file glyph. The trailing slash still says it in text and the glyphs are aria-hidden, so the cue no longer rests on the link colour alone. Per-filetype icons are deliberately not done.
• A /search hit carries its kind in a chip, in the words search prints, so the meta line no longer has to say "repository".
• A settings row lines its control up on the right: a checkbox, a number and a full-width text input all end on the same rule, with Save in its own column. The label column keeps a 14rem floor so a hint does not wrap a word to a line.
• The email rows on /settings put their buttons and confirm field on the right, so they line up however long an address is.
• /admin/users draws a disabled Promote on an account that is not active, rather than leaving the cell short, and the page is wide. At 48rem the Actions cell clipped the second form's button, which left its confirm field looking like it belonged to the button before it — an active row read as though Promote wanted the name typed. The cell is now two fixed slots, each right-aligned, so the role button, the confirm field and the access button each hold one column whichever controls a row carries: an admin's row has a field on both forms, a disabled account's enable form has none. The field is 14rem, which fits "type <name> to confirm" for a name of ordinary length.
• The profile's inactive tabs draw their underline in --line, so the strip reads as a track the current tab is marked in.
• .listhead sheds its children's block margins, which is what kept a p.meta from sitting level with the heading beside it.
• nav.tabs has a bottom margin.
• The footer links the iOS client.

The e2e suite runs in parallel (#246).

• startInstance linked a byte-identical 35MB gitbayd for each of the 207 tests, about 0.8s apiece: go's build cache covers the compile, not the link. Each binary is now built once per process, lazily, so a -run of one test links only what it needs.
• 202 of the 207 tests take t.Parallel; the five calling t.Setenv stay serial. freePorts allocates from an atomic counter instead of binding :0 and closing it, which raced once tests overlapped — waitForPort only asks whether something is listening, so the loser talked to another test's server.
• Locally on 12 cores the suite goes from 637s to two or three minutes. The -timeout floor the harness enforced (#143) is gone with the reason for it; make test and .gitbay/ci.yml still pass their own as a ceiling for a real hang.

Five findings from the outside review of the web UI (#241–#245).

• A run row on the builds page led with a ten-character sha, so recognising a build meant opening the commit or already knowing the sha (#241). build list resolves each distinct commit's subject in one git log and returns it as subject on every build, so the CLI, the API and the web all name the commit. The row leads with the subject and the sha follows as metadata; a build whose commit is gone falls back to the sha.
• build list takes --limit <n> and --cursor <c>, the keyset cursor issue list, mr list, repo list and feed already have (#244). Without the flags it returns the newest fifty matching builds as before, so existing scripts are unchanged — the cursor is what reaches past that window. The page asks for thirty, offers "older" carrying every filter, and says its count is this page's when there is another. Before, filtering to a sparse status reached much further back within the same cap and appeared to raise the run count.
• The profile is sections rather than one stack (#242). /{owner} is the repository list; About, Activity and an organization's People are tabs beside it at /{owner}/-/about, /-/activity and /-/people. A tab with nothing on it is not offered and its URL is a 404. The About text and the year of activity squares used to sit above the repository list and push it below the fold. profile show is unchanged.
• Explore names its filter: the number of repositories, the active query and a link that clears it, the line the builds page already carried (#243). An empty filtered list says nothing matched rather than that the instance has no public repositories.
• The landing page's picture was !315, closed without merging, with an empty review panel and alt text promising reviewers that were not there (#245). It is !450: merged, two CI checks reporting success with how long each ran, and an approval. The picture is a figure with a caption saying what it shows.

A push alert names the account it is for (#89).

• The payload carried path and nothing else, so a device signed in to more than one account could not tell which instance a notice came from: two instances can hold the same owner/name. It now carries instance, the instance's site_url, and user, the recipient's username — together the account's identity.
• DuePush joins users for the recipient; no schema change.
• notifications device add now returns the row id, so a client that wants to deregister does not have to list devices and match its own token against the truncated display value.
• The alert carries aps.badge, the recipient's unread inbox count. DuePush counts it at send time, a subquery against inbox, so a cleared inbox is reflected even though the row was queued earlier.

Push notifications to iOS devices (#89): activity reaches a registered phone the way it already reaches the inbox and mail.

• gitbayd talks to APNs directly over HTTP/2, authenticated by an ES256 JWT signed with an operator-supplied .p8 provider key. New config section [push]: enabled, key_file, key_id, team_id, topic (the app's bundle identifier) and environment (production | sandbox), all validated at load when enabled — a misconfigured [push] refuses to start rather than filling a queue nobody is watching. An APNs key belongs to a bundle id: a self-hoster ships their own build under their own topic to use this; the App Store build talks to gitbay.org.
• Migration 0059: push_devices and push_queue, and users.notify_push (default on).
• notifications device add (token on stdin), device list (token shown truncated), device remove <id>, and notifications settings push on|off. A device is dropped automatically when Apple reports the token dead (410 Unregistered or BadDeviceToken). With [push] enabled = false nothing is queued and device add refuses, rather than registering a device nothing can deliver to.
• [retention] push caps the delivery queue, beside mail.
• dashboard reports the push queue for admins beside the other five, by device id: a key_id or team_id Apple did not issue passes config validation and then dead-letters every send.
• issue assign now files a notice, so assignment reaches the inbox, mail and push.
• Notification text is sent in full, private repositories included: a repository's name and item number reach Apple and can appear on a lock screen.
• Web: the notification settings page carries the push toggle and the device list, with removal behind confirmation. No web page offers a device-add form — only the app can mint an APNs token.

The stylesheet URL carries the build's hash (#239).

• /static/style.css was served with a day's cache lifetime at an unversioned URL, and must-revalidate only forces a check once that lifetime expires. For a day after a deploy a browser rendered the new markup against its old stylesheet; the ETag was never consulted.
• The layout stamps the served bytes' hash on the link. A deploy changes the URL, so a cached copy cannot answer it, and a request carrying the current hash names bytes that cannot change and is served without revalidating at all.

The desktop layout (#226): the web UI uses a wide screen.

• One centered container at 100rem; the repository header, main and footer align on it. Text keeps its measure.
• The repository header is two rows: name, description and buttons, then the tabs.
• Issue, merge request, build, explore, search and notification rows are one line above 64rem, and those pages render at the container width.
• The dashboard is three columns: pinned repositories with open issue, merge request and last-build counts; a tile per queue with the queue rows below; the activity feed.
• A file navigator beside blob, blame and edit pages lists the file's directory and marks the file.
• Side columns: state, labels and open milestones on the issue and merge request lists; status, jobs and branches on builds; topics on explore; kinds on search; sections on repository settings, account settings and admin. A label or milestone nothing is filed under is left out, so the merge request list offers the labels that have merge requests rather than every label the repository holds; the branch group caps at ten, and the branch field below it still takes any ref.
• Below 62rem the facet and section columns become a closed disclosure before their content, headed by the filters in force, and the navigator hides, since the tree page is the navigator on a phone. Below 80rem the dashboard's pinned repositories return to a chip row above the queues.

Three accessibility defects the wider scan found, on pages the sixteen-page one never covered (#226):

• A label chip carries a tone per scheme. Chip text is 12px, which owes 4.5:1 against the ground mixed from the colour itself, and no single colour clears that on both canvases; the stored hex still names the label, and the page picks the tone. A page stamped light or dark now sets color-scheme to match, so native controls follow the theme.
• Every pre scrolls sideways, so every one takes tabindex"0"=: a keyboard reaches a blame view, a build log and a search match the way it already reached the pre blocks of rendered markup.
• A link that shares its line with other text is underlined — a path crumb, a heading that names an owner, an empty-state note. Link and muted text are 1.07:1 apart in dark.

The profile about text is a file (#236).

Upgrade note. Run gitbayd admin migrate-profile-about after upgrading. Migration 0058 parks each owner's about text in a holding table and drops the columns; that command writes it into a public <owner>/.gitbay. Until it runs, profiles that had an about show none. Nothing is lost in between — the table keeps the text.

• The about text on a profile is profile/README.md or profile/README.org on the default branch of <owner>/.gitbay, read with that repository's own access. The extension picks the renderer; .md, .org and .markdown resolve in that order. profile show gains about_path, the file the text came from.
• profile set and org profile lose --about, --about-format and --file. The about is written by a push or repo commit-file, the way a wiki page is. The settings page points at the file and offers to create the repository that holds it.
• Repository names may start with a dot; owner names may not. A repository whose name starts with a dot stays out of explore and off the profile's repository list, and remains in repo list and at its own URL.
• repo commit-file writes the first commit of a repository that has never been pushed to. An unresolvable branch is still an error anywhere the repository already has refs.

A web UI sweep.

• The rail's squares are 44px at every width, and its glyphs are 20px on a phone. Below 34rem eleven squares no longer fit, so explore, bookmarks, snippets, new repository, settings, admin and log out move into a More menu and the strip keeps dashboard, search, notifications, More and your account.
• Snippets are on the rail. The link on a profile page stays.
• /new creates an organization as well as a repository; the form leaves the profile page.
• repo fork takes --owner, and the web's Fork button opens a form with an owner and a name. The owner is you or an organization you administer, checked as repo create checks it; an organization's fork is not counted against your repository quota. A name of your own is how you fork the same repository twice.
• The dashboard's pinned key reads above the list rather than under it, its build dot sits on the row's centre line, and a pinned chip on the second row has its bottom border back.
• The activity feed drops its state dot.
• The SSH key and account tables keep each row on one line and scroll sideways, rather than wrapping a fingerprint or a timestamp.
• .pathbar actions sit on the centre line with the ref and the crumbs.

The SonarCloud dashboard is at zero (#238). Four of its 38 findings were real; the rest are dismissed with their reasons recorded on the dashboard.

• A trailing-slash redirect cannot leave the site. net/http fills URL.Scheme and URL.Host from an absolute-form request line, which RFC 7230 requires a server to accept, so GET http://evil.example/cmc/ answered 301 Location: http://evil.example/cmc. A browser sends absolute form only to a proxy, so nothing reached this through one directly.
• The global search, repository search and register forms no longer carry autofocus, which moved focus past the heading, the result count and the search page's filters. The diff line-comment box keeps it: that form renders only after the reader asks for it on a line, and with no JavaScript nothing else carries focus across the reload.

Every command runs on every surface, markup previews before it is written, and the web findings from the forge comparison (#232, #233, #234, #235).

Upgrade note. Dropping SSHOnly widens what a full-scope API token can do: it can now administer the instance and mint further tokens. Review the tokens you have issued and re-mint as --scope read any that only need to read.

• Every command now runs on every surface. The registry's SSHOnly flag is gone, and with it the refusal that met build secrets, mirror credentials, API token minting, web sessions, deploy keys, the audit log and instance administration when they arrived over HTTP. What a caller may do is the account's rights narrowed by the scope of the key or token the request came with, decided in one place. A full-scope API token can now do anything its owner can, minting another token included; a read-scoped one still cannot write. Operators should review the tokens they have issued and re-mint as --scope read any that only need to read (#234).
• /admin/users lists every account with the state filter and cursor admin user list takes, and runs promote, demote, disable and enable per row. Demote and disable ask for the username to be typed (#234).
• [registration] notify_admin mails the instance's admins when an account becomes active: an invite redeemed, or an open-mode signup that verified its address. Off by default, requires [mail], and queued like any other notice (#234).
• Every web form that takes markup has a Preview button beside its own submit: issue and merge request create, their edit and comment boxes, release create and edit, the profile about text, and the file editor on a path the forge renders. It renders the draft above the textarea and writes nothing (#235).
• Links inside running text are underlined: the meta lines on issues, merge requests and releases no longer tell a link apart by colour alone.
• File view line numbers are 24px targets and keep the focus ring; chroma's LineLink rule, which set outline: none, is dropped from the served palette.
• Every rendered <pre> and the landing page's quickstart block take keyboard focus, so a block that scrolls sideways can be reached.
• On one column the issue and merge request aside follows the thread instead of preceding it.
• The file tree at 320px keeps its last column inside the card.
• A path no route matches renders the 404 page instead of a plain-text body.
• An org image link with no description gets its file name as alt text, so a README badge is a named link.
• Release titles are h2.
• Text responses are gzipped for clients that accept it.
• web theme set system|light|dark and an Appearance section on the account page fix the colour scheme per account. Migration 0057 adds users.theme.
• A path that only misses because of a trailing slash redirects to the path without it: /cmc/ reaches /cmc, /cmc/-/snippets/ reaches /cmc/-/snippets (#233).

The icon nav is a top bar at every width.

• The 48px row of glyphs that narrow screens already used is now the only shell layout; the left column is gone. The row keeps the same order, labels and current-page mark, with settings, admin and the account cell at the far right.
• The landing picture is recaptured under the new shell.

The newcomer route names its web path (#226).

• After registering, the page and the verification mail say the code can be pasted under Settings after signing in with an emailed link, beside the terminal command.
• The SSH keys wiki page names this instance instead of a placeholder; the Quickstart leads with the browser route and Homebrew before go install.

Labels on merge requests (#231), and a one-column dashboard. Migration 0056 adds mr_labels; the daemon migrates on start.

• mr label <owner/name> <n> --add <l> --remove <l> attaches and detaches labels the way issue label does, resolving an org's label first and creating a repository label on the fly; mr list --label filters; mr show carries them; the event is mr.labeled.
• The merge request page has a Labels group with the same form as an issue; list rows show label chips and ?label= filters the list.
• label list and the labels pages count merge requests beside issues; removing a label detaches it from every issue and merge request. An org label folding repository rows moves merge request rows too.
• The dashboard is one column: the activity feed is a section after the queues, since the icon rail leaves no wide column to balance.

The follow-ups from the forge benchmark (#226) and two profile fixes.

• On a wide repository overview the About block (counts, licence, latest release, build, contributors, languages) and the clone commands sit in a column beside the file table; under 62rem the order is unchanged (#228).
• The landing page's Explore and Create an account routes sit above the picture, and the picture is capped so the first screen carries a call to action (#229).
• Each row of the merge request list shows the combined check state of its head, linking to the diff, and a comment count (#230). Labels on merge requests do not exist yet (#231).
• The profile page lists repositories after the activity graph, and a table in rendered prose keeps its last row's bottom border (#225).

A closed merge request can name the request that carried its change (#223). Migration 0055 adds the column; the daemon migrates on start.

• mr close <owner/name> <n> --by <m> records, at close time, that !m supersedes !n; mr edit <n> --superseded-by <m> sets it on a request already closed and --superseded-by none clears it. Both refuse a number that is not a request in the same repository, or the request itself. mr show carries the field.
• The web close form takes the number as an optional field. The closed request's title line says "in favour of !m"; the request it names says "supersedes !n". The state stays closed; nothing is inferred from prose.
• On a phone the dashboard's activity feed stacks after the queues; the aside-first rule is for checks and reviewers on a merge request (#222).

The site rail is an icon column (#220).

• At desktop the rail is a 3.5rem column of inline glyphs: dashboard, explore, search, notifications with the unread count as a badge, bookmarks, new repository, then settings and admin, then the account and sign-out. The search field leaves the rail; /search has its own.
• Under 52rem the rail is one 48px row that neither wraps nor scrolls.
• Every icon link carries an accessible name (aria-label, a title and visually hidden text) and hides its SVG from assistive tech; a test enforces it.
• Pinned repositories are a chip row under the dashboard heading; the review queue is the dashboard's section. Neither is in the rail.

The dashboard feed and the phone-width rail strip (#222, #220).

• Build events record their commit; the dashboard's activity feed folds a commit's jobs into one line per run with the combined state and a state dot. A status outside the known set is never shown as success.
• Feed times are relative, with the exact UTC time in a title, as the tree listings already do.
• Under 52rem the rail strip keeps the brand on its first row, shows pinned repositories as a compact labelled sub-row, and New repository is a + button at every width.

The web follow-ups to the design foundation (#219, #220, #221, #222, #224, #225), and a repository maintenance command.

• build list takes --ref, --status and --job, pushed down to the store query; the builds page reads the same three as GET parameters with shareable links, and groups a commit's jobs into one run showing the combined state (#224).
• The merge request page's "Files changed" view is wide; the conversation and commits views stay at reading width (#219).
• The profile page lists repositories above the biography; the contribution grid carries month labels and a legend (#225).
• The dashboard shows populated queues first, collapses empty ones to a heading, and says what the two Open lists cover (#222, in part).
• Under 52rem the rail strip keeps one scrolling row and shows pinned repositories as a second row instead of hiding them (#220).
• Polish from the v1.23.0 review: caption spans instead of dangling labels, runner attach keeps a rejected key and reports success, the tree root of the default branch is the repository home so the header is identical within the code tab, the file editor is wide (#221).
• admin mr prune <owner/name> <n>... --yes drops the named merged or closed MRs' refs/merge-requests/N/head and runs git gc --prune=now on the repository, for commits a history rewrite left reachable only through them. Open and source-gone MRs are refused. Nothing drops a head ref on its own. mr diff and the MR page say when a head is gone (#227).

The web design foundation (#218). Tokens measured in both schemes, one control family, content widths per page, and the landing, repository overview, merge request and settings pages recomposed. Set [web] title to gitbay in lower case; the templates already are.

• style.css rewritten on tokens defined on :root and again for dark; TestTokenContrast enforces the floors and TestEveryTemplateClassHasARule that every template class has a rule.
• Buttons are primary, secondary, quiet or destructive; one focus ring on everything; success and error flashes share one shape.
• Every page picks a width: wide for code, reading for lists and threads, bounded for forms.
• The repository header shows description and topics on the code tab only; the overview leads with the file table and puts clone commands and facts after the README; "Find file" is "Search code".
• A merge request states who merged or closed it under its title and explains an empty diff.
• Repository settings are bounded rows with a consequence beside each control, a saved flash, a rejected value kept, and topics as one field.
• Landing copy says what the product is and where to go; the register form says to paste the contents of the key file and links the SSH keys wiki page.
• The landing page shows the merge request page, light and dark, captured from gitbay.org (two embedded PNGs under /static/img/).

One merge gate fix.

• require-checks no longer refuses a merge request head that carries no statuses when nothing was going to report one: a repository with no .gitbay/ci.yml, or one whose jobs all wait on a schedule or a tag, had no mergeable merge request and no remedy but turning the setting off. A head whose config carries a job a push runs, and a head in a repository that has recorded a status before — which is what reporting from outside through status set looks like — is still refused (#216).

The CLI output sweep (#183). The rules are on the wiki's Users page, under "Output rules".

• A bad invocation prints the command's registered usage, the one source of it; the hand-written copies are gone.
• The gitbay CLI pads list rows into aligned columns at a terminal and leaves the tabs alone when piped.
• An empty list prints nothing on stdout and nothing to list on stderr.
• Every refusal (exit 4) says what to do instead.
• status list and repo topics print rows.
• admin runners remove; forget stays as an alias until the next release.
• A missing positional argument prints the hint and the usage line (#215).

The web UI/UX sweep (#182).

• Destructive controls ask for the object's name typed beside the button: release delete, snippet delete and file remove, team delete, label remove, and SSH key, email and PGP key removal. Reversible controls keep a plain button.
• Login returns to the page that asked for it, and says so.
• One timestamp format everywhere, 2006-01-02 15:04 UTC.
• Tags on the refs page and in the release form are in version order, newest first.
• The file editor explains up front when signed commits or merge-requests-only protection would refuse the commit, answers 404 for a branch that does not exist, and says when a path is new.
• Merge refusals name the strategy rather than the flag; an issue closed by a commit reads "closed by <who> in commit <sha>".
• Repository settings: every Save names its field. Labels: the colour column appears only when it means something. Sidebars use one shape for empty. List rows show the state only under "all" and say "in <milestone>". Global search counts its results. A merged MR shows its merged head and a deleted source branch. The repository home shows the SSH clone URL beside HTTPS. The settings page names auth token create.

One config check.

• A negative limits.max_snippets_per_user is refused at config load, as max_repos_per_user and max_bytes_per_user already were; it used to pass validation and read as unlimited (#214).

Snippets (#195): named text files a user owns outside any repository, shared by URL and edited in place.

• Migration 0054: snippets and snippet_files.
• snippet create|show|list|edit|delete and snippet file set|get|remove. Files are UTF-8 under limits.max_snippet_bytes (1MB), at most 64 per snippet; a snippet keeps at least one. limits.max_snippets_per_user (0, unlimited) caps how many an account may own, admins included. Visibility public, unlisted (default) or private; a private snippet is not found to everyone but its owner and admins.
• Web: /<owner>/-/snippets lists, each snippet page renders its files with a raw route per file, and the owner creates, edits and deletes from the page through the same commands. The owner page links to the list.

Labels and milestones an org defines once for every repository under it, and Closes owner/name#N acting across repositories (#203).

A runner that cannot hang on a dead connection, SSH keys with names, and dependency updates.

What the first real job on a user's runner needed. A twice-daily archive pull that had run on the server's host moved into a container and then onto a laptop, and each hop found a gap.

CI without the operator's compute: a runner anyone installs and attaches to their own repositories, and the server rule that makes that safe. The rest of the #184 list besides.

What stops a stranger from moving here: the repository plumbing and the team gates the #185 walk found missing, twelve merge requests merged as one stack.

Builds run in containers, a rebase is not rebuilt, and a runner restart no longer strands the build it was running.

Logging into the web without an SSH key, wikis inside the repository, CI that skips what a change does not touch, and the browser catching up with the command line on nine capabilities.

Only a writer's review decides a merge gate, and a scan of one branch stops overwriting another's results.

• mr review resolves with CanRead and applied no further check, and the merge gates counted every fresh verdict. On a public repository that let anyone with an account satisfy require_approvals — defeating four-eyes review by holding two accounts, which on an instance with open registration means defeating it outright — and equally let a passer-by block a merge the owner wanted, with no override and only a force-push to clear it. Both were confirmed against a running instance. Reviewing stays open to every reader, because an outside opinion on a public change is worth having; it no longer decides the gate. What does is write access, the same question the gates already answer. An uncounted review is marked advisory by mr show and by the merge request page, both reading the same rule, so the page cannot show an approval the gate ignores. #147
• The two git upload-pack spawns behind the smart HTTP transport now resolve git at start-up like everything else. The v1.13.2 rewrite matched a plain identifier for the context and these pass r.Context(), so it skipped them. #153
• CI analyses each branch as itself. Every scan was recorded against the project's main branch whatever branch produced it, so a feature branch replaced main's results — a branch that removes findings made main look clean before the fix merged, and one that added them made main look broken when it was not. #154

Replace the binary and reinstall the CLI. No migration.

A repository relying on approvals from accounts without write access will find those merges now refused. That was the defect: such an approval never meant the repository accepted the change. Grant write, or name the reviewer in CODEOWNERS and grant write, if their approval is meant to count.

The first SonarCloud scan's findings: eight fixed, the rest triaged and dismissed with reasons.

• A pages directory redirect could leave the site. Both redirects passed the raw request path to http.Redirect while the cleaned path sat a line above; net/url keeps a leading //, and Go emits Location: //evil.example/ unchanged, which a browser reads as protocol-relative. Reaching it needed a public repository named like a host under the subdomain's own owner — repository names permit dots — so it was narrow rather than impossible. The destination is built from the cleaned path through url.URL now, which also settles the two spellings the first fix missed: a .. that escapes to the root, and a backslash, which browsers following the WHATWG rules treat as a separator. #153
• The runner's default workspace was <tmp>/gitbay-runner: a fixed name in a world-writable directory, created with MkdirAll, which succeeds against a directory whoever already owns it. bay1 was never exposed — its unit names a workspace — but the default is what anyone running the binary by hand gets, and this is the process that clones repositories and exports build secrets. The default moves under the user's cache directory, the workspace is created 0700, and a symlink or a directory owned by someone else is refused. One we own that is merely too permissive is tightened rather than refused, since every runner before this one made it 0755 and refusing would take the runner down on upgrade. #153
• Logout and flash consumption expire their cookies with the attributes the setting calls used. Deletion worked either way; the difference was a reviewer's puzzle, and four findings. #153
• The topics-remove field has a label. A placeholder is not an accessible name. TestEveryInputHasAnAccessibleName is the guard that was missing, and it knows both associations — six inputs use <label>Name <input></label>, which is as good as for/id. #153
• git and ssh are resolved once at start-up rather than searched on every spawn, and gitbayd refuses to start when one is absent instead of failing on whichever request first needed it. This was 74 of the 118 findings; a dashboard that is mostly permanent noise is one nobody reads. #153

Also: SQLite migrations are excluded from analysis. They were read as PL/SQL, where '' is NULL, so WHERE col = '' on a NOT NULL DEFAULT '' column — correct SQLite, and the shape used throughout — read as a null-comparison bug.

Replace the binary and reinstall the CLI. No migration. A runner whose workspace is group- or world-readable will have it tightened to 0700 on next start, and will refuse to start if that workspace is a symlink or belongs to another user.

A command that reads its payload from stdin says so, and SonarCloud runs alongside the vulnerability scan.

• repo secret set blocked with nothing printed, which is indistinguishable from a hung connection, and pressing Enter did not end it because the server reads to EOF — so it looked the same before and after the value had been typed, and the secret echoed into the scrollback on the way. A terminal is now told what is wanted and that Ctrl-D ends it; a secret is read without echo and takes one line, so Enter is enough. Piped input is unchanged, byte for byte: printf %s "$TOKEN" | gitbay repo secret set ... still sends exactly the token. Applies to keys add, auth pgp add, repo deploy-key add and release asset add as well; public keys keep echoing, since they are public. #150
• A sonar CI job reports to SonarCloud, alongside vuln. Report-only: it does not gate a build, unlike the vulnerability scan. A merge request from a fork builds without secrets by design, so the job says why it is skipping there rather than failing on a missing credential. Only SONAR_TOKEN is secret and it is a build secret; the organization, project key and host are checked in. Ref #149

Replace the binary and reinstall the CLI. No migration.

Collaboration. A review is composed and submitted as one thing, a merge request can say it is not asking yet and can show what changed since you last looked, issues are searched by their text, and the events half the mutations never recorded now exist.

• A review is composed as a unit. mr diff-comment --pending holds a comment back; mr review publishes the batch with the verdict and says how many went with it; mr review --discard throws away what was never submitted. A pending comment notifies nobody when written — the review is the announcement, and it names its own size — and does not gate a merge, since a thread only its author can see is one nobody else could resolve. #111
• mr create --draft, mr draft, mr ready. A draft does not merge and does not appear in anyone's review queue; marking it ready is the request for review. Draft is a flag rather than a fifth state, so every state = 'open' rule still means what it did, and the merge refusal is unconditional: every other gate is a setting an admin turns on, and this one is the author's own statement about their own work. #111
• mr range-diff shows what changed between two revisions of a merge request, and mr revisions lists them. A push stales every review and nothing said what had moved; a diff of the two heads cannot answer it, and the previous head was overwritten in place. Each side of the comparison carries the merge base it had at the time, since measuring both against today's would attribute every commit that landed on the target in between to this merge request's author. #111
• Issues and merge requests are searched by their title and body, over FTS5. issue list --search and mr list --search narrow one repository; the instance-wide search reaches bodies now, and both list pages carry a search box. What someone types is quoted term by term, so an FTS5 operator — c++, AND, a lone quote — is a word to match rather than a syntax error. #114
• Ten mutations that changed a repository silently now record an event: mr.closed, mr.reviewed, mr.edited, mr.retargeted, mr.draft, issue.edited, issue.labeled, issue.assigned, issue.milestoned, mr.milestoned, release.deleted. mr close and issue edit also notify participants, which they did not. The full list is on the API wiki page and webhook add --events refuses a name that is not on it, since a subscription to a typo would never fire and nothing would say so. #112
• gitbay-runner -jobs N runs N builds at once. Claiming was always a single transaction that selects and updates, and each build already worked in its own directory, so several workers were safe the whole time; the runner never used more than one. #115
• A merge request replayed from a migration bundle has a diff. The bundle carried no head at all, and mr diff resolves through the head ref, so a merged merge request — which has no source branch left — could only fail. Re-running an import after the git push sets the head it could not set the first time. The GitHub import fetches refs/pull/*/head, which a mirror made with the default refspecs does not carry. #128
• The review loop is driven end to end by three accounts in the test suite: draft, ready, thread, approval, resolve, merge, with approvals, CODEOWNERS and require-resolved all on at once. Every one of those had its own test and none of them met. #139
• A bare go test ./... says the timeout is too short instead of panicking eleven minutes in and blaming whichever test was running. make test is what CONTRIBUTING asks for now. #143

Migrations 0036 through 0039 add the search index, the draft flag, pending review comments and merge request head history; 0036 and 0039 backfill from what is already there. They run on daemon start.

Two things this does not do. There is still no way to ask a particular person for a review — the queue is computed from involvement, so a collaborator with write access who has not touched a thread hears nothing (krz/gitbay#145). And a CI build still runs as the runner's own user with no container; the runner on this instance is scoped to one repository, which is what keeps that narrow (krz/gitbay#144). Both are v1.14.0.

The store and the push path. Dashboard queries walk an index instead of sorting the table, concurrent writers wait instead of failing, expired rows are swept, and a large first push no longer forks a process per commit.

• Every dashboard list scanned its table and sorted the result to take fifty rows. Reachability is correlated subqueries and cannot be indexed; the index supplies the ORDER BY instead, so the walk stops at LIMIT. On 20k issues and 20k merge requests: open issues 11.8ms to 0.8ms, open merge requests 12.1ms to 0.8ms, the review queue 15.5ms to 0.3ms, assigned issues 10.6ms to 0.04ms. The last of those also drives from issue_assignees rather than testing EXISTS against every issue. #137
• Concurrent writers serialise rather than failing. Every transaction in the store writes, and a deferred one takes the write lock at its first write, by which point another may hold it; SQLite answers SQLITE_BUSY and does not run the busy handler for that case, so busy_timeout could not help. Measured with eight concurrent read-then-write transactions, 44% of them failed. Beginning immediate takes the lock up front, where the timeout applies. #121
• repo settings updates no longer overwrite each other. settings_json is one blob, and every caller read it off a repository loaded earlier, changed a field and wrote it all back; two admins at once and the later write put back what it had read for the other's field. The read and the write happen together now, under one immediate transaction. #123
• Expired sessions and tokens are swept, and [retention] caps how long the audit log, the activity feed, webhook deliveries and the mail queue keep a row. Unset means forever, which is what every existing instance gets. #122
• The audit entry records flag names without their values. Secrets never reached argv — they travel on stdin — but prose did: --body <the whole issue> was stored verbatim, in a table nothing pruned, for a repository that may be private. Identifiers are positional and survive. #122
• pre-receive on a require-signed repository forked a cat-file per incoming commit and built one JSON message holding the whole push. A 50k-commit first push forked 50k processes and held the history in memory twice. One cat-file --batch serves the push now, and the daemon verifies each commit as it arrives. #100
• The payloads other surfaces decode are named types in control. httpd had its own copies of what the build, profile and dashboard commands emit, so a field added to a command was silently absent on the page. #126

Migration 0035 adds three indexes; it runs on daemon start.

Two changes in behaviour rather than configuration. A heavily contended write now blocks for up to busy_timeout (five seconds) instead of returning an error immediately — waiting is the point, but a caller that treated the error as normal will see a pause instead. And anything parsing audit --json for command arguments will find flag values gone; the flag names and the positional arguments are still there.

The web catches up with the rest of the forge: search across the instance, a notification inbox, a compare view, linkable diff lines, and a pass over contrast, heading structure and the stylesheet.

• Notifications are no longer mail or nothing. An inbox table holds a row per recipient whether or not the instance has SMTP; notifications list reads it, unread by default, and notifications read <id>... | --all clears it. repo watch adds you to a repository's notifications and repo unwatch mutes it, with a mute beating every other reason to be told, including owning the repository or having written the thread. The unread count rides on dashboard and in the web rail. #113
• search matches repository paths, descriptions and topics, and issue and merge request titles, across everything the caller can read; /search renders it with a field in the rail on every page, and an anonymous visitor gets the public rows from the same query. Titles only — body search is #114. #118
• /{owner}/{repo}/compare/{a}...{b} shows what one ref adds on top of another. Diff rows, files and review threads carry ids, so a line can be linked to. The issue and merge request lists page at fifty with the cursors the commands already emit. #118
• CODEOWNERS gating is a setting rather than a file that happens to exist: repo settings require-codeowners <owner/name> on|off, off by default, still independent of require-approvals. A repository can carry the file as documentation of who to ask without it gating merges. #142
• A failed form action's reason rides a one-shot cookie instead of ?e=<message>, so it no longer survives a reload or lands in history. #119
• A diff cut at 4 MiB cuts on a line boundary and says so, the diffstat says its counts are partial, and a merge request's commit list says "first 100 of N". #117
• Page templates parse once with the layout at start-up, so a template that does not parse fails the process rather than the first visit to its page. #116
• Markdown headings carry ids, matching org pages, and the stylesheet serves a hash ETag with a day's lifetime and answers a matching If-None-Match with 304. #132
• Dark-mode buttons carry a visible edge (a 1 px border was 1.3:1 against the 3:1 non-text contrast floor), and a stored label colour is held between 0.12 and 0.28 relative luminance so it clears 3:1 on both grounds while keeping its hue. #120
• Accessibility: the pin star is decoration and the word carries the meaning, the refs and release asset tables have scoped column headers, state filters carry aria-current rather than marking the active one by colour alone, and a rendered README or wiki page's headings move down one level so they sit under the page's own. #133
• The stylesheet drops rules no template reaches, folds two off-scale values onto the type scale, and resolves the classes templates asked for and it never defined. #131
• On a phone the tab bar wraps to a second row instead of scrolling sideways with its scrollbar hidden, and the landing page says in three sections what a reader, a writer and a reviewer can do. #134

Migration 0034 adds inbox and repo_watchers; it runs on daemon start. Reinstall the CLI for search, notifications and repo watch/unwatch.

Two upgrade notes beyond replacing the binary. A repository that relied on a CODEOWNERS file gating merges by its presence alone loses that gate until require-codeowners is set: nothing back-fills it, since the database cannot say which branches carry the file. And search and notifications are now reserved top-level routes, so a user or organization already holding either name keeps it but its profile page is shadowed by the route.

Every command parses its arguments the same way, the web answers by exit code, and a restart no longer waits on idle connections.

• One flag parser for every command: an unknown flag, a missing value or too many arguments is exit 2 with the command's usage, everywhere. mr review --approve --bogus used to report repository --bogus as not found. #96
• --json is honoured by the dispatcher's own refusals, so a script told no gets the envelope. #109
• A store failure is exit 1 and not-found is exit 3; both used to be usage errors. #107
• Web form actions answer by exit code: the 404 page for a thing that does not exist, the page with the message for anything else. #106
• Inside a clone, gitbay mr create takes the checked-out branch as --source; gitbay <noun> --help is the server's reference for the noun, flags included. #101 #130
• Shutdown closes idle SSH connections at once and drains only sessions mid-command; a store failure during key lookup no longer counts as a bad key against the auth limiter; the CLI says on ssh's exit 255 that a burst may have tripped it. #141
• A merge request head the target already contains is recorded as merged instead of refused; a fork is created with its parent in one insert; a failed transfer revert is reported; the repository quota is checked under a lock. #108
• Issues and merge requests share their comment, reference and author-or-write code. #110
• The payloads the web and clients decode are named types: Created, MRCreated, IssueShow, MRShow. JSON unchanged. #126
• Tests: parse failures per command, non-ASCII paths (which found ls-tree returning octal escapes, fixed with core.quotepath=off for every git the server runs), concurrent pushes. #129

Replace the binary and restart, and reinstall the CLI. No migration.

The runner is no longer an admin, the web no longer reaches around the registry, and the CLI stops paying a handshake per command.

• keys add --scope runner confines a key to runner next/log/done and read-only git; the runner commands accept that scope or an admin. The systemd drop-in sandboxes the runner process. gitbay.org's runner now polls as a non-admin ci account scoped to one repository. #92
• The web's repo create, issue create and edit, MR edit and both comment forms dispatch the command the CLI runs, so the repository quota, the archived-repository refusal, notifications, the body format and the audit entry hold from a browser. #93
• The CLI shares one SSH connection per instance (ControlMaster, five minutes idle): a command costs a round trip instead of a handshake, 0.4 s instead of 4 s from a distant laptop. no_multiplex = true on an instance opts out. #94
• A disabled account is refused on every surface, and disabling revokes its API tokens along with its sessions. #95
• CODEOWNERS gates whenever the file exists on the target branch, not only under require-approvals. #99
• The HTTP listeners have header and idle timeouts, and SIGTERM drains in-flight requests and SSH sessions before exit. #104 #105
• git archive runs under a two-minute deadline and a 512 MiB cap. #124
• Every git invocation ends option parsing before the ref, so a ref shaped like an option is a bad revision and never a flag. #135
• The admin noun is gated in the dispatcher as well as in each handler; registry tests cover that and ReadsStdin. #127
• An e2e test runs every ReadOnly command against a populated instance and fails on any row it changes. #97
• http.trusted_proxies attributes proxied API requests to the last untrusted X-Forwarded-For hop for rate limiting; email add is capped at five codes an hour per account. #136
• A merge request head is built in the target repository, at refs/merge-requests/<n>/head, so a fork's merge request has ci/<job> statuses for require-checks to gate on. A head from another repository is built without the target's secrets. #98
• Triggers refuse deleting a user or organization that still owns repositories, whatever path the delete takes. #136
• The stylesheet's fonts are served again, and directory crumbs on blob and blame pages link to the tree. #102 #103
• The Threat-Model wiki page covers the runner. #138

Replace the binary and restart, reinstall the CLI, and make deploy-runner: the runner fetches merge request refs before checkout. Migrations 0032 and 0033 run on start. The daemon host needs git 2.24 or newer for --end-of-options. Operators running gitbay-runner: give it a non-admin account with a key added by keys add --scope runner, remove the admin key it held, and make deploy-runner to install the sandboxed unit drop-in; an admin key keeps working meanwhile.

Markdown and org files render when opened.

• A .md, .markdown or .org file renders on its page the way a README does on the directory page, through the same renderer with relative links resolved against the file's directory. source in the action bar, or ?view=source, shows the text as before. Every other file is unchanged. #88
• The e2e harness waits for the HTTP and git listeners as well as SSH before a test starts; a test whose first act was an HTTP request could be refused, which failed two otherwise green runs. #91

Replace the binary and restart. No migration.

The tracker's lists narrow, labels have colours you set, and the CLI's help is the server's.

• issue list takes --label, --assignee, --author and --milestone (a title, or none for issues with no milestone); mr list takes --author and --milestone. The store narrows in SQL, and the web lists take the same names as query parameters and show each active filter with a link that drops it and keeps the rest. Both lists had taken --state and nothing else, so the web's filtering could never match the CLI's. #84
• label list shows a repository's labels with their colour and how many issues carry each; label set <label> [--color rrggbb|''] creates a label or sets its colour; label remove takes it off every issue. The colour column had existed since labels did and nothing wrote it. The hash is optional because over bare ssh a bare # starts a comment for the tokenizer. issue label --add still creates a colourless label on the fly. #85
• gitbay help with a prefix or --json runs the server's help, the only place flags are written down and whose JSON is the contract; bare gitbay help is still the local tree. Cobra's built-in help had owned the word, so gitbay help --json failed on an unknown flag. #86

Replace the binary and restart, and reinstall the CLI for the help change. No migration.

What an open instance needs before it is open: a cap on what one account can take, a way out of a browser session you no longer hold, and accounts that never verified do not stay forever.

• limits.max_repos_per_user caps the repositories an account owns directly; repo create, fork and import refuse past it with the numbers. limits.max_bytes_per_user caps their disk: a push may be no larger than what the owner has left, riding the same receive.maxInputSize as the pack cap, and is refused outright when nothing is left. Organizations are not capped. Migration 0031 adds per-account overrides, set with admin user limits <name> [--repos n|default] [--bytes n|default] and shown by admin user show. Both default to 0, unlimited, so nothing changes until set. #82
• registration.pending_expiry, a duration, removes self-registered accounts still unverified after that long, hourly and once at start, audited as pending.expired. Empty keeps them, as before. #82
• web sessions list shows each unexpired browser session by a short id with its creation and expiry; web sessions revoke <id> ends one and --all ends every one. SSH-only, matching the token commands, and scoped to the caller. #83
• A step runs in its own process group and a cancel or timeout kills the group. On a host whose /bin/sh is dash, killing the shell alone left its child holding the log pipe, so a cancelled build held the runner until the child finished on its own, minutes for a test suite. The wait after a kill is capped at ten seconds besides.
• A commit with a build still queued or running is not queued again when a fast-forward lands it; the v1.6.0 skip counted only a finished success. #90
• golang.org/x/crypto v0.56.0: GO-2026-6354 and GO-2026-6355 in its ssh package, both reached through ssh.NewServerConn in the embedded SSH server; one is a denial of service on a deadlocked undecided channel.

Replace both binaries and restart: make deploy for the daemon (migration 0031 adds two columns to users on start), then make deploy-runner for the process-group kill.

A cancel reaches a build in its clone.

• The runner honoured a cancel only in its step loop; a build cancelled during its clone or checkout ran git to completion first, which on a loaded host was long enough for the v1.6.0 test to fail on the CI host while passing locally. One runStep now drives the clone, the checkout and each step with the cancel signal and the deadline, and checks the signal before starting at all. The runner logs how its log session ended when that was not a cancel.

Replace the runner: make deploy-runner. The daemon is unchanged from v1.6.0.

The v1.4.0 admin surface answered questions about accounts. This one answers questions about the machinery: which runner is alive, what is stuck, whether last night's backup exists, and it lets an operator stop a build instead of waiting it out.

• A build a runner claimed and never reported is failed by the scheduler's minute tick, with no runner involved. It used to happen only when some runner polled again, so a dead sole runner left its builds running forever. GITBAY_STALE_BUILD_DEADLINE shortens the deadline for tests. #75
• Runners are visible. Migration 0030 adds runner_seen: one row per runner account with its last poll, the -repos scope it asked for, and the build it holds. admin runners lists them, over SSH and on the host. #76
• GET /healthz: whether the database answers and which commit serves, no auth, no repository data, 503 when the database does not answer. healthz joins the reserved names. #77
• The host monitor's hourly reading carries the age of the newest full backup and database snapshot, alerting at 25 and 2 hours, and the daemon's own /healthz answer read through site_url. Both ride the journald line and the webhook body. #78
• admin stats reports lfs_bytes. admin gc --lfs scans every repository's objects for LFS pointers and removes stored objects none names, keeping anything younger than a day since git lfs uploads before it pushes. #79
• admin backup --verify <archive> reads an archive back: SQLite's integrity check on the snapshot, and the repositories it names against the archive's. A database-only archive says so. Damage or a missing repository exits non-zero. #80
• A commit that already passed a job on another branch is not built again when a fast-forward lands it. Merging the six-layer v1.6.0 stack had queued eighteen jobs for commits that had each just gone green. Failed or abandoned builds still re-queue. #90
• build cancel <owner/name> <n> withdraws a queued build or ends a running one. For a running build the server closes the runner's log session, the runner kills the step within seconds, and its late report changes nothing. The commit status goes back to the passed result from another build of the same commit when one exists, else reads cancelled. Needs write access.
• Deploys copy with rsync --partial, so a transfer the host's load stalled resumes, and make deploy-runner installs a systemd drop-in (Nice=10, CPUWeight=30, IOWeight=30) so a build never starves the host's sshd again.

Replace both binaries and restart: make deploy for the daemon, then make deploy-runner for the runner, which carries its half of running- build cancellation and installs the drop-in. Migration 0030 adds the runner_seen table on start. The monitor change ships in deploy/cloud-init.yaml; an existing host takes it by hand.

Merge requests stack.

• A merge request whose target is the source branch of another open merge request in the same repository is stacked on it. Nothing is stored and no flag exists; the forge reads the stack from the branches. mr create says stacked on !A when it applies, mr show carries stacked_on and stacked, mr list rows carry stacked_on, and the page says both directions in the header. #87
• When the lower merge request merges, everything stacked on it is retargeted onto what it merged into, with a system comment naming the merge and its reviews kept: after a fast-forward or merge commit the diff against the new target is the diff they were of. A squash or rebase merge under a stack is refused, naming the stack, since it would rewrite the commits the stack builds on.
• The first stack merged on gitbay.org was the six merge requests of v1.6.0, bottom-up, with no mr retarget typed. The wiki's Stacked-MRs page walks through it.

Replace the binary and restart. No migration.

Until now the instance had one operator surface: root on the host. Every question about the instance itself — who is on it, what is stuck, what a spam repository is doing — needed a shell on port 2222. This release gives an instance admin the same answers over SSH, and one page on the web.

• admin user list pages accounts by username with --state active|pending|disabled|admin, each row carrying its state and last_seen, the newest use of any of its SSH keys or API tokens. admin user show <name> adds the keys with their last use, each address with how it was verified, PGP keys, org roles, owned repository count, API token names and live browser sessions. Both are SSH-only and refused to non-admins, like audit. #69
• admin user promote|demote. The only way to admin was admin user create --admin; an existing account could not be raised and an admin could not step down. Demoting the last admin is refused inside the transaction that counts them. The host-local twin is the recovery path when no admin key is reachable. #70
• Repository overrides for moderation: admin repo list with size and last push, and admin repo archive|unarchive|visibility|delete. Policy still knows nothing about instance admin — a private repository answers not-found to an admin as before — so each override skips the access check explicitly and writes its own admin repo.<action> audit row. #71
• gitbayd admin dispatches into the registry. User create, disable, enable and delete, email verify, invite and stats were reimplemented on the host; they now live in the registry, SSH-only and admin-gated, and the host binary runs them as the host — an admin context with no account behind it, so its audit rows say source: host where a session says the key fingerprint. Invite and stats gain an SSH twin by the same move. backup, gc and the backfills stay host-local. #72
• audit filters: --actor <user> or --actor - for actorless rows, --action <prefix>, and --since as a duration (30m, 24h, 7d) or a date. gitbayd admin audit takes the same flags and --json. #73
• dashboard carries a queues block for admins: per worker — webhooks, mail, mirrors, builds, dependency checks — the pending, retrying and dead-lettered counts, the oldest pending age, and the retrying or failed rows themselves, capped at twenty each. The mail queue was readable nowhere before. /admin renders the block by dispatching dashboard; non-admins get a 404 and no rail link. #74
• gitbayd admin config show prints the configuration in effect as TOML, defaults filled in and smtp_pass redacted, so a support question starts from what runs rather than what was written. #81
• Build badges are served as PNG at badge/build.png as well as SVG, for places that will not render SVG.
• Host monitoring writes its reading to journald on every run and exits non-zero on an alert, so an unset webhook no longer looks like a healthy host; it reads the ACME cache where it actually lives and reports the soonest expiry. govulncheck runs as its own CI job. The database is snapshotted hourly by gitbay-db-backup.timer, keeping 48, alongside the nightly full archive; archives inherit the database's mode rather than the umask default. #28
• A runner whose log stream drops no longer fails the build it was recording. #67
• go.yaml.in/yaml/v3 and golang.org/x/net bumped. #60

Replace the binary and restart. No migration. The gitbay-db-backup timer and the monitor changes ship in deploy/cloud-init.yaml for new hosts; an existing host takes them from there by hand.

A runner took every repository's work, which decided where you could run one.

• runner next takes optional owner/name arguments and gitbay-runner takes -repos, so a runner claims builds only for the repositories it names. Naming none is the old behaviour, so an existing runner is unaffected. This is what makes a runner outside the server practical: one on a machine that should build a single project no longer picks up a build belonging to someone else, which with open registration need not be anyone the operator knows. The scoping is what the runner asks for rather than an ACL the server holds over it — a runner account is admin by necessity, so the boundary is the operator choosing how to start it. #66

Replace the binary and restart. Runners want the new binary too, though an old one keeps working unscoped.

Merging landed commits without running anything.

• A merge moves the target ref with a direct ref update, so it never reached post-receive and none of the ref-update work fired: no push event for webhooks to subscribe to, and no builds. Pushing a commit to a branch ran the whole .gitbay/ci.yml; merging the identical commit ran nothing. Both now happen in the merge path, with the build queueing shared between it and post-receive rather than living in one of them. #65

Replace the binary and restart.

A merge request said what its state was and almost nothing about when it got there. It now keeps time.

• Reviews and checks carry the moment they last said something, on the merge request page and in mr show. A ci/<job> check also reports how long its build ran, so the timing of a run is readable without opening it. Checks posted through status set have no build and report only the time. !137
• A merged or closed merge request names who resolved it and when. The header stated "X wants to merge" whatever the state; it now says "X merged A into main on <date>", or "closed this without merging", and drops the claim entirely for a row that carries no stamp rather than inventing a time.
• mr show gains merged_at=/=merged_by and closed_at=/=closed_by, a created_at per review, and updated_at plus duration per check, in both JSON and text. Additive: nothing existing changed shape.
• The iOS client renders all of it as of krz/gitbay-ios!37.

Replace the binary and restart. Migration 0029 adds four columns to merge_requests and backfills the merge stamp for merge requests already merged, reading the mr.merged events. A merge with no such event to read — an import, or a row older than its events — keeps no stamp, and every surface says nothing about when it happened rather than guessing.

Every release until now answered questions. This one notices something on its own: that a repository's dependencies have moved, and says so without being asked.

• Dependency update checks, opt-in per repository. A daemon worker reads the manifests on the default branch, asks the ecosystem's registry what the current release is, and maintains one issue per repository — opened when something falls behind, rewritten when the set changes, closed once nothing is behind. No package manager runs, so it needs no CI runner and no configuration beyond turning it on. #58

  • go.mod against proxy.golang.org, package.json with package-lock.json against npm, Cargo.toml with Cargo.lock against crates.io, requirements.txt and pyproject.toml against PyPI. A lockfile wins where both exist. A requirement naming a set rather than a release — a range, a wildcard, a git or path source — is skipped, since a range that already admits the newest release is not news.
  • repo deps enable|disable|status, a toggle on the repository settings page, and the same three over the JSON API.
  • Off by default, because checking a private repository tells a public registry what it depends on. That is the owner's disclosure to make. [deps] check_interval_hours sets the cadence, default 24.
  • The issue is authored by a gitbay-bot account, so the existing notification mail reaches the repository's owner rather than excluding them as the actor. Its table is padded to its columns, which a renderer ignores and a mail client needs. #61
• help takes a prefix — help mr narrows the registry to one noun — and every command now documents its arguments, so the server answers "what are the flags" instead of being guessed at. #57
• Web: settings rows end in one column of controls, checkboxes drawn at the height of the inputs and buttons they sit beside #59; an added line keeps its leading dash in the diff; a contributor's several verified addresses collapse to one row #56.

Replace the binary and restart. Migration 0028 adds two tables and, when the name is free, the gitbay-bot account. An instance already using that name for a user or an org keeps what it has: the account is not created, and dependency checks report that as the reason they cannot open an issue rather than the migration failing and the daemon not starting. #64

Two CI fixes found by running orgo's release pipeline on this instance.

• A runner killed between claiming a build and reporting it left the build running forever, and the commit's ci/<job> status pending with it. runner next now fails builds past a 90-minute deadline — longer than the runner's own -timeout — and resolves their commit status. #53
• gitbay keys add and gitbay repo deploy-key add take stdin as a bare < key.pub, but only forwarded it when --file - appeared in the arguments, so both sent an empty body and rejected input the SSH API accepts. #55

Replace the binary and restart.

The web finishes the job #35 set it: reading, reviewing and responding, with the CLI still the complete interface. Every capability exists over SSH, every web write dispatches the same control command, and anything whose input is a credential stays on the command line. The Parity page in the wiki is the maintained matrix and says which rows are deliberately CLI-only.

• Diff view: one foldable section per file with line-number gutters, per-file stats, rename and binary handling, and syntax highlighting run per hunk per side so multi-line constructs lex as real code. Commit and merge request pages share it; review threads anchor inline.
• Repository facts on the code page: commit, branch and tag counts, detected license, latest release, build status, a language census by tracked bytes, and contributors resolved to accounts by verified email. All derived from git at render time.
• Account settings on the web: SSH keys with scope, OpenPGP keys, and email addresses. Public keys are the only credential-shaped input the web accepts — they are not secret, and a new user needs one registered before the CLI is reachable to them. Token minting and account export stay SSH-only.
• Organizations are run from their page: membership and roles, teams, team members, and team repository grants, for org admins.
• Commit log shows each commit's combined check status and gains a path filter, so per-file history is reachable without editing the URL.
• Issue references from commit messages read "referenced in commit <sha> by <author>", linking the author when their email is verified here.
• The rail's focus ring uses the shell's own mark: the light scheme's accent was a dark blue ring on a black rail.

No migrations. No new config.

Upgrading from v0.5.0 is replace-the-binary-and-restart.

A design pass and a parity pass. The web stops being a read-only mirror of the CLI without becoming the place you are expected to work.

• New design: a black shell with a persistent left rail carrying cross-repo state (pinned repos, review queue), the repo header rendered identically on every tab so navigation never moves, sharp lines, self-hosted IBM Plex, and code blocks that read against both color schemes. Tree listings sort directories first and carry each file's last commit; diffs, inputs and controls were reworked to match.

• Web parity with the CLI, dispatched through the same command registry the CLI and JSON API use — every web write is the equivalent gitbay command with --source web:

  • merge requests: review, resolve threads, merge, close, and open a new MR from the browser
  • issues: state, labels, assignees, milestones
  • repositories: settings, branch protection, visibility
  • releases: create and edit; builds: trigger a job

  Commands marked SSH-only still refuse over the web: build secrets, mirror tokens, domain claims, token minting, deletion and transfer.

• A dashboard that answers "what needs me": review queue, assigned issues, pinned repos, and an activity feed. Author names resolve to accounts and link to profiles wherever commits appear.
• Build status badges at /{owner}/{repo}/badge/build.svg for public repos.
• [web] title sets the instance's display name, separate from the hostname commands are pasted with.
• make build/test/deploy targets.
• Fixes: the mobile tab strip scrolls sideways only, long commit subjects no longer overflow on narrow screens, the shell fills the viewport with the line-length cap moved onto prose, and the account cell lines up with the page footer.

No migrations. New config: [web] title.

• Git LFS: standard clients work over both transports. git-lfs-authenticate joins the SSH dispatcher (deploy keys included; download needs read, upload write), minting stateless repo- and operation-scoped tokens for the batch API and basic transfers. Anonymous HTTPS downloads for public repos; uploads verified against size and sha256 before landing. Storage is content-addressed under [lfs] root behind a small interface an S3-compatible backend can drop into; [lfs] max_object_bytes caps objects (512MB default).
• Build failures mail the repo's notify targets with the log tail and build link — failed scheduled jobs reach an inbox.
• release edit updates a release's title and notes (absent flags keep their field); omaha-style CI note rebuilds work again.
• Syntax highlighting follows the color scheme: class-based chroma with light and dark palettes, the light-pinned code background is gone, and markdown fences and org src blocks highlight too. The UGC sanitizer admits only chroma's token-code classes.

No migrations. New config: [lfs] root, [lfs] max_object_bytes.

• CI: .gitbay/ci.yml jobs run as builds claimed by gitbay-runner over SSH (admin-only runner protocol; statuses feed require-checks). Per-repo secrets set over stdin and injected into build environments; cron schedules (server-local time) and tag-glob triggers, mutually exclusive per job; build list/show/log/trigger and a builds tab.
• Pages: public repos' pages branches served on <owner>.<domain> ([pages] domain), custom domains with DNS TXT ownership challenges and 7-day expiry for pending claims, per-subdomain on-demand ACME.
• Wikis (.wiki companion repos, access mirrors the parent) and teams within orgs (members-role scoping, per-repo team grants).
• Activity graphs on user and org pages, backfillable (admin backfill-activity); commits attributed by verified author email, deduped by sha.
• MR pages list the commits the MR carries; mr show gains a commits section.
• Per-file history: ?path= on the web log, --path on repo log, history link on blob pages.
• Mirror status surfaced in repo show and the repo header (admin-only), with sync errors visible; tag-only pushes now schedule mirror syncs.
• Rendering: GFM tables/strikethrough/autolinks/task lists, blob image previews, raw serves images with real content types (README images render under nosniff), 0BSD license recognition, repo website links, compact dashboard pins.
• admin user delete for accounts that anchor nothing, with named blockers otherwise.
• Fixes: wiki pages no longer overflow on mobile (iOS font-inflation trigger), GHSA-free deps, secret values pipe correctly through the CLI.

Migrations 0020-0025 apply on start. New config: [pages] domain. The runner is a new binary (gitbay-runner); see the wiki's Admin guide for setup. Stress-tested against an import of git.git (82k commits): see the wiki's Performance page.

• Deploy keys: repo-bound CI keys (repo deploy-key), ro/rw, rename- and transfer-proof.
• Commit statuses (status set/list), combined state on MR pages, and a require-checks merge gate.
• Email notifications for issue and MR activity (participants with verified addresses; never the actor).
• Inline review threads on MR diffs (mr diff-comment/threads/resolve), stale on force-push, require-resolved merge gate.
• Required approvals with CODEOWNERS (require-approvals; latest review wins, author excluded) and a require-resolved gate; merge gate order is checks → approvals → CODEOWNERS → resolved threads → signatures.
• Web design revamp: token-based stylesheet (light+dark), wordmark and favicon, aligned layout grid, card-based listings, designed 404, mobile pass.
• Cross-references and mentions: #N, !N, owner/name#N, @user autolink in issue/MR text, viewer-aware for private repos.
• Archived repositories (read-only with badge) and repo topics.
• Blame view with signature-aware attribution and 1000-line pages.
• Repository search (name/description/topic) and per-repo code search (repo grep, web search tab); blob line anchors.
• Homepage: dashboard for logged-in users (pinned repos via repo pin, open MRs and issues involving you), landing page for visitors, full public listing at /explore; MR diffs collapsed by default.
• Milestones (milestone create/list/close, issue/mr milestone) with web progress; issue templates from .gitbay/issue-template*.md (CLI $EDITOR prefill and web form).
• Issue actions from commit messages landing on the default branch: closes/fixes/resolves #N closes, bare #N leaves a reference comment; once per issue+commit.
• Vanity Go imports: [go_import] config serves go-import meta tags, so go install gitbay.org/gitbay/cmd/...@latest works.
• Release script: deploy/release.sh <tag> builds reproducible linux/amd64, linux/arm64, and darwin/arm64 binaries with SHA256SUMS.
• Repository maintenance: admin gc (repack/prune, per-repo sizes), admin stats (counts + disk usage), weekly gitbay-gc.timer.
• Releases: tag-anchored notes and binary assets (release commands, assets over SSH stdin/stdout, web releases tab with downloads).
• GitHub history import: repo import-issues brings issues and PRs (as merged/closed MRs) with comments, labels, and state, attributed inline and resumable.
• Push and pull mirroring (repo mirror): background sync, read-only pull mirrors, per-mirror status; credentials server-side, SSRF-guarded.
• Web signup at /register for open and invite instances.
• Audit log (audit, gitbayd admin audit): every mutating command with source key fingerprint, registrations, force-pushes, auth failures. Hardening: per-IP auth-failure throttling (ssh_auth_rate), max_pack_bytes enforced, admin user disable/enable.
• Account migration: gitbay migrate --from <host> (bundle export/replay + client-side git mirror); gitbay auth export as a user-level backup.
• Editable issues and MRs (issue edit, mr edit, web forms).
• Commit references appear as system messages with linked shas.
• Design: top nav, repo listing rows (topics, license, last updated), file table headers, README relative-link resolution, branch dropdown, web pinning, org owner picker, label filters, linked usernames and commit parents, /privacy page, blue accent.

Upgrade notes: migrations 0006–0019 apply on start. No config changes required; [go_import], [mirrors], web.privacy_notice, and web.mode = "accounts" are opt-in.

First tagged release: the complete CLI-first forge. SSH control plane (bare-OpenSSH usable), git over SSH/HTTPS/git-daemon, repos, issues, merge requests (ff/merge/squash/rebase with signature policy), OpenPGP and SSHSIG verification with retroactive re-verification, orgs, repo import, web UI (view-only or accounts mode), registration with invites and SMTP, HTTPS/JSON API with SSH-minted tokens, webhooks, backups, ACME TLS, systemd deployment.