<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://nesbitt.io/feed/by_tag/twisc.xml" rel="self" type="application/atom+xml" /><link href="https://nesbitt.io/" rel="alternate" type="text/html" /><updated>2026-11-22T18:32:53+00:00</updated><id>https://nesbitt.io/feed/by_tag/twisc.xml</id><title type="html">Andrew Nesbitt</title><subtitle>Package management and open source metadata expert. Building Ecosyste.ms, open datasets and tools for critical open source infrastructure.</subtitle><author><name>Andrew Nesbitt</name><email>andrew@ecosyste.ms</email></author><entry><title type="html">This Week in Source Control: 18 November 2026</title><link href="https://nesbitt.io/2026/11/18/this-week-in-source-control.html" rel="alternate" type="text/html" title="This Week in Source Control: 18 November 2026" /><published>2026-11-18T10:00:00+00:00</published><updated>2026-11-18T10:00:00+00:00</updated><id>https://nesbitt.io/2026/11/18/this-week-in-source-control</id><content type="html" xml:base="https://nesbitt.io/2026/11/18/this-week-in-source-control.html"><![CDATA[<p>This week’s version control and forge news, gathered from release feeds for source control clients and forges, the <a href="https://lobste.rs/t/vcs">Lobsters vcs tag</a>, Hacker News, and my boosts on <a href="https://mastodon.social/@andrewnez">Mastodon</a>. Package management news is in the Saturday <a href="/2026/11/14/this-week-in-package-management.html">This Week in Package Management</a> roundup.</p>

<h2 id="releases">Releases</h2>

<p><a href="https://www.gerritcodereview.com/3.15.html">Gerrit 3.15.0</a> declares Git’s reftable ref storage ready for production after load testing and fixes to the remaining stability and conversion bugs. Administrators can convert a repository between the files and reftable formats from the project screen, as long as the repository receives no writes during the conversion.</p>

<p>A new <code class="language-plaintext highlighter-rouge">POST /projects/{project-name}/branches/{branch-id}/commit</code> REST endpoint creates, updates, deletes or renames files on a branch in one commit, with no clone and no change. The caller needs Push access on the branch. An optional <code class="language-plaintext highlighter-rouge">base_revision</code> makes the request fail with 409 Conflict if the branch has moved.</p>

<p>Comments and votes can now be marked as AI-generated through an <code class="language-plaintext highlighter-rouge">is_ai</code> field, and the UI shows an icon next to them. The <code class="language-plaintext highlighter-rouge">aiReview</code> permission moves to a default-deny ACL. An experimental Stack Diff dialog shows the combined diff of a whole relation chain against its base. Gerrit is now built with JDK 25 and Bazel 9, and plugins that declare dependencies in <code class="language-plaintext highlighter-rouge">external_plugin_deps.bzl</code> have to move to Bazel modules.</p>

<p><a href="https://github.com/gitbutlerapp/gitbutler/releases/tag/release%2F0.23.4">GitButler 0.23.4</a> narrows its warning for repositories using Git LFS or git-crypt to editing and resolving commits. Auto-merge now works in GitHub repositories that only allow squash or rebase merges. New installs open the native app by default. In that app, a plain <code class="language-plaintext highlighter-rouge">git commit</code> on <code class="language-plaintext highlighter-rouge">gitbutler/workspace</code> no longer breaks the project, and the app offers to uncommit it and keep the changes.</p>

<p>Also out: Gerrit <a href="https://www.gerritcodereview.com/3.14.html#3146">3.14.6</a>, <a href="https://www.gerritcodereview.com/3.13.html#31311">3.13.11</a> and <a href="https://www.gerritcodereview.com/3.12.html#31212">3.12.12</a>.</p>

<h2 id="security">Security</h2>

<p><a href="https://blog.gitea.com/release-of-28.4.0/">Gitea 28.4.0</a> lists 21 CVEs, including one in Go’s <code class="language-plaintext highlighter-rouge">net/http</code> fixed by building with Go 1.27.4 and two already fixed in earlier 28.x releases. Among them:</p>

<ul>
  <li>CVE-2026-125423: a repository created with auto-init accepted pushes before initialisation had finished. A user allowed to create repositories could push a crafted tree so that writing the README followed a symlink and overwrote a server-side git hook, which ran commands as the Gitea system user.</li>
  <li>CVE-2026-123006: since 28.0.0 the dashboard’s repository search returned each repository’s commit status object with the owner’s full user record. Any signed-in user could read the password hash, salt and email address of the owner of any visible repository with a commit status.</li>
  <li>CVE-2026-123638: protected file patterns were matched against file names as git prints them. Git quotes names containing a double quote, backslash or control character, so those names matched no pattern and a user with write access could change files under a protected path.</li>
  <li>CVE-2026-118535: a repository registered as an owner-level source of scoped workflows kept that registration after a transfer. The new owner could change workflows that still ran in the previous owner’s repositories with their Actions secrets.</li>
  <li>CVE-2026-129337: a repository still being created by a migration, fork or template has no server-side hooks, so a user with read access could push to it over HTTP during that window.</li>
  <li>CVE-2026-123002: Gitea accepted unlimited wrong TOTP passcodes. Five failures now block further attempts on the account for 15 minutes.</li>
</ul>

<p><a href="https://github.com/desktop/desktop/releases/tag/release-3.6.11">GitHub Desktop 3.6.11</a> updates its bundled Git to 2.56.1, the release that fixed the six vulnerabilities covered <a href="/2026/11/11/this-week-in-source-control.html">last week</a>.</p>

<h2 id="github">GitHub</h2>

<p><a href="https://github.blog/changelog/2026-11-11-issue-types-and-fields-are-available-for-personal-accounts">Issue types and issue fields</a> are generally available on repositories owned by personal accounts. Each account can define up to 25 types and 25 fields under Planning in its settings, and both are exposed through the REST and GraphQL APIs and webhooks. Labels and milestones can now also be created from the issue page when a search finds no match.</p>

<p>The <a href="https://github.blog/changelog/2026-11-10-a-more-informative-github-dashboard">dashboard is more compact</a> after feedback that the new default layout showed too little. Pull request and issue lists show six items by default instead of three, long titles stay on one line, and either the Feed or Home tab can be pinned as the default view. The agent sessions section is hidden for accounts with no agent sessions.</p>

<p><a href="https://github.blog/changelog/2026-11-17-github-event-streams-is-now-in-preview">Event Streams</a>, in preview behind a waitlist on all plans, lets a client subscribe to a pull request and keep a connection open. GitHub then sends an event when a review is submitted, commits are pushed, a merge conflict appears, a check suite changes status, or the pull request is merged or closed. Events arrive over the connection the client opened, in place of a public webhook endpoint, and the changelog presents it as a replacement for agents polling the API from a laptop.</p>

<p>Secret scanning has a <a href="https://github.blog/changelog/2026-11-12-secret-scanning-adds-a-detector-for-cloudflare">new detector for Cloudflare service tokens</a>, listed as <code class="language-plaintext highlighter-rouge">cloudflare_access_service_token</code>. Partner secrets found in public repositories are reported to the issuer, and user secrets raise alerts in public and private repositories.</p>

<h2 id="elsewhere">Elsewhere</h2>

<p><a href="https://lwn.net/SubscriberLink/1104195/1193ea577aaef643/">Git considers voting to determine its LLM policy</a> (Jonathan Corbet, LWN) reports on a draft voting process that Emily Shaffer posted to the Git list on 21 October. Git’s contribution guidelines have said since October 2025 that anything that looks AI-generated will be rejected. A session at the Git Contributor’s Summit revisited that policy and reached no consensus.</p>

<p>Under the draft, proposals are patches to the project’s documentation and need a second from another eligible voter. Discussion runs for around four weeks, followed by a two-week vote. The draft gives a vote to anyone with a commit merged to <code class="language-plaintext highlighter-rouge">next</code> or two code reviews. Patrick Steinhardt suggested a threshold of 25 or 30 commits. The counting method is undecided, and Steinhardt and brian m. carlson both asked for a secret ballot.</p>

<p><a href="https://yorickpeterse.com/articles/migrating-from-github-to-codeberg/">Migrating from GitHub to Codeberg</a> (Yorick Peterse) covers moving Inko and a set of personal repositories by hand with Forgejo’s repository migration feature. The GitHub importer stalled for about an hour at rate limits without reporting it, and it does not map users, so assignees had to be set again. GitHub issue types have no Forgejo equivalent and became labels.</p>

<p>CI moved to Forgejo Actions on self-hosted runners, because Codeberg’s shared runners are AMD64 Linux only and time-limited. Peterse reports that a <code class="language-plaintext highlighter-rouge">git push</code> typically takes between 5 and 10 seconds, and that a request to raise the Inko organisation’s 1.5 GiB quota was unanswered at the time of writing.</p>

<p><a href="https://social.anoxinon.de/@Codeberg/117636454915265360">Codeberg reported</a> on the morning of 18 November that codeberg.org was unreachable. The site is unavailable at the time of writing and the issue is ongoing. Codeberg said the domain had not expired or been transferred, but was missing from its registrar account and in <code class="language-plaintext highlighter-rouge">clientHold</code> status, and that no email notification had arrived. A <a href="https://social.anoxinon.de/@Codeberg/117636553104473348">follow-up</a> said no warning had arrived under the registrar’s abuse reporting procedures and that a technical issue was the most likely cause.</p>

<p><a href="https://entropicthoughts.com/stacked-diffs-with-maiao">Stacked diffs with Maiao</a> (kqr, Entropic Thoughts) describes keeping one commit per change on a single <code class="language-plaintext highlighter-rouge">dev</code> branch and publishing it to GitHub with the <a href="https://github.com/runetes/maiao">community fork of Maiao</a>. One <code class="language-plaintext highlighter-rouge">git review</code> command fetches upstream, rebases the branch, pushes a disposable branch for each commit, and opens a pull request for each as a native GitHub stack. Running it again after amending a commit force-pushes the branches and updates the pull request descriptions and merge targets.</p>

<p><a href="https://blog.hofstede.it/git-beyond-the-basics-worktrees-cherry-picks-and-signed-commits/">Git Beyond the Basics</a> (Christian Hofstede-Kuhn) is a long tutorial for people who already use add, commit and push, checked against Git 2.56.1. It covers a starting configuration, rerere, the reflog, fixup commits with autosquash, <code class="language-plaintext highlighter-rouge">--update-refs</code> for stacked branches, and what worktrees share.</p>

<p>In the signing section’s tests, a plain <code class="language-plaintext highlighter-rouge">git rebase</code> or <code class="language-plaintext highlighter-rouge">git cherry-pick</code> of a signed commit dropped the signature from the copy, and Forgejo’s “require signed commits” branch protection rejects the result. Passing <code class="language-plaintext highlighter-rouge">-S</code> or setting <code class="language-plaintext highlighter-rouge">commit.gpgsign</code> signs the new commits. Hofstede-Kuhn’s own signatures come from an OpenPGP smartcard through <code class="language-plaintext highlighter-rouge">oct-git</code> in place of GnuPG.</p>

<p><a href="https://tangled.org/nvim-mini.org/mini.nvim">mini.nvim</a>, the library of Neovim modules, now has mirrors on Tangled and <a href="https://codeberg.org/nvim-mini/mini.nvim">Codeberg</a>. Its README lists the GitHub repository as the main one.</p>

<p><a href="https://rbit.sh/GitRbit/rbit">rbit</a> is a self-hosted Git forge written in Rust that runs as one binary with SQLite, redb and bare Git repositories in a single data directory. It reads repositories in-process with gitoxide and serves Git over smart HTTP and a built-in SSH server that offers no shell. The feature list covers issues, pull requests, reviews, Git LFS, mirrors, and imports from GitHub and Gitea. Actions jobs run on a separate <code class="language-plaintext highlighter-rouge">rbit-runner</code>.</p>

<p>GitHub processed four DMCA notices from Nintendo dated 6 November, <a href="https://www.ign.com/articles/nintendo-takes-down-switch-emulators-and-mod-chip-firmware-in-massive-github-dmca-sweep">IGN reports</a> (Jacqueline Thomas). They target the Switch emulators Yuzu and Citron Neo and firmware for mod chips. Because the firmware’s fork network was larger than 100 repositories, GitHub applied <a href="https://github.com/github/dmca/blob/master/2026/11/2026-11-06-nintendo-2.md">one notice</a> to all 144 repositories in it.</p>

<p>Send links for next week to <a href="https://mastodon.social/@andrewnez">@andrewnez@mastodon.social</a>.</p>]]></content><author><name>Andrew Nesbitt</name><email>andrew@ecosyste.ms</email></author><category term="git" /><category term="weekly" /><category term="twisc" /><summary type="html"><![CDATA[Releases, advisories, and articles from across version control and forges]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://nesbitt.io/images/boxes.png" /><media:content medium="image" url="https://nesbitt.io/images/boxes.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">This Week in Source Control: 11 November 2026</title><link href="https://nesbitt.io/2026/11/11/this-week-in-source-control.html" rel="alternate" type="text/html" title="This Week in Source Control: 11 November 2026" /><published>2026-11-11T10:00:00+00:00</published><updated>2026-11-11T10:00:00+00:00</updated><id>https://nesbitt.io/2026/11/11/this-week-in-source-control</id><content type="html" xml:base="https://nesbitt.io/2026/11/11/this-week-in-source-control.html"><![CDATA[<p>This week’s version control and forge news, gathered from release feeds for source control clients and forges, the <a href="https://lobste.rs/t/vcs">Lobsters vcs tag</a>, Hacker News, and my boosts on <a href="https://mastodon.social/@andrewnez">Mastodon</a>. Package management news is in the Saturday <a href="/2026/11/07/this-week-in-package-management.html">This Week in Package Management</a> roundup.</p>

<h2 id="scaling">Scaling</h2>

<p><a href="https://github.blog/engineering/architecture-optimization/inside-githubs-new-git-storage-architecture/">Inside GitHub’s new Git storage architecture</a> (Karthik Raman and Brian Celenza, GitHub) describes Rubicon, the design announced at GitHub Universe. Packs go to Azure Blob Storage. References and the list of packs are stored in Ref-CAS, a replicated log service where each reference update is a compare-and-swap committed by a quorum, so a push waits only on other pushes to the same reference. In internal tests one repository accepted 7,200 pushes per second from 5,000 concurrent agents.</p>

<p>Requests still arrive at Spokes, which routes each one to a small group of virtual replicas, disposable compute nodes whose local disk is a cache. A replica handling a write indexes the pack, uploads it to Blob Storage, then commits one Ref-CAS transaction. For reads it sends the version in its cache, and the reply includes references only if they have changed since that version.</p>

<p>Two earlier prototypes stored reference state in blobs. The first, a write-ahead log indexed by a single blob, reached a limit of writes in the mid-hundreds per second. Hashing references across several segment blobs raised the write limit, but every read then had to check every segment.</p>

<p>Compaction runs on separate nodes that lease a shard of the repository’s packs and merge them into larger ones. Each node checks that the new packs contain exactly the same objects before publishing them. The architecture is in a limited private preview, with a broader rollout planned for early next year. The follow-up list includes an atomic multi-file commit API, reading files straight from the server, and event streams.</p>

<p><a href="https://nayak.im/posts/optimizing-reference-deletion/">Optimizing reference deletions in Git</a> (Karthik Nayak) covers deleting refs in the files backend in repositories with millions of them, such as GitLab’s own with over 15 million. Deleting a packed ref rewrites the whole <code class="language-plaintext highlighter-rouge">packed-refs</code> file, which can reach several GB. Nayak had an LLM write a Rust version of the files backend to measure the overhead of the C to Rust boundary, and the Rust version deleted refs about 17% faster.</p>

<p>For every record being retained, the C code rebuilt the line with <code class="language-plaintext highlighter-rouge">fprintf()</code> and <code class="language-plaintext highlighter-rouge">oid_to_hex()</code>, where the Rust version copied the original bytes. Nayak’s patch writes retained records with <code class="language-plaintext highlighter-rouge">fwrite()</code> and matches the Rust version’s speed. It is merged and will ship in Git 2.98, the version number that follows 2.56, with Git 3.0 due two releases after that.</p>

<h2 id="releases">Releases</h2>

<p><a href="https://github.com/jj-vcs/jj/releases/tag/v0.47.0">jj 0.47.0</a> adds a built-in <code class="language-plaintext highlighter-rouge">:editor</code> merge tool for <code class="language-plaintext highlighter-rouge">jj resolve</code>, which opens the conflicted file with conflict markers in a text editor and supports conflicts with more than two sides. Templates have a new top-level <code class="language-plaintext highlighter-rouge">revset()</code> function for evaluating revsets. In colocated workspaces, <code class="language-plaintext highlighter-rouge">jj describe -r@</code> and <code class="language-plaintext highlighter-rouge">jj restore --into=@</code> now preserve the Git staging area, and two race conditions with concurrent Git processes are fixed.</p>

<p>Updating remote-tracking Git refs in non-colocated workspaces moves from <code class="language-plaintext highlighter-rouge">jj git fetch</code> and <code class="language-plaintext highlighter-rouge">push</code> to <code class="language-plaintext highlighter-rouge">jj git export</code>. <code class="language-plaintext highlighter-rouge">Timestamp.format()</code> now uses jiff’s strftime syntax in place of chrono’s. <a href="https://github.com/jj-vcs/jj/releases/tag/v0.47.1">0.47.1</a> fixes a dependency error that broke Linux builds of 0.47.0, and deprecates the <code class="language-plaintext highlighter-rouge">git.sign-on-push</code> boolean in favour of a <code class="language-plaintext highlighter-rouge">revsets.git-sign-on-push</code> revset of the commits to sign.</p>

<p><a href="https://github.com/gitbutlerapp/gitbutler/releases/tag/release%2F0.23.3">GitButler 0.23.3</a> updates linked worktrees when the workspace is updated, and preserves conflicting uncommitted changes in them with conflict markers. It fixes branch apply, unapply and update writing encrypted files or Git LFS pointers in place of file contents in git-crypt and Git LFS repositories.</p>

<p>On the command line, <code class="language-plaintext highlighter-rouge">but commit</code>, <code class="language-plaintext highlighter-rouge">amend</code>, <code class="language-plaintext highlighter-rouge">discard</code> and <code class="language-plaintext highlighter-rouge">diff</code> accept Git-style paths, and <code class="language-plaintext highlighter-rouge">but diff</code> and <code class="language-plaintext highlighter-rouge">but show</code> take <code class="language-plaintext highlighter-rouge">--stat</code>. <code class="language-plaintext highlighter-rouge">but commit</code> runs Git commit hooks again in the main checkout. <code class="language-plaintext highlighter-rouge">but push --dry-run</code> lists the branches that would be refused and exits non-zero if there are any.</p>

<p><a href="https://github.com/danielroe/forges/releases/tag/v0.3.2">forges 0.3.2</a> adds providers for Entire and GitBucket, which brings the capability table to 14 forges. The Cursor Origin provider goes from 13 verified capabilities to 35, and the GitHub provider adds <code class="language-plaintext highlighter-rouge">users.sponsorableMany</code>. Two sourcehut fixes cover parsing web URLs on an instance’s root host and accepting a service host as <code class="language-plaintext highlighter-rouge">baseUrl</code>.</p>

<p>The <a href="https://pushin.eu/docs/blog/2026-11-06-changelog">Pushin changelog for 6 November</a> (Peter, Pushin) adds branch and tag rulesets that can block history rewrites and deletion, and require a minimum number of approvals and passing workflow checks before a merge. Personal access tokens can now be scoped per permission group and limited to selected repositories. Existing tokens are migrated with full access and their expiry dates removed.</p>

<p>Webhooks are set up once per account or organisation and reused across repositories. The release also adds repository transfers that the new owner has to accept, runner groups shared across repositories, and Atom feeds for commits, releases, issues and pull requests.</p>

<h2 id="security">Security</h2>

<p><a href="https://github.blog/open-source/git/git-security-vulnerabilities-announced-7/">Git 2.56.1</a> (Elijah Newren, GitHub) fixes six vulnerabilities, with backports in 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3 and 2.50.2:</p>

<ul>
  <li>CVE-2026-111760: an integer truncation in index handling let an extremely long path pass validation under one name and be written under a shorter one. A malicious repository could use it to replace a submodule’s <code class="language-plaintext highlighter-rouge">.git</code> file with a symlink to a directory of attacker-supplied config or hooks, which then ran during a recursive clone.</li>
  <li>CVE-2026-113408: when cloning an empty repository over protocol v2, a server could advertise a HEAD symref whose target contained path-traversal components. With the files ref backend, a later update to that branch could write outside the reference directory.</li>
  <li>CVE-2026-114467: the code that strips GPG signatures from a message had a fixed-size stack array with room for two. Merging a tag with more than two wrote past the end of it, and hosting services that run merges for users are affected too.</li>
  <li>CVE-2026-114469: the 1 GiB patch size limit checked only the size of the input, so a small binary patch that inflates past the limit caused an out-of-bounds read.</li>
  <li>CVE-2026-105437: the size calculation for a merge result could overflow with many conflicts and a large <code class="language-plaintext highlighter-rouge">conflict-marker-size</code>, and Git then wrote outside the undersized buffer.</li>
  <li>CVE-2026-114466: <code class="language-plaintext highlighter-rouge">git fast-import</code> now accepts <code class="language-plaintext highlighter-rouge">rewrite-submodules-from</code>, <code class="language-plaintext highlighter-rouge">rewrite-submodules-to</code> and <code class="language-plaintext highlighter-rouge">export-pack-edges</code> in an input stream only when the caller passes <code class="language-plaintext highlighter-rouge">--allow-unsafe-features</code>. The first two could read arbitrary files and the third could create or append to them.</li>
</ul>

<p>GitHub has deployed the fixes on github.com and released GitHub Enterprise Server 3.19.15, 3.20.11, 3.21.9 and 3.22.4. <a href="https://github.com/git-for-windows/git/releases/tag/v2.56.1.windows.1">Git for Windows 2.56.1</a> includes the same six fixes, and GitHub says patched GitHub Desktop builds will follow.</p>

<p><a href="https://github.com/jesseduffield/lazygit/releases/tag/v0.66.3">lazygit 0.66.3</a> skips submodules whose name or path in <code class="language-plaintext highlighter-rouge">.gitmodules</code> resolves outside the repository. lazygit parses <code class="language-plaintext highlighter-rouge">.gitmodules</code> itself, and <a href="https://github.com/jesseduffield/lazygit/pull/6187">the pull request</a> explains that removing a submodule named <code class="language-plaintext highlighter-rouge">../../../victim</code> deleted the <code class="language-plaintext highlighter-rouge">victim</code> directory next to the repository. Anyone able to commit a <code class="language-plaintext highlighter-rouge">.gitmodules</code> file could set that up. Git skips such names, and lazygit now applies the same check and removes a submodule only when its git dir is inside <code class="language-plaintext highlighter-rouge">.git/modules</code>.</p>

<p><a href="https://www.gerritcodereview.com/3.14.html#3145">Gerrit 3.14.5</a> fixes a vulnerability where any user able to read a change could use <code class="language-plaintext highlighter-rouge">on_behalf_of</code> to act as a project owner and remove another reviewer’s vote. The release also speeds up tag listing by building the full tag details only for the page being returned. Listing 26 tags in a repository with 20,000 annotated tags went from around 450ms to between 15 and 35ms.</p>

<h2 id="github">GitHub</h2>

<p>A <a href="https://github.blog/changelog/2026-11-05-new-pull-request-overview-page-in-public-preview">new pull request overview page</a> is in opt-in public preview. It moves merge status to the top of the page in a redesigned merge box that takes less than half the space, with checks, comments and approvals summarised beside it. Conversations can be filtered to unresolved threads or the viewer’s own comments, and sorted newest first. A button in the header switches the preview on, and the same menu switches back to the classic page.</p>

<p><a href="https://github.blog/changelog/2026-11-09-secret-scanning-detects-secrets-in-github-actions-workflow-logs">Secret scanning now covers GitHub Actions workflow logs</a> in public preview, for GitHub Enterprise Cloud customers with Secret Protection or Advanced Security. Logs are scanned for provider patterns when a run completes, and the alerts are retained when the logs are deleted. Scanning is limited to provider patterns in logs from new runs, which excludes existing logs, generic patterns, custom patterns and secrets already masked by Actions.</p>

<h2 id="elsewhere">Elsewhere</h2>

<p>Anil Madhavapeddy is <a href="https://amok.recoil.org/@avsm/117581872386695231">using Brief to power auto-CI</a> in a new Tangled spindle. <a href="https://github.com/git-pkgs/brief">Brief</a> is my tool for detecting the languages and toolchains in a repository. In <a href="https://tangled.org/anil.recoil.org/xdge/pipelines/3mzsusqp3zf22/workflow/detect">the pipeline for Madhavapeddy’s xdge library</a>, a <code class="language-plaintext highlighter-rouge">detect</code> workflow runs first, followed by an <code class="language-plaintext highlighter-rouge">ocaml-ci</code> workflow that builds on Debian 13 across several OCaml versions on x86_64 and arm64.</p>

<p>Send links for next week to <a href="https://mastodon.social/@andrewnez">@andrewnez@mastodon.social</a>.</p>]]></content><author><name>Andrew Nesbitt</name><email>andrew@ecosyste.ms</email></author><category term="git" /><category term="weekly" /><category term="twisc" /><summary type="html"><![CDATA[Releases, advisories, and articles from across version control and forges]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://nesbitt.io/images/boxes.png" /><media:content medium="image" url="https://nesbitt.io/images/boxes.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">This Week in Source Control: 4 November 2026</title><link href="https://nesbitt.io/2026/11/04/this-week-in-source-control.html" rel="alternate" type="text/html" title="This Week in Source Control: 4 November 2026" /><published>2026-11-04T10:00:00+00:00</published><updated>2026-11-04T10:00:00+00:00</updated><id>https://nesbitt.io/2026/11/04/this-week-in-source-control</id><content type="html" xml:base="https://nesbitt.io/2026/11/04/this-week-in-source-control.html"><![CDATA[<p>This week’s version control and forge news, gathered from release feeds for source control clients and forges, the <a href="https://lobste.rs/t/vcs">Lobsters vcs tag</a>, Hacker News, and my boosts on <a href="https://mastodon.social/@andrewnez">Mastodon</a>. Package management news is in the Saturday <a href="/2026/10/31/this-week-in-package-management.html">This Week in Package Management</a> roundup.</p>

<h2 id="scaling">Scaling</h2>

<p><a href="https://openai.com/index/scaling-git-at-openai/">Scaling Git at OpenAI</a> (Aaron Friel, Taylor Blau and Ted Nyman, OpenAI) describes Pando, a Rust backend for git repositories that now serves all development in OpenAI’s monorepo. Each push is stored as an immutable packfile in blob storage, and each branch update records a ref version in a metadata store, so pushes contend only when they target the same ref. The trade-off is causal consistency, so a client reading several branches can see them at different points in time.</p>

<p>When a new branch is pushed, Pando advertises only trunk, which keeps the pushed pack reusable for anyone who already has trunk, and the median pack produced this way was under 20 KiB. On a fetch, Pando sends an empty packfile in the response and lists the packs the client needs as packfile-uri links. The client downloads those packs from a regional cache with a hit rate above 99%.</p>

<p>Background compaction merges small packs into larger ones in levels, up to L4 in the monorepo, and the levels double as a skip list for choosing which packs a client needs. OpenAI reports median push latency down by nearly 80% and nearly a petabyte of git data served a day. Fixes to packfile-uri downloads have gone upstream, and other changes, such as downloading and indexing packs in parallel, are in <a href="https://github.com/openai/git">OpenAI’s git fork</a>.</p>

<p><a href="https://typesanitizer.com/blog/scion.html">An outsider’s perspective on Scion and Mononoke</a> (typesanitizer) responds to Anthropic’s Scion post from someone on the source control team at Databricks, whose monorepo’s main branch history is 20-50GB. The author lists the parts of Scion’s design that already exist in Mononoke, Perforce or Piper, such as per-directory ACLs, server-side history queries and changesets in place of git trees.</p>

<p>They also question Anthropic’s mirror count: Databricks serves CI from fewer than 10 git mirrors and reference repositories refreshed every two hours, while Anthropic reported running several hundred mirrors at its peak.</p>

<p><a href="https://delta.dev/blog/fine-grained-version-control-for-agents">Building fine-grained version control for agents</a> (Antonio Scandurra, Delta) describes DeltaDB from the team behind Zed. Each agent thread is a DAG of CRDT deltas stored in SQLite on the client and synced to one Cloudflare Durable Object per thread.</p>

<p>Worktrees are layered on top of git, starting from a commit and recording edits as deltas, and creating a commit adds a delta that links the DAG back to git’s history. Subagents work on separate timelines in the same DAG and merge back into it, and coordinating agents this way needs no git commit.</p>

<p><a href="https://thenewstack.io/github-7-4b-commits-september/">GitHub saw 7.4B commits in September</a> (Frederic Lardinois, The New Stack) reports figures from GitHub Universe. GitHub had 1.4 billion commits a month in April and 2.9 billion in August. It has added 4 million CPU cores and 160 PB of storage this year, alongside the move to separate compute and storage covered in <a href="/2026/10/28/this-week-in-source-control.html">last week’s issue</a>.</p>

<h2 id="releases">Releases</h2>

<p><a href="https://github.com/meta/sapling/releases/tag/0.2.20261028-123539%2B7415fb2f">Sapling 0.2.20261028</a> makes <code class="language-plaintext highlighter-rouge">sl worktree</code> work in checkouts made with <code class="language-plaintext highlighter-rouge">git clone</code>, using <code class="language-plaintext highlighter-rouge">git worktree add</code> underneath, and ships it in builds without EdenFS, including the open source ones. <code class="language-plaintext highlighter-rouge">sl drop -r REV</code> is now on by default and removes commits from a stack, rebasing their descendants.</p>

<p>This release also adds a <code class="language-plaintext highlighter-rouge">--plan</code> flag to <code class="language-plaintext highlighter-rouge">histedit</code> for giving the plan on the command line, plus an <code class="language-plaintext highlighter-rouge">into</code> verb that folds the previous commit in while keeping the current message. Rewriting a commit in the middle of a stack now works with <code class="language-plaintext highlighter-rouge">uncommit</code> too. <a href="https://github.com/meta/sapling/releases/tag/0.2.20261102-153821%2Ba53273dc">0.2.20261102</a> fixes a regression from that release, where files under directories matched by rules like <code class="language-plaintext highlighter-rouge">target/</code> showed up as untracked and nested <code class="language-plaintext highlighter-rouge">.gitignore</code> files were skipped.</p>

<p><a href="https://github.com/ivankovic/omnidiff/releases/tag/v0.3.0">OmniDiff 0.3.0</a> is the latest release of Marko Ivankovic’s content-aware difftool in Rust. It was on Hacker News this week and diffs code by syntax, along with pictures, fonts, archives and PDFs. This release diffs code embedded in strings as its own language, for example shell in a YAML <code class="language-plaintext highlighter-rouge">run:</code> block or CSS in template literals, and diffs CSS class lists one class at a time.</p>

<p>The <a href="https://gitroot.dev/blog/version-0.5.0-plugins.html">GitRoot 0.5.0 plugins</a> include Firefly, which is written in Zig and generates status pages inside the forge. Silo, which builds indexes from files and their metadata, can now render them to the web grouped by any property, and Apex, the plugin that renders repository files to the web, adds a slide layout.</p>

<p><a href="https://blog.gitea.com/release-of-gitea-cli-1.0.0/">gt 1.0.0</a> is the first stable release of the Gitea command line tool <a href="/2026/10/28/this-week-in-source-control.html">introduced last week</a>, and it replaces tea as Gitea’s official CLI. tea is discontinued and its repository archived. A migration guide maps its commands and flags to gt’s. Commands, flags, <code class="language-plaintext highlighter-rouge">--json</code> fields and exit codes now follow semantic versioning. Changes since 0.1.0 include:</p>

<ul>
  <li><code class="language-plaintext highlighter-rouge">gt upgrade</code> replaces the binary after checking its SHA-256 checksum, or names the package manager command when gt came from Homebrew, Nix, a Linux package or <code class="language-plaintext highlighter-rouge">go install</code>.</li>
  <li>Extensions named <code class="language-plaintext highlighter-rouge">gt-NAME</code> install from any Gitea instance, and GitHub CLI extensions that avoid GitHub’s APIs also run.</li>
  <li><code class="language-plaintext highlighter-rouge">gt pr backport</code> cherry-picks a merged pull request onto one or more release branches and opens a pull request into each.</li>
  <li>Every command with <code class="language-plaintext highlighter-rouge">--json</code> also takes <code class="language-plaintext highlighter-rouge">--csv</code>.</li>
</ul>

<p><a href="https://github.com/narnaud/git-loom/releases/tag/v1.0.0">git-loom 1.0</a> merges a set of feature branches into one integration branch, where they are built and tested together. Its commands commit, amend, split and move changes between those branches while the integration branch stays checked out, and rewrite history so each stays a side branch joined by a merge.</p>

<p>Stacked branches are pushed as one pull request each to GitHub, GitLab, Azure DevOps or Gerrit. Commits get short IDs from a <code class="language-plaintext highlighter-rouge">Change-Id</code> trailer, so the IDs stay the same across rewrites. With 1.0 the commands, <code class="language-plaintext highlighter-rouge">loom.*</code> settings and agent mode follow semantic versioning, and it requires Git 2.43 or later.</p>

<p><a href="https://github.com/Wilfred/difftastic/releases/tag/0.72.0">difftastic 0.72.0</a> changes its preprocessing heuristics so it falls back to text diffing less often, and updates the Haskell and Kotlin parsers. Verilog, F# and Smali support is removed. The Verilog and F# parsers made the <code class="language-plaintext highlighter-rouge">difft</code> binary large, and the upstream Smali parser is unmaintained. It also fixes terminal width detection when stdin, stdout and stderr are all redirected, which broke in 0.71 and was most noticeable when running difft from jj.</p>

<p><a href="https://github.com/gitbutlerapp/gitbutler/releases/tag/release%2F0.23.2">GitButler 0.23.2</a> stops commits and amends from disturbing staged files, and undo now restores deleted branches after a git garbage collection. Merge request listing also works on older GitLab instances. On the command line, <code class="language-plaintext highlighter-rouge">but agent setup</code> adds Amp support, and <code class="language-plaintext highlighter-rouge">but worktree new --above</code> takes branch names and IDs as well as git revisions.</p>

<p>Also out: <a href="https://github.com/danielroe/forges/releases/tag/v0.3.1">forges v0.3.1</a>.</p>

<h2 id="security">Security</h2>

<p><a href="https://blog.gitea.com/release-of-28.3.0/">Gitea 28.3.0</a> fixes 21 CVEs, many of them places where public-only tokens could reach private data or admin actions. Among them:</p>

<ul>
  <li>With <code class="language-plaintext highlighter-rouge">ACCOUNT_LINKING = auto</code> and open registration, someone signing in through an OAuth2 provider could enter another user’s name or email and be linked to that existing account with only the OAuth2 sign-in (CVE-2026-120263).</li>
  <li>A user with read access could submit a pull request review whose <code class="language-plaintext highlighter-rouge">commit_id</code> named their own commit, so <code class="language-plaintext highlighter-rouge">pull_request_review</code> workflows ran from that commit with the repository’s secrets and a write token (CVE-2026-118386).</li>
  <li>A site administrator’s public-only token could use the admin API to list every user’s email address and create new administrators (CVE-2026-117635).</li>
  <li>An organization owner’s public-only token had enough access to delete all of the organization’s repositories, private ones included (CVE-2026-119441).</li>
  <li>Release binaries are built with Go 1.27.3, which rejects certificates chained through the eMudhra intermediates, for Gitea’s outgoing connections to OAuth2 providers, webhooks, mirrors and migrations (CVE-2026-111943). Saturday’s <a href="/2026/10/31/this-week-in-package-management.html">package management roundup</a> has more on that incident, including a test page showing that the git Apple ships with macOS still accepts those certificates.</li>
</ul>

<p>Alpine Linux <a href="https://alpinelinux.org/posts/GitLab-security-incident-CVE-2026-97229.html">rebuilt its GitLab instance</a> after an attacker tried to exploit CVE-2026-97229 on 20 and 21 October. The bug is in Onigmo, Ruby’s regular expression engine, and GitLab’s fix is a patch applied to the Ruby in its official packages. Alpine’s image used standard Ruby, so upgrading GitLab on 22 October left it vulnerable.</p>

<p>The attacker crashed worker processes eight times, and Alpine found no evidence of code execution. A check on 26 October turned up the unpatched Ruby, and the instance was rebuilt and reopened on 29 October. The aports repository and packages, including the 21 October releases, were checked against outside records, and all passwords were reset. GitLab installs that use their own Ruby also need Ruby 3.3.13, 3.4.12, 4.0.9 or later.</p>

<p><a href="https://www.mongodb.com/company/blog/technical/scanning-7-point-25-million-public-repositories-chinas-largest-git-platform-for-secrets">Scanning 7.25M public repositories on Gitee for secrets</a> (Ben Zimmermann, MongoDB) found 26,400 unique verified-live credentials using TruffleHog and Kingfisher. The only official Gitee API endpoint that returned useful data at that size was user search, so the repository list was built from that, Explore feeds, per-user pages and the Elasticsearch widget behind the site’s search. GitHub runs secret-scanning partnerships with credential issuers, and Gitee has no public equivalent.</p>

<h2 id="github">GitHub</h2>

<p><a href="https://github.blog/changelog/2026-11-02-github-desktop-adds-short-lived-authentication-tokens">GitHub Desktop 3.6.10 and later can sign in with short-lived tokens</a> that refresh automatically for API requests and git operations. The rollout is gradual and covers github.com only. Existing tokens stay as they are, and an installation gets short-lived tokens at its first sign-in after the rollout reaches it.</p>

<p>The <a href="https://github.com/desktop/desktop/releases/tag/release-3.6.8">3.6.8 release notes</a> list the change alongside Git 2.56.0, Git LFS 3.8.1 and Git Credential Manager 2.9.1. <a href="https://github.com/desktop/desktop/releases/tag/release-3.6.10">3.6.10</a> bundles <a href="https://github.com/git-for-windows/git/releases/tag/v2.56.0.windows.4">Git for Windows 2.56.0.windows.4</a>, whose brotli upgrade to 1.2.1 fixes CVE-2026-111497.</p>

<p>Pull request limits can now <a href="https://github.blog/changelog/2026-10-28-pull-request-limits-exempt-contributors-by-age-or-history">exempt contributors by account age or by number of merged pull requests</a> in that repository. A contributor who meets either enabled rule can open pull requests beyond the cap.</p>

<p><a href="https://github.blog/changelog/2026-10-28-push-protection-beyond-predefined-secret-patterns">Push protection can block AI-detected secrets</a>, in public preview, using a classifier that scores a value by how the surrounding code uses it, in place of format matching. GitHub reports it more than doubled the number of pushes where push protection caught a secret. It is opt-in and requires AI-detected secret scanning and push protection to be enabled first.</p>

<p>The Meta API now lists <a href="https://github.blog/changelog/2026-10-29-webhook-ip-ranges-added-to-the-meta-api">three more IP ranges for webhook deliveries</a> in its <code class="language-plaintext highlighter-rouge">hooks</code> field. Static allowlists for incoming webhooks need the new CIDR prefixes added.</p>

<h2 id="elsewhere">Elsewhere</h2>

<p>Tangled has <a href="https://tangled.org/blog/forge">relaunched as a federated code forge</a> on the AT Protocol. Knot2, a rewrite of its git server in Rust, stores issues, pull requests, comments and labels in the repository as collaborative objects, chains of git objects synced over the AT Protocol firehose. Each edit also writes an attestation record to the author’s own PDS.</p>

<p>The release adds organization accounts and stacked pull requests with interdiffs for git and jj users. A new Svelte frontend is served from read-only Rust indexers in 11 or more regions, and self-hosted knots need upgrading to v1.20.0.</p>

<p>David Bushell <a href="https://dbushell.com/2026/11/01/tangled-accessibility/">responded to the new Tangled UI</a> with an accessibility review. The interface sets text at 12px, and a <code class="language-plaintext highlighter-rouge">font-size: 16px</code> on the <code class="language-plaintext highlighter-rouge">&lt;html&gt;</code> element fixes the root size regardless of browser settings. Forcing a 200% resize clips and truncates text, which fails WCAG 2.2’s 1.4.4 Resize Text criterion.</p>

<p>Forgejo is <a href="https://forgejo.org/2026-11-removing-openid/">removing OpenID 2.0 sign-in</a> in v19, due on 25 March 2027, and keeping OpenID Connect and OAuth. The v15 LTS keeps OpenID 2.0 until its end of life on 15 July 2027, and v17 and v18 keep it until 29 April 2027.</p>

<p><a href="https://git.github.io/rev_news/2026/10/31/edition-140/">Git Rev News 140</a> leads with a fix for <code class="language-plaintext highlighter-rouge">git push --force-if-includes</code>, which rejected valid force pushes when the remote-tracking ref had no reflog. A ref created by <code class="language-plaintext highlighter-rouge">git clone</code> with the files backend gets its first reflog entry when it moves, and before that a cut-off timestamp was left uninitialised.</p>

<p>Aleksei Sviridkin’s one-line patch sets it to 0. In review Junio Hamano suggested a 90-day cut-off, then agreed to 0 after Tyler Cipriani described a case with default gc settings where the cut-off gives the wrong answer.</p>

<p>The first version of the patch carried an <code class="language-plaintext highlighter-rouge">Assisted-by: LLM</code> trailer following Linux kernel practice. After Junio pointed to the AI section of Git’s <code class="language-plaintext highlighter-rouge">SubmittingPatches</code>, version 3 of the patch dropped the trailer.</p>

<p>Send links for next week to <a href="https://mastodon.social/@andrewnez">@andrewnez@mastodon.social</a>.</p>]]></content><author><name>Andrew Nesbitt</name><email>andrew@ecosyste.ms</email></author><category term="git" /><category term="weekly" /><category term="twisc" /><summary type="html"><![CDATA[Releases, advisories, and articles from across version control and forges]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://nesbitt.io/images/boxes.png" /><media:content medium="image" url="https://nesbitt.io/images/boxes.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">This Week in Source Control: 28 October 2026</title><link href="https://nesbitt.io/2026/10/28/this-week-in-source-control.html" rel="alternate" type="text/html" title="This Week in Source Control: 28 October 2026" /><published>2026-10-28T10:00:00+00:00</published><updated>2026-10-28T10:00:00+00:00</updated><id>https://nesbitt.io/2026/10/28/this-week-in-source-control</id><content type="html" xml:base="https://nesbitt.io/2026/10/28/this-week-in-source-control.html"><![CDATA[<p>Alongside package management, I follow new features and security fixes in source control clients and in the forges that host repositories, since a lot of what I build, like <a href="https://github.com/git-pkgs">git-pkgs</a>, reads git repositories and calls forge APIs. <a href="/2026/10/24/this-week-in-package-management.html">This Week in Package Management</a> has been published every Saturday since May, and I kept putting git releases and forge news in its Elsewhere section.</p>

<p>Starting this week, I’m publishing that material as a separate roundup on Wednesdays. It covers clients like git, jj, gitoxide, Sapling, Mercurial and Git LFS, and forges like GitHub, GitLab, Forgejo, Gitea, Codeberg, sourcehut, Radicle and Tangled. Package managers resolving git dependencies and CI systems like GitHub Actions are covered in the Saturday post.</p>

<p>This first issue covers the fortnight since 11 October, with links from release feeds for those tools and forges, the <a href="https://lobste.rs/t/vcs">Lobsters vcs tag</a>, Hacker News and my boosts on <a href="https://mastodon.social/@andrewnez">Mastodon</a>. In that fortnight Anthropic, GitHub, Entire and Enroute each published a post about rebuilding source control or git hosting for the volume of pushes and checkouts from coding agents.</p>

<h2 id="scaling">Scaling</h2>

<p><a href="https://www.anthropic.com/engineering/redesigning-source-control">Redesigning source control at Anthropic</a> (Anthropic Engineering) describes Scion, an in-house version control system that replaced git for the company’s monorepo in five months. Merges went from around 2,500 a day in May to over 30,000 a day in September. The main branch history is almost 100 GB, and CI performs around 25 million checkouts a day. Scion is designed for clients that are always online. The server stores changesets in a write-ahead log on Spanner and runs blame, history and merge queries server-side, and clients fetch only the trees and blobs they request through regional caches. Anthropic reports the new infrastructure uses 200x less CPU and memory than the git mirror fleet it replaced. In <a href="https://simonwillison.net/2026/Oct/13/redesigning-source-control-at-anthropic/">notes on the post</a>, Simon Willison compares it to centralised systems like Subversion.</p>

<p><a href="https://sunshowers.io/posts/anthropic-mononoke/">Anthropic’s Scion is heavily inspired by Mononoke</a> (sunshowers) points out that Scion’s “derived data” for fast blame and history queries matches the design of Mononoke, the server side of Meta’s Sapling. The original post credited Sapling only for “hard-won lessons”. <a href="https://sunshowers.io/posts/anthropic-mononoke-2/">A follow-up</a> compares Scion’s changesets with Mononoke’s Bonsai changesets. Anthropic has since updated its post with more detail on the projects Scion is based on.</p>

<p><a href="https://github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure/">The bridge to agent-scale Git infrastructure</a> (Eleanor White and Victoria Dye, GitHub Blog) covers the move of GitHub’s repositories to Azure. Most repositories have two of their five replicas there, and Azure serves about half of Git traffic. Moving the busiest repositories was blocked by a repository-wide lock that every write held across a 25ms cross-region round trip. Spokes is switching to per-reference serialisation, so only writes to the same ref wait for each other, which gave 3-4x write throughput in internal tests. Object storage then joins the write quorum as a “virtual replica”, so read replicas can be stateless.</p>

<p><a href="https://entire.com/blog/the-git-forge-for-agent-human-collaboration">Entire</a>, a new git forge from a company co-founded by former GitHub CEO Thomas Dohmke, is built for repositories where coding agents and people push to the same branches. Its git server replicates each repository across regions, and the company’s <a href="https://github.com/entireio/forgemark">forgemark</a> benchmark reports pushes up to 89x faster than GitHub and 6x faster than Cursor Origin. Review happens through Trails, which run configured checks and agent-run evaluations in Daytona or E2B sandboxes on every push instead of a pull request diff. Agent sessions and prompts are synced into the repository and indexed for later agents to search.</p>

<p><a href="https://enroute.sh/blog/everyone-is-doing-git-on-s3-wrong">Everyone is doing Git on S3 wrong</a> (Enroute) looks at the write-ahead log designs for git on object storage that followed Cursor’s Continuity. Those designs send every push to a repository through one primary, and every replica keeps a full copy of the repository on disk. Enroute keeps each repository’s refs and a list of immutable object layers in a Raft-replicated log. Packfiles are rewritten on ingestion so a read from object storage needs only a few requests, and Enroute reports more than 7,600 pushes per second into a single repository. Against stock git serving a repacked linux.git, full clones are about 17% slower and shallow clones more than twice as fast.</p>

<h2 id="releases">Releases</h2>

<p><a href="https://docs.gitlab.com/releases/19/gitlab-19-5-released/">GitLab 19.5</a> makes the GitLab MCP server and GitLab Secrets Manager, built on OpenBao, generally available. Smaller changes include a commit count variable for commit message templates, and commits signed by revoked GPG identities now show as unverified.</p>

<p><a href="https://forgejo.org/2026-10-release-v17-0/">Forgejo 17.0</a> resolves absolute links in rendered documents against the repository root, as other forges do, and deprecates action run webhook events in favour of workflow run events. It also adds a Donate button driven by <code class="language-plaintext highlighter-rouge">FUNDING.yml</code>, migration from Bitbucket Data Center, and opt-in invitations for organisation membership. <a href="https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/17.0.1.md">Forgejo 17.0.1, 16.0.7 and 15.0.11</a> followed on 26 October as security releases. The main fix stops a <code class="language-plaintext highlighter-rouge">pull_request_review</code> event running an Actions workflow as trusted from an arbitrary commit, including one from a fork, by ignoring the unvalidated <code class="language-plaintext highlighter-rouge">commit_id</code> on the submitted review. 17.0.1 also carries bug fixes for 17.0.0, which the project had <a href="https://floss.social/@forgejo/117450533397721524">advised holding off from</a> after reports of blocked pushes and merges.</p>

<p><a href="https://gitroot.dev/blog/version-0.5.0.html">GitRoot 0.5.0</a>, a self-hosted forge with no database that is extended through WASM plugins, now references plugins by PURL with a checksum qualifier in place of separate URL, checksum and version fields. New per-forge and per-repository settings cap how many branches anonymous users can push before further anonymous pushes are rejected.</p>

<p><a href="https://pushin.eu">Pushin.eu</a>, an invite-only forge hosted in the EU, shipped several releases this fortnight according to its <a href="https://pushin.eu/pjullrich/pushin/changelog">changelog</a>. 0.3.26 adds tag-based releases with a GitHub-compatible API and GoReleaser publishing, and 0.3.29 serves public repository files from <code class="language-plaintext highlighter-rouge">raw.pushin.eu</code>. 0.3.32 adds runner groups for self-hosted runners and removes the per-repository <code class="language-plaintext highlighter-rouge">allow_persistent_runners</code> setting.</p>

<p><a href="https://forges.link/">forges</a> (Daniel Roe) is a TypeScript version of my Go library <a href="https://github.com/git-pkgs/forge">git-pkgs/forge</a>, with one interface for issues, pull requests, notifications, checks and webhooks across GitHub, GitLab, Bitbucket, Forgejo, Gitea, Gitee, Azure DevOps, Cursor Origin, Tangled, Pushin.eu and Sourcehut. Each provider declares which operations it supports, and the release notes show the capability changes per forge. <a href="https://github.com/danielroe/forges/releases/tag/v0.1.0">0.1.0</a> came out on 11 October, and <a href="https://github.com/danielroe/forges/releases/tag/v0.3.0">0.3.0</a> adds branch rules and review threads.</p>

<p><a href="https://blog.gitea.com/release-of-gitea-cli-0.1.0/">gt 0.1.0</a> replaces <code class="language-plaintext highlighter-rouge">tea</code>, Gitea’s command line tool, with a rewrite under a new name and repository. Every list and view command supports <code class="language-plaintext highlighter-rouge">--json</code> and <code class="language-plaintext highlighter-rouge">--jq</code>, and <code class="language-plaintext highlighter-rouge">gt pr checkout</code> and <code class="language-plaintext highlighter-rouge">gt pr diff</code> handle fork and AGit pull requests. It requires Gitea 28 or newer.</p>

<p><a href="https://github.com/GitoxideLabs/gitoxide/releases/tag/v0.61.0">gitoxide 0.61.0</a> moves the plumbing crates to a standard <code class="language-plaintext highlighter-rouge">std::error::Error</code> compatible error type and improves tracing across commands, along with security fixes.</p>

<h2 id="security">Security</h2>

<p><a href="https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1">Git LFS 3.8.1</a> fixes four CVEs:</p>

<ul>
  <li>unquoted arguments in remote commands sent over SSH</li>
  <li>Cookie headers forwarded to other hosts after a redirect</li>
  <li>an arbitrary program run from a malicious repository through line feeds in a submodule URL</li>
  <li>an arbitrary program run from a malicious repository through a custom transfer adapter set in <code class="language-plaintext highlighter-rouge">.lfsconfig</code></li>
</ul>

<p>GitLab shipped two critical patch releases for integer overflows in its regular expression compiler that allowed unauthenticated code execution. The <a href="https://www.bleepingcomputer.com/news/security/gitlab-warns-of-max-severity-rce-flaw-in-regex-compiler-engine/">first, on 12 October</a>, fixed CVE-2026-97229 in CI configuration patterns, and a <a href="https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/">21 October release</a> fixed CVE-2026-110264, which affects every version from 7.0 and was backported as far as 18.11.13. The underlying bugs are in Ruby’s Onigmo, whose fixes were in <a href="/2026/10/24/this-week-in-package-management.html">last week’s package management roundup</a>.</p>

<p><a href="https://blog.gitea.com/release-of-28.2.0/">Gitea 28.2.0</a> discloses 13 CVEs, two of them fixed in earlier releases. One fix limits which stored public keys an SSH certificate principal is matched against. Before the fix, matching against every stored key let a certificate authenticate as a different user.</p>

<p><a href="https://git-annex.branchable.com/security/cross_repository_data_exfiltration_via_special_remote/">git-annex 10.20261026</a> fixes CVE-2026-112818, a cross-repository exfiltration attack found by Joey Hess. A repository the victim clones can autoenable a special remote that points at the victim’s own private git-annex storage, so a later <code class="language-plaintext highlighter-rouge">git-annex sync --content</code> reads the private files and sends them to the attacker. After the fix, <code class="language-plaintext highlighter-rouge">enableremote</code> requires the special remote’s configuration to be verified, and git-annex refuses to send content to an unverified autoenabled remote.</p>

<p><a href="https://www.wiz.io/blog/gheist-attempted-scaled-abuse-of-stolen-github-tokens-stumbles">Gheist</a> (Rami McCarthy and Hila Ramati, Wiz) is a campaign that used stolen GitHub tokens to push a workflow to every reachable repository. The workflow writes repository secrets to its log in base32 so GitHub’s masking leaves them unredacted, and the attacker’s tool fetches the log over the API and deletes the run seconds later. GitHub’s hold on potentially malicious workflows in public repositories, in place since 28 July, blocked the payload there. Private repositories and GitHub Enterprise Server fall outside that hold, and Wiz observed successful runs and follow-on AWS activity from those.</p>

<p>An attacker took over a developer’s GitHub account and <a href="https://www.bleepingcomputer.com/news/security/ovhcloud-cli-releases-backdoored-on-github-to-steal-developer-secrets/">replaced OVHcloud CLI releases 0.11.0 to 0.15.0</a> with builds that read secrets from disk. Release immutability was turned off on the repository, so the attacker could overwrite the existing releases directly and skip CI.</p>

<h2 id="github">GitHub</h2>

<p><a href="https://github.blog/changelog/2026-10-12-push-attribution-public-preview">Push attribution</a>, in limited preview for Enterprise customers, records the authenticated user who pushed each commit alongside the author and committer fields. A new “Committer must match pusher” ruleset condition accepts a push only when the committer matches one of the pusher’s verified email addresses.</p>

<p>During periods of unusual traffic, <a href="https://github.blog/changelog/2026-10-19-some-git-over-https-may-temporarily-require-authentication">unauthenticated HTTPS clones and fetches of public repositories may require authentication</a>, while SSH, authenticated HTTPS and pushes work as before.</p>

<p><a href="https://github.blog/changelog/2026-10-21-github-cli-opt-in-to-expiring-auto-refreshing-oauth-tokens">GitHub CLI 2.103.0</a> adds <code class="language-plaintext highlighter-rouge">gh auth login --expiring</code> for refreshable tokens that expire within hours. Used as a git credential helper, it requires git 2.46 or newer, which discards a cached credential when it expires.</p>

<p>Repositories can now <a href="https://github.blog/changelog/2026-10-20-bulk-migrate-branch-protections-to-rulesets-for-a-repository">convert all their branch protection rules to rulesets</a> in one step, with a preview before anything changes. A new <a href="https://github.blog/changelog/2026-10-13-github-app-improvements-for-least-privilege-and-management"><code class="language-plaintext highlighter-rouge">repository_creation:write</code> permission</a> lets apps and fine-grained tokens create repositories with only that permission instead of full repository administration.</p>

<p>On the Files changed tab of a pull request, the <a href="https://github.blog/changelog/2026-10-22-pull-requests-saved-whitespace-preferences-and-improved-split-view">whitespace visibility setting can be saved</a> so it applies across pull requests, and new and deleted files now span both columns in split view.</p>

<p><a href="https://github.blog/changelog/2026-10-15-email-notifications-for-repository-push-events-have-been-retired">Email notifications for push events</a> have been retired because recipients could be added without consenting.</p>

<h2 id="elsewhere">Elsewhere</h2>

<p><a href="https://try.haxy.net/haxy:haxy">Haxy</a>, now in preview, is a local-first forge written in Zig that stores issues, pull requests and discussions as events on a <code class="language-plaintext highlighter-rouge">haxy/events</code> branch and serves a TUI over SSH alongside its web interface.</p>

<p><a href="https://offby1.website/posts/making-git-hooks-visible-in-fish-shell.html">Making git hooks visible in fish shell</a> (Chris R) ports Ned Batchelder’s zsh function, which lists a repository’s executable hooks when you <code class="language-plaintext highlighter-rouge">cd</code> into it, after Frank Wiles nearly fell for an attack hidden in a shared hooks folder.</p>

<p>jwz has created <a href="https://github.com/xscreensaver-official/xscreensaver">a GitHub repository</a> whose only content is a README stating that XScreenSaver releases are published only as tarballs on the XScreenSaver website and that other repositories are unofficial.</p>

<p>Send links for next week to <a href="https://mastodon.social/@andrewnez">@andrewnez@mastodon.social</a>.</p>]]></content><author><name>Andrew Nesbitt</name><email>andrew@ecosyste.ms</email></author><category term="git" /><category term="weekly" /><category term="twisc" /><summary type="html"><![CDATA[Releases, advisories, and articles from across version control and forges]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://nesbitt.io/images/boxes.png" /><media:content medium="image" url="https://nesbitt.io/images/boxes.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry></feed>