# version-control

Version control is a system that records and manages changes to files or code over time, allowing versions to be recalled, compared, and restored.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Fast Computation of Lowest Common Ancestor in Version Control Commit Graph

DevFeed: [Fast Computation of Lowest Common Ancestor in Version Control Commit Graph](<https://devfeed.tech/articles/fast-computation-of-lowest-common-ancestor-in-version-control-commit-graph-145782.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.25912>)

Author: Stepan Polokhin, Ruslan Savchenko, Yuriy Chernyshov

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Graphs](<https://devfeed.tech/topics/graphs.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>)

Tags: [branch](<https://devfeed.tech/tags/branch.md>), [commit](<https://devfeed.tech/tags/commit.md>), [cs-ds](<https://devfeed.tech/tags/cs-ds.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [data-structures-and-algorithms](<https://devfeed.tech/tags/data-structures-and-algorithms.md>), [fast](<https://devfeed.tech/tags/fast.md>), [version-control](<https://devfeed.tech/tags/version-control.md>)

### AI overview

Finding a merge base in a version control commit graph is difficult because the graph is an arbitrary acyclic graph, and searches can traverse millions of commits when no common ancestor exists. The proposed method identifies "supporting branches," preprocesses the graph around them, and uses this structure to accelerate lowest-common-ancestor queries. When removing those branches leaves connected components of bounded size, a query can take time comparable to searching within one component. The stated running time is O(δ_G m_c + n_s log² n_s + m_s log n_s), with O(d) preprocessed data per vertex; the abstract defines these parameters in terms of component size, supporting-branch reachability, and branch adjacency. The supplied text gives no benchmark results.

### Source excerpt

arXiv:2611.25912v1 Announce Type: cross Abstract: The problem of finding the lowest common ancestor in the commit graph arises when a user wants to merge two (or more) development branches: for example, to add their own development into a common branch. At that moment, the version control system must determine the merge base - the common ancestor of the latest commits of the branches, in order to show the mutual difference between the branches. The problem is complicated by the fact that the commit graph is not a tree but an arbitrary acyclic graph. Moreover, if there is no common ancestor, searching for one may require traversing the entire graph. Traversing a graph with several million vertices takes tens of seconds, which becomes noticeable to users. We show that the commit graph has additional structure - supporting branches - and that this can be used to speed up the algorithm. By extracting supporting branches, the graph can be preprocessed and the search for the lowest common ancestor can be significantly accelerated. Moreover, if removing the supporting branches decomposes the graph into connected components of bounded size, the lowest common ancestor query can be answered in time comparable to searching for a common ancestor within a single component only. We present an algorithm running in time $O(\delta_Gm_c + n_s\log^2 n_s + m_s\log n_s)$ and requiring $O(d)$ preprocessed data per vertex, where $\delta_G$ is the maximum out-degree of a vertex in $G$, $n_c$ and $m_c$ are the maximum numbers of vertices and edges in a connected component formed after removing the supporting branches, $n_s$ is the number of supporting branches, $m_s$ is the number of edges in the reachability graph between the supporting branches, and $d$ is the maximum number of supporting branches adjacent to any single component.

## Integrating AI Coding Agents Into Scientific Research

DevFeed: [Integrating AI Coding Agents Into Scientific Research](<https://devfeed.tech/articles/integrating-ai-coding-agents-into-scientific-research-142179.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23334>)

Author: Rory Barnes

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Data science and engineering](<https://devfeed.tech/topics/data-science-and-engineering.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [also](<https://devfeed.tech/tags/also.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [archive](<https://devfeed.tech/tags/archive.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [astro-ph-im](<https://devfeed.tech/tags/astro-ph-im.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [research](<https://devfeed.tech/tags/research.md>), [scientific-research](<https://devfeed.tech/tags/scientific-research.md>)

### AI overview

AI coding agents can speed up scientific analysis and figure generation, but errors may damage a researcher's computer, increase validation effort, and weaken confidence in results. The paper proposes the six-level PROOF scale, which classifies AI-assisted numerical experiments by provenance, reproducibility, openness, oversight, and falsifiability. Its levels progress from locally self-consistent, version-controlled, human-verified results to a curated public archive with files, change history, prompt transcripts, independent agent regeneration, and cryptographically verifiable attestations. The open-source vaibify package supports this workflow: Docker containers isolate agents, while a GUI lets researchers prompt command-line agents, monitor local and remote file changes, and work toward PROOF Level 3, described as reproducible. The authors suggest these methods may reduce verification time and help communicate trust in AI-assisted science.

### Source excerpt

arXiv:2611.23334v1 Announce Type: new Abstract: New software tools have emerged that enable AI agents to quickly develop code that analyzes data and generates figures, but their mistakes can also harm a researcher's computer, require extensive resources for validation, and cause the results to be received more skeptically. These concerns could be mitigated if scientific software is developed in a secure environment with a system for monitoring file changes and well-defined standards for handling AI agents. This paper first describes how coding agents change eleven aspects of generating, verifying, and reproducing numerical results. A six-level scale is then proposed for classifying AI-assisted numerical experiments by their provenance, reproducibility, openness, oversight, and falsifiability (PROOF). The scale begins with locally self-consistent, version-controlled, human-verified results and culminates in a publicly accessible and curated archive of the files, change history, prompt transcripts, independent agent regeneration of the analysis, and multiple cryptographically verifiable attestations of regeneration by independent researchers. These aspects of AI-assisted scientific software development have been synthesized into a new open source software package called vaibify that optimizes the agentic development of computational experiments ascending the PROOF Ladder. Docker containers sequester the agents while a GUI enables researchers to prompt command line agents, monitor the current status of local and remote files, and drive a project to PROOF Level 3 (reproducible). The methods described in this paper could help researchers reduce the time required to verify agent-written software and efficiently communicate trust in AI-assisted science.

## How Claude Code Agents Accidentally Delete Files--and How to Stop Them

DevFeed: [How Claude Code Agents Accidentally Delete Files--and How to Stop Them](<https://devfeed.tech/articles/how-claude-code-agents-accidentally-delete-files-and-how-to-stop-them-140472.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-claude-code-agents-accidentally-delete-filesand-how-to-stop-them?source=rss>)

Author: Myeongseok Kang

Published: 2026-11-18T05:54:54Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [rsync](<https://devfeed.tech/topics/rsync.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-assistant-risks](<https://devfeed.tech/tags/ai-coding-assistant-risks.md>), [arguments](<https://devfeed.tech/tags/arguments.md>), [bash](<https://devfeed.tech/tags/bash.md>), [bsd](<https://devfeed.tech/tags/bsd.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-code-safety](<https://devfeed.tech/tags/claude-code-safety.md>), [codex](<https://devfeed.tech/tags/codex.md>), [command](<https://devfeed.tech/tags/command.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [drive](<https://devfeed.tech/tags/drive.md>), [echo](<https://devfeed.tech/tags/echo.md>), [empty-variable-deletion](<https://devfeed.tech/tags/empty-variable-deletion.md>), [files](<https://devfeed.tech/tags/files.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [rm-rf](<https://devfeed.tech/tags/rm-rf.md>), [rm-rf-command](<https://devfeed.tech/tags/rm-rf-command.md>), [rm-rf-safety](<https://devfeed.tech/tags/rm-rf-safety.md>), [root](<https://devfeed.tech/tags/root.md>), [rsync](<https://devfeed.tech/tags/rsync.md>), [variable](<https://devfeed.tech/tags/variable.md>)

### AI overview

Three Claude Code incidents show destructive commands deleting data when an empty or root-level path was used: `cygpath` resolved to `/c/`, an unset variable expanded to `/` across WSL shell layers, and an `rm -rf` removed an unpushed `.git` directory. Quoting, `set -u`, and `--preserve-root` did not cover these cases. The excerpt recommends making empty values fail with `${VAR:?}`, printing or validating resolved targets, and moving `.git` aside rather than deleting it. It describes claude-bulkhead 0.4.0 PreToolUse hooks that block several risky `rm`, `rsync --delete`, and macOS `pkill` patterns, while allowing some checked assignments and `${VAR:?}` forms. Because hooks inspect command text, they do not catch destructive commands inside scripts the agent writes and runs; those scripts need their own checks.

### Source excerpt

Three coding agent incidents where an empty variable or a drive-root path turned rm -rf and rsync --delete into deleting /, and the checks that stop it.

## Loop Engineering: Version-Bound, Evidence-Gated Coordination for Production Coding Agents

DevFeed: [Loop Engineering: Version-Bound, Evidence-Gated Coordination for Production Coding Agents](<https://devfeed.tech/articles/loop-engineering-version-bound-evidence-gated-coordination-for-production-coding-agents-137957.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18571>)

Author: Yupeng Pang, Meiling Chen, Yang Yang, Wei Fu

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-loops](<https://devfeed.tech/tags/agent-loops.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-design](<https://devfeed.tech/tags/ai-design.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automated](<https://devfeed.tech/tags/automated.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [commit](<https://devfeed.tech/tags/commit.md>), [context](<https://devfeed.tech/tags/context.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [loop-engineering](<https://devfeed.tech/tags/loop-engineering.md>), [production](<https://devfeed.tech/tags/production.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Loop Engineering coordinates asynchronous coding-agent work through shared auditable repository state. Each loop defines a trigger, context projection, authority boundary, verifier, stop condition, and write-back rule; versioned Skills encode policy, a Harness limits actions and collects evidence, and human gates approve consequential transitions against exact artifact versions. In a production study at MewDesign, five specialized loops handled planning, implementation, review, test release, and reconciliation. Of five pull requests reaching a version-bound test lock, three advanced to test releases with runtime evidence from sources separate from deployment requests, while two stopped before merge. In one drift episode, a new commit invalidated prior approval and evidence, so stale continuous-integration results were not reused. This design-and-experience study is not a controlled benchmark and does not establish causal productivity or general safety; it offers early evidence of feasibility and traceability in one production setting.

### Source excerpt

arXiv:2611.18571v1 Announce Type: new Abstract: Coding agents can edit repositories and execute tests, yet production software work extends far beyond code generation. It requires durable task context, scoped authority, version-aware approval, source-independent verification, interruption recovery, and accountable handoffs between humans and automated workers. We present Loop Engineering, a method for operating multiple asynchronous agent loops over shared, auditable repository state without relying on private conversational handoffs. Each loop is specified by six elements: a trigger, a context projection, an authority boundary, a verifier, a stop condition, and a write-back rule. Versioned procedural contracts, called Skills, encode reusable operating policy; a Harness bounds the available action surface and collects evidence; human gates authorize high-consequence transitions against exact artifact versions. We report a design-and-experience study from MewDesign, a revenue-generating commercial AI design product. Five specialized loops cover planning, scoped implementation, review, test release, and reconciliation. A cross-sectional audit contains 50 durable marker records across 26 GitHub work items. Five pull requests reached a version-bound test lock: three proceeded to test releases with runtime evidence from sources distinct from the deployment request, and two stopped before merge. A detailed drift episode shows one observed fail-closed path: a new commit invalidated prior approval and evidence, and the workflow refused to reuse stale continuous-integration results. The study is not a controlled benchmark and does not establish causal productivity or general safety. It provides early evidence of feasibility, traceability, and bounded progression in one production setting.

## Claude Merged 30,401 Changes in One Day. Git Couldn't Keep Up.

DevFeed: [Claude Merged 30,401 Changes in One Day. Git Couldn't Keep Up.](<https://devfeed.tech/articles/claude-merged-30-401-changes-in-one-day-git-couldn-t-keep-up-131607.md>)

Original publisher: [Read original article](<https://hackernoon.com/claude-merged-30401-changes-in-one-day-git-couldnt-keep-up?source=rss>)

Author: Sidra Zafar

Published: 2026-11-13T07:56:20Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [Git](<https://devfeed.tech/topics/git.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-scion](<https://devfeed.tech/tags/anthropic-scion.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automated](<https://devfeed.tech/tags/automated.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [blob](<https://devfeed.tech/tags/blob.md>), [bonsai](<https://devfeed.tech/tags/bonsai.md>), [branch](<https://devfeed.tech/tags/branch.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [changes](<https://devfeed.tech/tags/changes.md>), [claude](<https://devfeed.tech/tags/claude.md>), [git](<https://devfeed.tech/tags/git.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [scion](<https://devfeed.tech/tags/scion.md>), [source-control](<https://devfeed.tech/tags/source-control.md>), [version-control](<https://devfeed.tech/tags/version-control.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Anthropic reports that its Git mirror fleet could not keep up as Claude-driven changes rose to a peak of 30,401 merges in one day. It replaced Git for its main repository with Scion, an online, server-centered system using local and regional caches, sparse or virtual worktrees, and server-side history queries. In Anthropic's workload, a new agent worktree fell from 7.1 minutes to 5.1 seconds, status checks from 4.3 seconds to under 0.2, and commits from 18 seconds to 761 milliseconds. Scion also removes the global merge queue: changes merge concurrently, with conflicts repaired by Claude, while post-merge and pre-deploy tests provide a later safety net. Anthropic reports 200x smaller infrastructure and 25% lower CI CPU use, but says these are workload-specific results. Scion requires online access, is tied to Anthropic's tools, and is not open source or intended as a general Git replacement.

### Source excerpt

Anthropic swapped git for Scion after Claude hit 30,401 merges a day. A new worktree fell from 7.1 minutes to 5.1 seconds. Here's the full workflow.

## How to Write Professional Git Commit Messages: 4 Essential Rules

DevFeed: [How to Write Professional Git Commit Messages: 4 Essential Rules](<https://devfeed.tech/articles/how-to-write-professional-git-commit-messages-4-essential-rules-130190.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-write-professional-git-commit-messages-4-essential-rules?source=rss>)

Author: William

Published: 2026-11-12T07:00:35Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [atomic](<https://devfeed.tech/tags/atomic.md>), [body](<https://devfeed.tech/tags/body.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-fix](<https://devfeed.tech/tags/bug-fix.md>), [button](<https://devfeed.tech/tags/button.md>), [commit](<https://devfeed.tech/tags/commit.md>), [commits](<https://devfeed.tech/tags/commits.md>), [database](<https://devfeed.tech/tags/database.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [developer](<https://devfeed.tech/tags/developer.md>), [git](<https://devfeed.tech/tags/git.md>), [git-5072-rule](<https://devfeed.tech/tags/git-5072-rule.md>), [git-commit](<https://devfeed.tech/tags/git-commit.md>), [github](<https://devfeed.tech/tags/github.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [messages](<https://devfeed.tech/tags/messages.md>), [professional-github](<https://devfeed.tech/tags/professional-github.md>), [rules](<https://devfeed.tech/tags/rules.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [version](<https://devfeed.tech/tags/version.md>), [version-control](<https://devfeed.tech/tags/version-control.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

The article recommends four practices for readable Git history: write subjects in the imperative mood, as in "Fix bug," so they describe what the commit will do; keep the subject to 50 characters and, when needed, add a body after a blank line wrapped at 72 characters; use Conventional Commit prefixes such as `feat:`, `fix:`, `chore:`, and `refactor:` to categorize changes and support changelog generation and regression tracing; and keep each commit atomic so reverting one change does not undo an unrelated fix. These are presented as conventions the author is learning to apply to a more professional GitHub presence.

### Source excerpt

To write professional GitHub commits, learn to follow the unspoken rules of version control.

## Releases as Code

DevFeed: [Releases as Code](<https://devfeed.tech/articles/releases-as-code-132578.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/11/12/releases-as-code.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-11-12T00:00:00Z

Content type: article

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [automate](<https://devfeed.tech/tags/automate.md>), [code](<https://devfeed.tech/tags/code.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [language](<https://devfeed.tech/tags/language.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [npm](<https://devfeed.tech/tags/npm.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [readme](<https://devfeed.tech/tags/readme.md>), [release](<https://devfeed.tech/tags/release.md>), [release-workflow](<https://devfeed.tech/tags/release-workflow.md>), [releases](<https://devfeed.tech/tags/releases.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [rust](<https://devfeed.tech/tags/rust.md>), [stable](<https://devfeed.tech/tags/stable.md>), [tag](<https://devfeed.tech/tags/tag.md>), [test](<https://devfeed.tech/tags/test.md>), [test-it](<https://devfeed.tech/tags/test-it.md>), [testing](<https://devfeed.tech/tags/testing.md>), [updating](<https://devfeed.tech/tags/updating.md>)

### AI overview

The article argues that release workflows should be treated as testable project code because a partial failure can leave published packages, tags, or development versions inconsistent. It describes npm-package-release, ruby-gem-release, and rust-crate-release, showing lifecycle hooks that update a README's "Release Status" section to identify the stable version at the release tag and the next version on the development branch. Each example tests the actual workflow with project fixtures and checks both versions. The author reports that adopting shared libraries reduced release-related JavaScript and Ruby code by 66% across four cited projects; the excerpt also names projects using the three libraries.

### Source excerpt

A release needs to be reliable, which means it needs to be testable. A typical release selects a version, updates a changelog, builds an artifact, creates a commit and a tag, publishes the package, creates a GitHub Release, and often prepares the next development version. Projects add their own steps, such as updating version references in documentation, and these steps need to agree on what was released. If one breaks, the release fails halfway through, leaving a published package without a matching tag or a development version that wasn't updated. You can't always undo a published package and start over. Test your release code. Releases Are Software I've spent plenty of time maintaining release instructions, shell scripts, and GitHub Actions YAML. They automate the work, but the interesting logic tends to be spread across commands that are hard to exercise without actually making a release. I wanted to treat a release workflow like the rest of the project: write it in code, customize it in code, and test the behavior that matters. This idea has become a family of libraries: npm-package-release, ruby-gem-release, and rust-crate-release. Each brings the workflow into the language of the project it releases. For example, a project's README on the default branch may describe features that haven't been released yet. Grape's README identifies the upcoming version and links to the stable release so users don't confuse the two. After a release, I want the development README to say "You're reading the documentation for the next release, v1.2.3." The README at the release tag should identify the stable version instead. I could do this with a shell script that searches and replaces text, then hope it still works the next time I release. Instead, I can write the release logic in the project's language and test it. Updating the README These examples assume a ## Release Status section in README.md. Each replaces that section during release preparation and again when preparing t

## AI Agents Can Delete Files. Here's How IT Teams Get Them Back.

DevFeed: [AI Agents Can Delete Files. Here's How IT Teams Get Them Back.](<https://devfeed.tech/articles/ai-agents-can-delete-files-here-s-how-it-teams-get-them-back-129377.md>)

Original publisher: [Read original article](<https://www.backblaze.com/blog/ai-agents-can-delete-files-heres-how-it-teams-get-them-back/>)

Author: Kari Wilson

Published: 2026-11-11T16:59:39Z

Content type: article

Language: en

Sources: [Backblaze](<https://devfeed.tech/sources/backblaze-blog-cloud-storage-cloud-backup.md>)

Topics: [backups](<https://devfeed.tech/topics/backups.md>), [Data Recovery](<https://devfeed.tech/topics/data-recovery.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [backblaze](<https://devfeed.tech/tags/backblaze.md>), [backing-up](<https://devfeed.tech/tags/backing-up.md>), [backup](<https://devfeed.tech/tags/backup.md>), [businessbackup](<https://devfeed.tech/tags/businessbackup.md>), [can](<https://devfeed.tech/tags/can.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-backup](<https://devfeed.tech/tags/cloud-backup.md>), [delete](<https://devfeed.tech/tags/delete.md>), [featured](<https://devfeed.tech/tags/featured.md>), [featured-backing-up](<https://devfeed.tech/tags/featured-backing-up.md>), [files](<https://devfeed.tech/tags/files.md>), [first](<https://devfeed.tech/tags/first.md>), [here](<https://devfeed.tech/tags/here.md>), [heres](<https://devfeed.tech/tags/heres.md>), [home](<https://devfeed.tech/tags/home.md>), [it](<https://devfeed.tech/tags/it.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [restore](<https://devfeed.tech/tags/restore.md>), [risk](<https://devfeed.tech/tags/risk.md>), [storage](<https://devfeed.tech/tags/storage.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

AI agents running with a user's permissions can delete files, and recovery depends on a backup the agent could not reach. The article cites reports involving several vendors, while noting that causes and details vary and some remain unconfirmed. Recycle Bin or Trash recovery may fail for command-line deletions; Git covers only committed repository content, sync mirrors deletions, and personal Time Machine or NAS setups may be hard to verify across a fleet. Reduce risk with sandboxes or separate accounts, approval for deletion commands, restricted access, and clear understanding of full-access settings. For recovery, the article recommends automatic off-machine endpoint backup with broad folder coverage, long version history, admin restore controls, managed deployment, and predictable pricing. It describes Backblaze Computer Backup with Enterprise Control as offering automatic Mac and Windows backup, one year of version history, deleted-file retention, centralized restore permissions, deployment through Jamf Pro, Iru, Addigy, and Microsoft Intune, and per-license pricing. It provides recovery points, not a live project mirror, and does not replace Git.

### Source excerpt

AI agents have wiped drives and home folders on real machines. Here is how IT teams reduce the risk and restore files with endpoint backup. The post AI Agents Can Delete Files. Here's How IT Teams Get Them Back. appeared first on Backblaze Blog | Cloud Storage & Cloud Backup

## How Anthropic Redesigned Source Control

DevFeed: [How Anthropic Redesigned Source Control](<https://devfeed.tech/articles/how-anthropic-redesigned-source-control-119199.md>)

Original publisher: [Read original article](<https://blog.bytebytego.com/p/how-anthropic-redesigned-source-control>)

Author: ByteByteGo

Published: 2026-11-04T16:30:59Z

Content type: article

Language: en

Sources: [ByteByteGo](<https://devfeed.tech/sources/bytebytego.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [Git](<https://devfeed.tech/topics/git.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automated](<https://devfeed.tech/tags/automated.md>), [availability](<https://devfeed.tech/tags/availability.md>), [background](<https://devfeed.tech/tags/background.md>), [blob](<https://devfeed.tech/tags/blob.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [branch](<https://devfeed.tech/tags/branch.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [central](<https://devfeed.tech/tags/central.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [changeset](<https://devfeed.tech/tags/changeset.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [scion](<https://devfeed.tech/tags/scion.md>), [source-control](<https://devfeed.tech/tags/source-control.md>)

### AI overview

Scion shifts repository work from independent local Git clones to a shared service because Anthropic's growing monorepo workload made repeated checkouts and mirror maintenance costly. The service handles history queries, diffs, commits, merges, and rebases; clients keep a limited cache and prepare working files, with no separate push step. Changesets record changed files, parent information, and author details; metadata is stored in Spanner and compressed file contents in cloud object storage. Content-addressed immutable objects support shared caching: jobs use a node-level scion-daemon, then a regional scion-cache, then authoritative servers. This reduces repeated downloads and lets jobs request only missing objects. The tradeoff is dependence on service availability and network connectivity. The account describes the architecture and reported scale, but notes it is based on publicly shared details and may contain inaccuracies.

### Source excerpt

In this article, we'll look at the architecture behind Scion.

## I Put My Country's Entire Legal Code in Git: 300,000+ Documents Since 1810

DevFeed: [I Put My Country's Entire Legal Code in Git: 300,000+ Documents Since 1810](<https://devfeed.tech/articles/i-put-my-country-s-entire-legal-code-in-git-300-000-documents-since-1810-112831.md>)

Original publisher: [Read original article](<https://hackernoon.com/i-put-my-countrys-entire-legal-code-in-git-300000-documents-since-1810?source=rss>)

Author: Maximiliano Morel

Published: 2026-11-02T20:15:33Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [search-engines](<https://devfeed.tech/topics/search-engines.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [apis](<https://devfeed.tech/tags/apis.md>), [article](<https://devfeed.tech/tags/article.md>), [building](<https://devfeed.tech/tags/building.md>), [code](<https://devfeed.tech/tags/code.md>), [country](<https://devfeed.tech/tags/country.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [git](<https://devfeed.tech/tags/git.md>), [git-legal-history](<https://devfeed.tech/tags/git-legal-history.md>), [github](<https://devfeed.tech/tags/github.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [law](<https://devfeed.tech/tags/law.md>), [legal](<https://devfeed.tech/tags/legal.md>), [legal-corpus](<https://devfeed.tech/tags/legal-corpus.md>), [legaltech](<https://devfeed.tech/tags/legaltech.md>), [net](<https://devfeed.tech/tags/net.md>), [repo](<https://devfeed.tech/tags/repo.md>), [user-friendly](<https://devfeed.tech/tags/user-friendly.md>)

### AI overview

The project records Chilean legal publications in Git, with one commit per publication, so users can inspect laws and amendments as they stood on a given date. It builds a corpus from BCN's SPARQL catalog and LeyChile's norm and version data, then creates an amendment graph and Git history. The author reports roughly 358,000 cataloged norms, with about 339,000 placed in the main history builder. Git's directory and push limits required workarounds including compressed cache files, split commits, sparse checkout, and date handling for pre-1970 publications. A web interface, API, and read-only MCP server make the corpus searchable; search moved from Meilisearch plus Postgres to Postgres alone after Meilisearch's storage and memory costs and an outage exposed a reliability problem. Postgres uses separate typeahead and deep-search strategies, though common-word results can favor low-ID laws over relevance. Git serves as the history source, while the UI and search infrastructure provide practical access.

### Source excerpt

Building a Git repo from the Chilean law: more than 300,000 legal documents in a corpus that reaches back to 1810. Lots of interesting engineering challenges.

## English Compiles

DevFeed: [English Compiles](<https://devfeed.tech/articles/english-compiles-111313.md>)

Original publisher: [Read original article](<https://joncphillips.com/english-compiles/>)

Author: Jon C. Phillips

Published: 2026-11-02T02:06:00Z

Content type: article

Language: en

Sources: [Jon C. Phillips](<https://devfeed.tech/sources/jon-c-phillips.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2023](<https://devfeed.tech/tags/2023.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [added](<https://devfeed.tech/tags/added.md>), [advice](<https://devfeed.tech/tags/advice.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [articles](<https://devfeed.tech/tags/articles.md>), [audience-building](<https://devfeed.tech/tags/audience-building.md>), [code](<https://devfeed.tech/tags/code.md>), [design](<https://devfeed.tech/tags/design.md>), [digital-products](<https://devfeed.tech/tags/digital-products.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [english](<https://devfeed.tech/tags/english.md>), [english-compiles](<https://devfeed.tech/tags/english-compiles.md>), [files](<https://devfeed.tech/tags/files.md>), [i](<https://devfeed.tech/tags/i.md>), [music](<https://devfeed.tech/tags/music.md>), [photography](<https://devfeed.tech/tags/photography.md>), [product-engineering](<https://devfeed.tech/tags/product-engineering.md>), [project](<https://devfeed.tech/tags/project.md>), [side-projects](<https://devfeed.tech/tags/side-projects.md>), [skills](<https://devfeed.tech/tags/skills.md>), [web-development](<https://devfeed.tech/tags/web-development.md>), [writing-thinking](<https://devfeed.tech/tags/writing-thinking.md>)

### AI overview

The author argues that English instructions shape agent-produced software, so clarity and rigor matter: vague requests such as "follow best practices" invite a model's defaults, while specific, verifiable rules can guide behavior. Effective instructions use concrete nouns, one rule per line, clear completion criteria, and explicit exceptions or limits on the agent's authority. The author recommends maintaining instruction files like code: version them, record why new rules were added, review and prune them regularly, and split long files by concern. Some rules can be enforced with scripts that fail builds or tests. The excerpt also notes that instructions can become stale, contradictory, or too long, and that the author's examples and experience are personal.

### Source excerpt

I counted them last night, a mix of agent instruction files and skills scattered across every project I've touched in the last year or so.

## STORY2DIFF: A Dataset Linking Real-World User Stories to Code Changes

DevFeed: [STORY2DIFF: A Dataset Linking Real-World User Stories to Code Changes](<https://devfeed.tech/articles/story2diff-a-dataset-linking-real-world-user-stories-to-code-changes-107400.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.39872>)

Author: Benedetta Donato, Daniele Franchini, Alessandro Greco, Oliviero Riganelli, Daniela Micucci, Leonardo Mariani

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [User Stories](<https://devfeed.tech/topics/user-stories.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>)

Tags: [automatic](<https://devfeed.tech/tags/automatic.md>), [code](<https://devfeed.tech/tags/code.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [commit](<https://devfeed.tech/tags/commit.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [english](<https://devfeed.tech/tags/english.md>), [file](<https://devfeed.tech/tags/file.md>), [files](<https://devfeed.tech/tags/files.md>), [impact](<https://devfeed.tech/tags/impact.md>), [java](<https://devfeed.tech/tags/java.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [mining](<https://devfeed.tech/tags/mining.md>), [original](<https://devfeed.tech/tags/original.md>), [public](<https://devfeed.tech/tags/public.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [python](<https://devfeed.tech/tags/python.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [traceability](<https://devfeed.tech/tags/traceability.md>), [user-stories](<https://devfeed.tech/tags/user-stories.md>)

### AI overview

STORY2DIFF links 7,785 English user stories to merged pull requests from 982 public Java and Python repositories, covering January 2017 through July 2026. Each record includes the original issue, extracted Connextra elements, pull request and commit metadata, a file-level diff, and affected files before and after the change. Its mining tool can repeat the automatic extraction with different parameters, such as a different timeframe. The dataset is intended to support requirements-to-code research, including requirement discovery, traceability, change-impact estimation, and requirements-aware code generation.

### Source excerpt

arXiv:2610.39872v1 Announce Type: new Abstract: Research on requirements-to-code tasks needs examples in which a genuine requirement is paired with the change that implemented it. Existing user-story collections, however, largely contain isolated or synthetic text. To address this limitation, we present STORY2DIFF, a dataset of 7,785 English user stories linked to merged pull requests from January 2017 to July 2026. The dataset is mined from a set of 982 public Java and Python repositories. Each record in the dataset combines the original issue, extracted Connextra elements, the associated pull request and commit metadata, a file-level diff capturing the code changes introduced by the associated pull request, and the affected files before and after the change. The tool we built to mine STORY2DIFF can be used to repeat the automatic extraction of the records, using different parameters (e.g., a different timeframe). The dataset can support a variety of tasks, including requirement discovery, traceability, change- impact estimation, and requirements-aware code generation. Dataset: https://github.com/riganelli/user-story-mining-pipeline/ releases/tag/V4.0.1. Video: https://youtu.be/qOhXUeyeiTQ.

## Introducing the Quarkus Almanac

DevFeed: [Introducing the Quarkus Almanac](<https://devfeed.tech/articles/introducing-the-quarkus-almanac-107180.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-almanac/>)

Author: Fouad Almalki (https://twitter.com/engineer\_fouad)

Published: 2026-10-29T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [browser](<https://devfeed.tech/tags/browser.md>), [classes](<https://devfeed.tech/tags/classes.md>), [comparisons](<https://devfeed.tech/tags/comparisons.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [history](<https://devfeed.tech/tags/history.md>), [jackson](<https://devfeed.tech/tags/jackson.md>), [java](<https://devfeed.tech/tags/java.md>), [lts](<https://devfeed.tech/tags/lts.md>), [migration-guides](<https://devfeed.tech/tags/migration-guides.md>), [properties](<https://devfeed.tech/tags/properties.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [releases](<https://devfeed.tech/tags/releases.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>)

### AI overview

The Quarkus Almanac compares any two Quarkus releases, covering configuration properties, managed dependencies, extensions, and public or protected API changes. Comparisons summarize change counts and let users inspect relevant sections. Dependency comparisons use platform BOMs when both releases have them; users can switch to core BOMs, which may manage different versions. Release and history pages track changes across releases for properties, artifacts, and classes. The dataset is built from Quarkus artifacts published on Maven Central, updated every twelve hours by a GitHub workflow, and comparisons run in the browser on a static site.

### Source excerpt

Upgrading Quarkus starts with a question: what changed between the release I use and the one I want? The answer is spread over migration guides, release notes, the BOM, the configuration reference, and the code. The Quarkus Almanac puts it in one place. Pick two releases, and it shows what changed between them: config properties, managed dependencies, extensions, and the API of the classes in the Quarkus jars. It covers every Quarkus release, from 0.0.1 to the latest release. The Almanac is inspired by javaalmanac.io, the Java Version Almanac, which collects the history of every Java release and compares the API of any two of them. Compare two releases Pick a release to compare from and a release to compare to. The home page also offers quick comparisons, for example between two LTS releases. A comparison starts with a summary that counts the changes of each kind. The sections below it list the changes, and start collapsed: open the ones you need. Configuration The Configuration section lists the config properties that were added or removed, and those whose default value, type, accepted values, or phase changed, or that were deprecated. The properties are grouped by extension: open an extension to see its changes, or filter by property, extension, or description. Dependencies The Dependencies section compares the versions that the Quarkus BOM manages: major, minor, and patch upgrades, downgrades, and the artifacts that were added or removed. Applications generated by code.quarkus.io import the platform BOM, io.quarkus.platform:quarkus-bom, which sometimes manages other versions than the core BOM, io.quarkus:quarkus-bom. The Almanac compares the platform BOMs when both releases have one; turn off the Platform BOM switch to compare the core BOMs instead. From 3.33.3.3 to 3.33.4, for example, the platform BOM upgrades 68 Jackson artifacts from 2.21.6 to 2.21.7, while the core BOM keeps them at 2.21.6. Extensions The Extensions section lists the extensions that were add

## How Sigma runs a 2,883-model semantic layer on dbt and Dagster

DevFeed: [How Sigma runs a 2,883-model semantic layer on dbt and Dagster](<https://devfeed.tech/articles/how-sigma-runs-a-2-883-model-semantic-layer-on-dbt-and-dagster-102652.md>)

Original publisher: [Read original article](<https://www.getdbt.com/blog/sigma-dbt-dagster-semantic-layer>)

Author: Daniel Poppy

Published: 2026-10-27T18:51:00Z

Content type: news

Language: en

Sources: [dbt Labs](<https://devfeed.tech/sources/dbt-labs.md>)

Topics: [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [analytics-engineering](<https://devfeed.tech/tags/analytics-engineering.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [api](<https://devfeed.tech/tags/api.md>), [applications](<https://devfeed.tech/tags/applications.md>), [building](<https://devfeed.tech/tags/building.md>), [business](<https://devfeed.tech/tags/business.md>), [column](<https://devfeed.tech/tags/column.md>), [company](<https://devfeed.tech/tags/company.md>), [dagster](<https://devfeed.tech/tags/dagster.md>), [dbt](<https://devfeed.tech/tags/dbt.md>), [learn](<https://devfeed.tech/tags/learn.md>), [model](<https://devfeed.tech/tags/model.md>), [models](<https://devfeed.tech/tags/models.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [semantic-layer](<https://devfeed.tech/tags/semantic-layer.md>), [sigma](<https://devfeed.tech/tags/sigma.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Sigma manages its semantic layer as version-controlled SQL and Jinja in a dbt project, using explicit column-level exposure controls and models organized by business function. Three dbt packages compile definitions into Sigma data models, Snowflake semantic views, and Cortex agents. Dagster coordinates 63 jobs across 2,883 dbt models and six regions: jobs download the dbt manifest from S3, run a state-aware dbt build, sync Sigma data models through Sigma's API, and upload the manifest for the next run. Sigma frames the layer as a way to apply model-level AI guardrails, keep metric definitions consistent across AI surfaces, and provide agents with context, synonyms, and verified queries. Senick also previewed Open Semantic Interchange ("Ossie"), intended to enable conversion among Snowflake semantic views, dbt metrics, and Sigma data models.

### Source excerpt

Sigma shows how it manages its semantic layer as version-controlled code across thousands of dbt models.

## AI doesn't remove complexity, it changes where complexity lives

DevFeed: [AI doesn't remove complexity, it changes where complexity lives](<https://devfeed.tech/articles/ai-doesn-t-remove-complexity-it-changes-where-complexity-lives-102696.md>)

Original publisher: [Read original article](<https://kinsta.com/blog/ai-complexity/>)

Author: Carlo Daniele

Published: 2026-10-27T13:00:59Z

Content type: article

Language: en

Sources: [WordPress Guides, Tutorials & Tips - Kinsta® Blog](<https://devfeed.tech/sources/wordpress-guides-tutorials-tips-kinsta-blog.md>)

Topics: [reliable codebases](<https://devfeed.tech/topics/reliable-codebases.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [configuration-management](<https://devfeed.tech/topics/configuration-management.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [agencies](<https://devfeed.tech/tags/agencies.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [apm](<https://devfeed.tech/tags/apm.md>), [backup](<https://devfeed.tech/tags/backup.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [bug](<https://devfeed.tech/tags/bug.md>), [charges](<https://devfeed.tech/tags/charges.md>), [classification](<https://devfeed.tech/tags/classification.md>), [client](<https://devfeed.tech/tags/client.md>), [code](<https://devfeed.tech/tags/code.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [context](<https://devfeed.tech/tags/context.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [crm](<https://devfeed.tech/tags/crm.md>), [crm-integration](<https://devfeed.tech/tags/crm-integration.md>), [demo](<https://devfeed.tech/tags/demo.md>)

### AI overview

AI can speed up building software, but the time saved may shift into review, integration, release, and ongoing support. The article recommends estimating those tasks explicitly: validate behavior against client workflows, permissions, data handling, and failure cases; test in staging with synthetic or sanitized records; document rollback and outside-system effects; and assign someone to verify production after release. Track custom tools, versions, maintainers, and usage so the agency can support or retire them, and scope implementation, testing, handoff, and ongoing maintenance separately. Kinsta is presented as providing a consistent operating environment through MyKinsta staging, backup options, APM, logs, analytics, and user permissions. The article distinguishes ordinary AI-assisted code from live AI model use, which adds classification review, cost monitoring, and provider-change management. DORA findings cited are associations: respondents commonly perceived productivity gains, while AI adoption also showed a negative relationship with delivery stability.

### Source excerpt

Featured image for AI doesn't remove complexity, it changes where complexity lives

## ComBeautify: Leveraging Code Change Summaries for Conventional Commit Generation

DevFeed: [ComBeautify: Leveraging Code Change Summaries for Conventional Commit Generation](<https://devfeed.tech/articles/combeautify-leveraging-code-change-summaries-for-conventional-commit-generation-101769.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.34374>)

Author: Rishi Raj, Aashray Tandon, Nikolay Matyunin, Jibesh Patra

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ccs](<https://devfeed.tech/tags/ccs.md>), [classification](<https://devfeed.tech/tags/classification.md>), [classification-accuracy](<https://devfeed.tech/tags/classification-accuracy.md>), [code](<https://devfeed.tech/tags/code.md>), [commit](<https://devfeed.tech/tags/commit.md>), [commits](<https://devfeed.tech/tags/commits.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [context](<https://devfeed.tech/tags/context.md>), [context-aware-ai](<https://devfeed.tech/tags/context-aware-ai.md>), [conventional-commits](<https://devfeed.tech/tags/conventional-commits.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [generation](<https://devfeed.tech/tags/generation.md>), [git](<https://devfeed.tech/tags/git.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [languages](<https://devfeed.tech/tags/languages.md>), [learn](<https://devfeed.tech/tags/learn.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### AI overview

ComBeautify generates Conventional Commits-compliant messages by summarizing Git diffs with context preserved, then using large language models to classify changes and produce descriptions. It learns category definitions from a project's historical commits instead of relying on generic, manually curated categories. Across 20 popular repositories, the project-specific approach outperformed baselines by up to 3x; on 2,000 manually curated commits, its summarization reached up to 95.25% accuracy and surpassed baselines. A separate analysis of more than 20 million commits across 6,500 repositories and 13 languages found increasing Conventional Commits compliance. The abstract reports these results but does not provide further methodological detail.

### Source excerpt

arXiv:2610.34374v1 Announce Type: new Abstract: Modern software development relies on version control systems such as Git to track changes and facilitate collaboration. While commit messages are crucial for conveying developer intent, they do not affect program functionality; as a result, developers often lack motivation to write meaningful ones. The Conventional Commits Specification (CCS) addresses this with a structured format and guidelines that help developers express the intent of a change, improving clarity and enabling automation. Yet, developers frequently struggle to express intent while adhering to the format. In particular, they may misclassify commits due to the large number of possible categories or the lack of project-specific guidance. We introduce ComBeautify, an approach that automatically generates CCS-compliant commit messages. Our hybrid approach leverages context-preserving summarization of Git diffs with large language models (LLMs) to improve commit classification accuracy under CCS. Rather than relying on manually curated category definitions, we learn them from historical commits. We also propose a method for automatically generating the CCS description component. Our empirical evaluation across 13 languages, 6,500 open-source repositories, and over 20 million commits provides long-term insights into CCS adoption, revealing increasing compliance. Our evaluation on twenty popular repositories reveals the limitations of approaches guided by generic category definitions, and shows that ComBeautify, when trained on project-specific data, outperforms baselines by up to 3x. Additionally, using a dataset of 2,000 manually curated commits, we validate our summarization approach, achieving up to 95.25% accuracy and surpassing baselines. These findings emphasize the need for adaptable, context-aware AI methods for commit classification and CCS-compliant commit message generation.

## Reusing Assurance Evidence in AI Pipelines: Validity Conditions, a Fail-Closed Release Gate, and a Replay of 714 Public Data Version Control Pipelines

DevFeed: [Reusing Assurance Evidence in AI Pipelines: Validity Conditions, a Fail-Closed Release Gate, and a Replay of 714 Public Data Version Control Pipelines](<https://devfeed.tech/articles/reusing-assurance-evidence-in-ai-pipelines-validity-conditions-a-fail-closed-release-gate-and-a-replay-of-714-public-data-version-control-pipelines-93702.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.27672>)

Author: Atanu Mukhopadhyay, Shravya Reddy Nalla

Published: 2026-10-21T04:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [ai security](<https://devfeed.tech/topics/ai-security.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [ai](<https://devfeed.tech/tags/ai.md>), [article](<https://devfeed.tech/tags/article.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-ai](<https://devfeed.tech/tags/artificial-intelligence-ai.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [audit](<https://devfeed.tech/tags/audit.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [control](<https://devfeed.tech/tags/control.md>), [cs-cv](<https://devfeed.tech/tags/cs-cv.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [data](<https://devfeed.tech/tags/data.md>), [gate](<https://devfeed.tech/tags/gate.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [public](<https://devfeed.tech/tags/public.md>), [release](<https://devfeed.tech/tags/release.md>), [version-control](<https://devfeed.tech/tags/version-control.md>)

### AI overview

Safe reuse of AI pipeline assurance evidence requires both complete dependency declarations and a release gate that verifies the evidence matches the candidate. In a replay of 38,083 commits across 714 public DVC pipelines, declared dependencies avoided 83.4% of stage executions but led to stale reuse in 3.3% of commits, affecting 31% of pipelines; an audit found undeclared dependencies in 36 of 40 sampled events. Adding each stage's static import closure reduced stale reuse to 0.4% while still avoiding 81.6% of executions. The reference gate using Ed25519 signatures blocked eight of nine manipulation scenarios, compared with one for a gate trusting the planner and three for a signature-only gate; an undeclared dependency passed all three.

### Source excerpt

arXiv:2610.27672v1 Announce Type: cross Abstract: Rerunning every governance control after every change to an artificial intelligence (AI) pipeline is expensive, so teams reuse earlier results. Reuse is safe only if each control's declared dependencies cover everything that can change its outcome, and only if the release gate checks that reused evidence describes the candidate being released. This article makes both conditions explicit and measures how often the first fails in practice. It defines when a signed evidence record is valid for a candidate and gives sufficient conditions under which change-local re-execution reaches the same release decision as rerunning every control. A reference gate implementing these checks with Ed25519 digital signatures blocks eight of nine manipulation scenarios, against one for a gate that trusts the planner and three for a gate that only verifies signatures; a dependency the policy never declared passes every gate. A replay of 38,083 commits from 714 public Data Version Control (DVC) pipelines measures that failure mode. Reusing stage results according to declared dependencies avoids 83.4% of stage executions, but in 3.3% of commits it reuses a stage whose imported code or referenced configuration changed, and 31% of pipelines are affected. A manual audit confirms the undeclared dependency in 36 of 40 sampled events. Evaluation stages, whose outputs are the evidence, are the most exposed. Adding each stage's static import closure lowers stale reuse to 0.4% while still avoiding 81.6% of executions; sampled shadow re-execution removes far less, and rerunning everything after unexplained changes avoids only 45.3%.

## An online-first version control system in this agentic era

DevFeed: [An online-first version control system in this agentic era](<https://devfeed.tech/articles/an-online-first-version-control-system-in-this-agentic-era-89216.md>)

Original publisher: [Read original article](<https://www.amitmerchant.com/an-online-first-version-control-system/>)

Author: Amit Merchant

Published: 2026-10-17T00:00:00Z

Content type: article

Language: en

Sources: [Amit Merchant](<https://devfeed.tech/sources/amit-merchant.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [Git](<https://devfeed.tech/topics/git.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [ci](<https://devfeed.tech/tags/ci.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [git](<https://devfeed.tech/tags/git.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [miscellaneous](<https://devfeed.tech/tags/miscellaneous.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [version-control](<https://devfeed.tech/tags/version-control.md>)

### AI overview

Anthropic developed Scion, an online-first version control system for its large monorepo and high volume of automated code merges. Unlike Git's decentralized model, Scion relies on a server for repository history and operations while clients access files and objects as needed. The article says this reduced computing demands and checkout time, but Anthropic is not releasing Scion publicly because adapting it for general use would require substantial engineering work.

### Source excerpt

Anthropic recently shared an article explaining a version control system (VCS) that they have been using internally to overcome their own limitations around managing their humongous monorepo.

## Anthropic's Scion version control system handles high-volume code changes with server-side operations

DevFeed: [Anthropic's Scion version control system handles high-volume code changes with server-side operations](<https://devfeed.tech/articles/anthropic-ditched-git-for-its-own-version-control-system-because-claude-is-writing-too-much-code-87839.md>)

Original publisher: [Read original article](<https://www.techspot.com/news/114209-anthropic-ditched-git-own-version-control-system-because.html>)

Author: Skye Jacobs

Published: 2026-10-15T13:43:00Z

Content type: article

Language: en

Sources: [TechSpot](<https://devfeed.tech/sources/techspot.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [devops](<https://devfeed.tech/tags/devops.md>), [git](<https://devfeed.tech/tags/git.md>), [scion](<https://devfeed.tech/tags/scion.md>), [software](<https://devfeed.tech/tags/software.md>), [version-control](<https://devfeed.tech/tags/version-control.md>)

### AI overview

Anthropic replaced Git in its main code repository with Scion as AI-generated changes increased. Scion moves commits, merges, rebases, and file-history queries to servers, while clients track local edits and fetch only needed files. The company reports faster checkouts, lower CPU and memory use, and more CI capacity. It says Scion suits its always-online agents and automated jobs, but requires custom review, search, and CI tools, so Git remains suitable for most repositories.

### Source excerpt

Anthropic detailed the system in a recent engineering post, reporting that it averaged about 2,500 merged code changes a day in May. By September, that figure exceeded 30,000. Read Entire Article

## Anthropic builds Scion source control system for increased AI code production

DevFeed: [Anthropic builds Scion source control system for increased AI code production](<https://devfeed.tech/articles/anthropic-reinvents-source-control-as-claude-floods-the-world-with-code-86609.md>)

Original publisher: [Read original article](<https://developers.slashdot.org/story/26/10/14/0244248/anthropic-reinvents-source-control-as-claude-floods-the-world-with-code>)

Author: BeauHD

Published: 2026-10-14T11:00:00Z

Content type: news

Language: en

Sources: [Slashdot](<https://devfeed.tech/sources/slashdot.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Magic Pocket](<https://devfeed.tech/topics/magic-pocket.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [blob-storage](<https://devfeed.tech/tags/blob-storage.md>), [changeset](<https://devfeed.tech/tags/changeset.md>), [claude](<https://devfeed.tech/tags/claude.md>), [general](<https://devfeed.tech/tags/general.md>), [git](<https://devfeed.tech/tags/git.md>), [has](<https://devfeed.tech/tags/has.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>)

### AI overview

Anthropic says rising volumes of Claude-generated code outpaced its Git-based infrastructure, prompting it to build Scion, a centralized source-control system, with AI-assisted review and search tools. Designed for AI agent workflows, Scion moves more work to the server and exposes source-control queries through an API. Anthropic says the bespoke system is not intended for general use and will not be open-sourced.

### Source excerpt

Anthropic says Claude-generated code has scaled so quickly that its existing Git-based infrastructure could not keep up. In response, the company built a custom centralized source-control system called Scion, along with AI-assisted review and search tools. The Register reports: "In May 2026, Anthropic averaged around 2,500 code changes merged per day; as of September, we merged over 30,000 per day," the biz said in a blog post on Tuesday. "We don't expect this rate of growth to slow down anytime soon; the latent demand for merging code is practically infinite, and every bottleneck we remove immediately leads to a further increase in the amount of code we produce." After several months of model prompting and five months of migration, the result is a homemade version control system called Scion, a monorepo scheme that sounds a bit like Subversion, Apache's centralized version control system. [...] Scion has been designed to meet the needs of AI agents, so the client leaves much of the work to the server; the source control queries are exposed via API so internal tools can respond without needing a local repo, and there's less synchronization but more need for server speed. "In Scion, the unit of work is a 'changeset,' an entry in a write-ahead log," Anthropic explains. "A changeset stores most of what you'd expect from a commit in git. But where a git commit stores a pointer to the tree, a changeset stores a list of the files that changed relative to its first parent, along with content-addressed pointers to the compressed file contents in blob storage." [...] Anthropic says its bespoke system isn't right for general use. There will be no open source release. Nonetheless, the company contends that its own code scaling problems will become commonplace in other organizations over the next few months, so it wanted to share its approach -- having ample funding to pay for writing custom infrastructure tools. Read more of this story at Slashdot.

## Introducing pglifecycle 2.0 beta

DevFeed: [Introducing pglifecycle 2.0 beta](<https://devfeed.tech/articles/introducing-pglifecycle-2-0-beta-86635.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/introducing-pglifecycle-20-beta-3401/>)

Author: Gavin M Roy

Published: 2026-10-14T00:00:00Z

Content type: release

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [Database Migration](<https://devfeed.tech/topics/database-migration.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [bazel](<https://devfeed.tech/topics/bazel.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [database](<https://devfeed.tech/tags/database.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [rust](<https://devfeed.tech/tags/rust.md>), [schema-drift](<https://devfeed.tech/tags/schema-drift.md>)

### AI overview

pglifecycle 2.0 beta is an open source PostgreSQL schema management tool that stores database objects as structured YAML under version control. Its plan first deployment workflow generates SQL for review, with destructive changes withheld unless explicitly allowed, and its GitHub Action can identify schema drift and post plans to pull requests. Version 2 is a Rust rewrite that expands PostgreSQL object coverage and improves deployment convergence and safety.

### Source excerpt

I'm pleased to announce the first public release of pglifecycle, an open source schema management tool for PostgreSQL. pglifecycle keeps your database schema in version control as structured YAML, with one file for each table, view, function, role, and other object. This makes the current schema easy to browse, review, and change without reconstructing it from years of migration files. With pglifecycle, you can: Pull an existing database into a schema project Build that project into an archive for pg_restore Compare it with a live database and generate the DDL needed to reconcile them Deployment is plan first. Destructive changes are withheld unless explicitly allowed, making the generated SQL suitable for review in CI. The companion pglifecycle GitHub Action can detect schema drift and post deployment plans directly to pull requests without applying them. Version 2 is a Rust rewrite of the original tool, which has managed AWeber's production schema for more than seven years. The beta release expands PostgreSQL object coverage and improves deployment convergence and safety. Getting Started Documentation GitHub Action Feedback and real world test cases are welcome as pglifecycle moves toward a stable 2.0 release.

## Redesigning source control at Anthropic

DevFeed: [Redesigning source control at Anthropic](<https://devfeed.tech/articles/redesigning-source-control-at-anthropic-86412.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Oct/13/redesigning-source-control-at-anthropic/>)

Author: Simon Willison

Published: 2026-10-13T23:00:06Z

Content type: article

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agentic-engineering](<https://devfeed.tech/tags/agentic-engineering.md>), [agentic-engineering-66](<https://devfeed.tech/tags/agentic-engineering-66.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-2-279](<https://devfeed.tech/tags/ai-2-279.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-348](<https://devfeed.tech/tags/anthropic-348.md>), [branch](<https://devfeed.tech/tags/branch.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [generative-ai-2-021](<https://devfeed.tech/tags/generative-ai-2-021.md>), [git](<https://devfeed.tech/tags/git.md>), [git-58](<https://devfeed.tech/tags/git-58.md>), [gpt](<https://devfeed.tech/tags/gpt.md>), [hacker](<https://devfeed.tech/tags/hacker.md>), [hacker-news](<https://devfeed.tech/tags/hacker-news.md>), [llms](<https://devfeed.tech/tags/llms.md>), [llms-1-987](<https://devfeed.tech/tags/llms-1-987.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [migrations-15](<https://devfeed.tech/tags/migrations-15.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [version-control](<https://devfeed.tech/tags/version-control.md>), [version-control-13](<https://devfeed.tech/tags/version-control-13.md>)

### AI overview

Anthropic developed Scion, a custom source control system, after its code change rate rose sharply. The article describes Scion's scale, its migration from Git, and the team's use of adversarial review with Claude, including the need for engineers to steer the model away from over-engineering.

### Source excerpt

Redesigning source control at Anthropic Interesting piece from Anthropic describing why and how they built their own custom alternative to Git, based on the dramatic increase in rate of changes to their code after the past six months. In May 2026, Anthropic averaged around 2,500 code changes merged per day; as of September, we merged over 30,000 per day. They included a chart showing those changes. I had Claude modify their chart (code here) to add markers for the public releases of each of their models in 2026: This shows public release dates, not the date when models became available for Anthropic's internal use. My guess is that the introduction of Fable/Mythos class models is a key factor in the increased coding velocity. "Antique" is their new code review system. The source control system is called Scion, and sounds to me like a reinvention of centralized source control along the lines of Subversion. They had some pretty extreme requirements: The history of our main branch alone is almost 100 GB, and a compressed working copy is over 25 GB. We perform on the order of 25 million code checkouts per day for CI, before counting developer environments, agent sandboxes, and research jobs. Fetched naively, that would be over 600 PB of git traffic per day. The new system was built by a team of seven people, and the migration from Git was completed in five months. When asked on Hacker News about the lack of offline support, Scion engineer Nick G replied: Since Claude is by far the heaviest user of Scion and is necessarily online, this just wasn't important to do. As an aside, I've been trying adversarial review in my own projects recently, where you have a model try and find flaws (I often play Claude and GPT off against each other). This note from the article reflected my own experience with that: Anthropic also makes extensive use of adversarial review, and, while this is incredibly effective in many ways, it can also be myopic, so skilled engineers needed to steer Cl

## Dwarf Fortress uses version control now

DevFeed: [Dwarf Fortress uses version control now](<https://devfeed.tech/articles/dwarf-fortress-uses-version-control-now-84600.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Oct/11/dwarf-fortress/>)

Author: Simon Willison

Published: 2026-10-11T00:52:37Z

Content type: article

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [version-control](<https://devfeed.tech/topics/version-control.md>), [Git](<https://devfeed.tech/topics/git.md>)

Tags: [version-control](<https://devfeed.tech/tags/version-control.md>), [version-control-12](<https://devfeed.tech/tags/version-control-12.md>)

### AI overview

Dwarf Fortress creator Tarn Adams did not use version control for many years, describing concerns about commits feeling like a black box. By March 2023, Adams said he had version control work to do, making the development process more involved.

### Source excerpt

I remember hearing a while ago that Dwarf Fortress didn't use version control. That fact has been lodged in my head, because given its inherent complexity I have trouble imagining a codebase that would benefit from version control more. That's art. I went looking and I'm sad to report that the days without version control appear to have ended. Quoting Tarn Adams over time: March 2013: "I don't use version control -- I didn't like the feeling of having the code get committed into a black box thingy with no immediate upside" March 2016: "I don't even use version control. If you don't know what that is then you're not gonna yell at me. If you even know what version control is you're gonna be like, 'You don't use version control? You don't use source control? What is wrong with you? How can you even work? I'm just not cut out for it, in a sense. It's been 15 years, so the reasons have change over time, but that's my current understanding of it." March 2023: "I've got Discord channels to check and version control stuff to use now, so the process is definitely a little more involved" That March 2023 quote comes from an interview about the release on Steam which made them millionaires. I'm a tiny bit sad that they gave in before they hit that milestone, but what an impressive run. Tags: version-control

## 7 Paragon Alternatives for Enterprise AI Agents in 2026

DevFeed: [7 Paragon Alternatives for Enterprise AI Agents in 2026](<https://devfeed.tech/articles/7-paragon-alternatives-for-enterprise-ai-agents-in-2026-90761.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/paragon-alternatives-in-2026>)

Author: Swytchcode Team

Published: 2026-10-05T16:20:00Z

Content type: comparison

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [n8n](<https://devfeed.tech/topics/n8n.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Langgraph](<https://devfeed.tech/topics/langgraph.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [apis](<https://devfeed.tech/tags/apis.md>), [arcade](<https://devfeed.tech/tags/arcade.md>), [code](<https://devfeed.tech/tags/code.md>), [composio](<https://devfeed.tech/tags/composio.md>), [connect](<https://devfeed.tech/tags/connect.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [look](<https://devfeed.tech/tags/look.md>), [n8n](<https://devfeed.tech/tags/n8n.md>), [ownership](<https://devfeed.tech/tags/ownership.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [teams](<https://devfeed.tech/tags/teams.md>), [user](<https://devfeed.tech/tags/user.md>), [workato](<https://devfeed.tech/tags/workato.md>)

### AI overview

Paragon's white-labeled Connect Portal and prebuilt ActionKit actions suit teams seeking a branded integration experience, but its sales-quoted pricing scales with Connected Users and new connections stop at plan limits. The alternatives serve different needs: Nango puts TypeScript integrations in the team's repository; Pipedream Connect offers published pricing and per-user OAuth across a broad catalog; Composio centers on hosted agent tools; Arcade ties user authorization to identity providers; Workato brings agents into enterprise workflows; and n8n supports self-hosted internal workflows. For calls to internal, partner, or legacy APIs, the article presents Swytchcode as a complementary execution layer rather than a portal replacement. It runs on customer-owned infrastructure, applies policy before calls, brokers OAuth, supports human approval and retries designed to avoid duplicate writes, and keeps a local audit trail. Claims and prices are described as checked against vendor sources in October 2026.

### Source excerpt

Why enterprise teams look past Paragon and ActionKit in 2026: connected-user pricing, code ownership, and legacy APIs. Nango, Pipedream Connect, Composio, Arcade, Workato, n8n, and Swytchcode compared.

[Next page](<https://devfeed.tech/topics/version-control.md?cursor=WyIyMDI2LTEwLTA1VDE2OjIwOjAwKzAwOjAwIiwgIjBkN2UyY2M1LTY3NmEtNDUyZi04MTNiLWU4OWRmZGM3NmZkMSJd>)