CHANGELOG.org

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.