# Continuous integration

Continuous integration is a software development practice in which code changes are frequently merged into a shared repository and automatically built and tested.

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

## Anticipating Future Build Results with BuildPredictor

DevFeed: [Anticipating Future Build Results with BuildPredictor](<https://devfeed.tech/articles/anticipating-future-build-results-with-buildpredictor-145187.md>)

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

Author: Christian Macho, Katharina Stengg

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

Content type: article

Language: en

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

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Predictive AI](<https://devfeed.tech/topics/predictive-ai.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [changes](<https://devfeed.tech/tags/changes.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [interpretability](<https://devfeed.tech/tags/interpretability.md>), [machine](<https://devfeed.tech/tags/machine.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [model](<https://devfeed.tech/tags/model.md>), [performance](<https://devfeed.tech/tags/performance.md>), [random](<https://devfeed.tech/tags/random.md>), [save](<https://devfeed.tech/tags/save.md>), [testing](<https://devfeed.tech/tags/testing.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

BuildPredictor uses a random forest to predict CI build outcomes from features including source and build code changes, code complexity changes, and historical build results, with the goal of avoiding unnecessary build runs. The abstract reports median MCC scores of 0.82 in an intra-project setting and 0.86 in a holistic setting. Historical build information was most important, but the model still achieved decent performance when those harder-to-interpret features were removed, improving interpretability. It also reportedly reached peak performance quickly over time. The abstract does not specify the evaluated projects or operational criteria for skipping builds.

### Source excerpt

arXiv:2611.26476v1 Announce Type: cross Abstract: Continuous Integration (CI) is a popular programming practice for the seamless integration of code changes into the code base. Using CI, developers benefit from automated assembling and testing of the code after each commit. However, while the frequent integration and building supports developers, it also comes at the high costs of wasting time and resources for minimal changes. In this work, we investigate the potential of reducing the drawbacks by anticipating the build outcome using machine learning techniques. In particular, we propose a random forest model with various features such as changes to the source and build code, and changes to the complexity of the code. We observe that our model shows a good performance in an intra-project and holistic setting yielding a median MCC of 0.82 and 0.86, respectively. We also found that the most important features of our model concern the historical build result information. Additionally, we investigated the development of the performance of our model over time and found that our model can quickly arrive at its peak performance. In an additional experiment, we removed the hard-to-interpret historical build information features and found that our model still yields decent performance while improving the interpretability of it. Summarizing, our model can help to avoid unnecessary build runs by anticipating the build result and thus, save resources.

## CircleCI Expands Smarter Testing to Power Independent Validation for AI-Driven Development

DevFeed: [CircleCI Expands Smarter Testing to Power Independent Validation for AI-Driven Development](<https://devfeed.tech/articles/circleci-expands-smarter-testing-to-power-independent-validation-for-ai-driven-development-144327.md>)

Original publisher: [Read original article](<https://sdtimes.com/software-testing/circleci-expands-smarter-testing-to-power-independent-validation-for-ai-driven-development/>)

Author: SD Times Newswire

Published: 2026-11-19T18:02:50Z

Content type: news

Language: en

Sources: [SD Times](<https://devfeed.tech/sources/sd-times.md>)

Topics: [test impact analysis](<https://devfeed.tech/topics/test-impact-analysis.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [CI/CD Pipeline](<https://devfeed.tech/topics/ci-cd-pipeline.md>), [CircleCI](<https://devfeed.tech/topics/circleci.md>), [auto rerun failed tests](<https://devfeed.tech/topics/auto-rerun-failed-tests.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-powered-customer-service](<https://devfeed.tech/tags/ai-powered-customer-service.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [circleci](<https://devfeed.tech/tags/circleci.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [development](<https://devfeed.tech/tags/development.md>), [dymanic-parallelism](<https://devfeed.tech/tags/dymanic-parallelism.md>), [dynamic-test-splitting](<https://devfeed.tech/tags/dynamic-test-splitting.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [faster](<https://devfeed.tech/tags/faster.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [latest-news](<https://devfeed.tech/tags/latest-news.md>), [newswire](<https://devfeed.tech/tags/newswire.md>), [parallelism](<https://devfeed.tech/tags/parallelism.md>), [platform](<https://devfeed.tech/tags/platform.md>), [smarter-testing](<https://devfeed.tech/tags/smarter-testing.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>), [validation](<https://devfeed.tech/tags/validation.md>)

### AI overview

CircleCI's Smarter Testing suite aims to speed validation and reduce CI compute by running tests affected by a code change and adjusting machine count to match selected work. Developers and AI coding agents can run affected tests locally before pushing at no additional charge; in CI, Intelligent Test Selection selects tests, Dynamic Parallelism adjusts machines, Dynamic Test Splitting balances work, and Auto Rerun retries only failed tests. CircleCI says the suite is built in, with no additional vendor or infrastructure required. Customers report different outcomes: Medallion cites lower cost per pull request and shorter builds as pull request volume grew 10x and its suite 2.5x; Kustomer says test costs fell by a quarter and feedback became faster. These are customer-reported results, not a guarantee of similar savings.

### Source excerpt

SAN FRANCISCO, CA -- CircleCI, a leading continuous integration and continuous delivery (CI/CD) platform, announced new features available in its Smarter Testing suite. Smarter Testing helps engineering teams get faster feedback by running only the tests affected by a code change, and new Dynamic Parallelism adjusts the number of machines for each run to cut... ... continue reading The post CircleCI Expands Smarter Testing to Power Independent Validation for AI-Driven Development appeared first on SD Times.

## MicroVMs, Egress MITM, and sealed tokens: Sandboxing untrusted code at scale

DevFeed: [MicroVMs, Egress MITM, and sealed tokens: Sandboxing untrusted code at scale](<https://devfeed.tech/articles/microvms-egress-mitm-and-sealed-tokens-sandboxing-untrusted-code-at-scale-140598.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/microvms-egress-mitm-and-sealed-tokens-sandboxing-untrusted-code-at-scale>)

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

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [agent-fleet](<https://devfeed.tech/tags/agent-fleet.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [ci](<https://devfeed.tech/tags/ci.md>), [controls](<https://devfeed.tech/tags/controls.md>), [egress](<https://devfeed.tech/tags/egress.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [instant](<https://devfeed.tech/tags/instant.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [mitm](<https://devfeed.tech/tags/mitm.md>), [network](<https://devfeed.tech/tags/network.md>), [results](<https://devfeed.tech/tags/results.md>), [sandboxing](<https://devfeed.tech/tags/sandboxing.md>), [scale](<https://devfeed.tech/tags/scale.md>), [sealed](<https://devfeed.tech/tags/sealed.md>), [startup](<https://devfeed.tech/tags/startup.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

The described CI sandbox runs each job in a hardware-isolated microVM and enforces outbound network policy outside the guest. A gVisor-based layer blocks cloud metadata, private ranges, and loopback, and tears down the VM on the first forbidden connection. The supervisor terminates application traffic and can add credentials in flight; SDKs that need a token receive an ephemeral-key-sealed token that is usable only when sent to an authorized host. The article reports that indexed toolchains are exposed through a lazy virtual filesystem, allowing environments with gigabytes of tools to start in under a second. Jobs are configured declaratively, can be invoked from the CLI, a pre-commit hook, an agent call, or a GitHub webhook, and run in separate microVMs with lockfile checks. Each run yields a signed attestation linking environment, result, and commit for merge-gate verification without rerunning the suite. These are the authors' reported design and performance claims.

### Source excerpt

Chainguard explains the engineering behind secure CI for AI agents, from microVM isolation and network controls to instant startup and signed results.

## 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.

## We have a Slopware Factory

DevFeed: [We have a Slopware Factory](<https://devfeed.tech/articles/we-have-a-slopware-factory-131135.md>)

Original publisher: [Read original article](<https://blog.sentry.io/slopware-factory/>)

Author: David Cramer

Published: 2026-11-12T16:30:00Z

Content type: article

Language: en

Sources: [Sentry](<https://devfeed.tech/sources/sentry-blog.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [board](<https://devfeed.tech/tags/board.md>), [ci](<https://devfeed.tech/tags/ci.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [code](<https://devfeed.tech/tags/code.md>), [commits](<https://devfeed.tech/tags/commits.md>), [context](<https://devfeed.tech/tags/context.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [factory](<https://devfeed.tech/tags/factory.md>), [intern](<https://devfeed.tech/tags/intern.md>), [junior](<https://devfeed.tech/tags/junior.md>), [pr](<https://devfeed.tech/tags/pr.md>), [slack](<https://devfeed.tech/tags/slack.md>), [software](<https://devfeed.tech/tags/software.md>), [software-factory](<https://devfeed.tech/tags/software-factory.md>)

### AI overview

Junior, an open-source Slack-enabled intern, turns a vague request into a pull request by using memory and tools to infer context. In the example, it found prior conversations about a kanban experiment, removed it, and prepared a PR that the author briefly reviewed and approved for auto-merge. The process took about five minutes of the author's time and cost $1.32; Junior handled CI and PR feedback, though the author says they were not notified of any CI failures. The author describes the system as reducing implementation tedium, not as self-improving or fully automated. Results can vary, and the author acknowledges uncertainty about code quality and whether every reference or regression test was handled correctly.

### Source excerpt

What a state of the art software factory looks like this week: Junior, our Slack intern, turns a one-line ask into a merged PR for $1.32.

## Using AI for CI & Automation in iOS Projects \[SUBSCRIBER\]

DevFeed: [Using AI for CI & Automation in iOS Projects \[SUBSCRIBER\]](<https://devfeed.tech/articles/using-ai-for-ci-automation-in-ios-projects-subscriber-129463.md>)

Original publisher: [Read original article](<https://www.kodeco.com/ios/paths/shipping-with-ai/53703840-using-ai-for-ci-automation-in-ios-projects>)

Author: acm0x

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

Content type: tutorial

Language: en

Sources: [Kodeco](<https://devfeed.tech/sources/kodeco-high-quality-programming-tutorials-ios-android-swift-kotlin-unity-and-more.md>)

Topics: [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.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-code](<https://devfeed.tech/tags/ai-code.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automation](<https://devfeed.tech/tags/automation.md>), [ci](<https://devfeed.tech/tags/ci.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [codex](<https://devfeed.tech/tags/codex.md>), [compare](<https://devfeed.tech/tags/compare.md>), [configure](<https://devfeed.tech/tags/configure.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [ios](<https://devfeed.tech/tags/ios.md>), [multimodal-module](<https://devfeed.tech/tags/multimodal-module.md>), [subscriber](<https://devfeed.tech/tags/subscriber.md>)

### AI overview

The module explains how to add agentic AI code review to an iOS continuous integration pipeline and configure GitHub Copilot, OpenAI Codex, and Claude Code for pull request checks. It covers prompts for CI, triaging feedback to prioritize useful findings and discard noise, and judging when human oversight is needed. It also addresses approximate token use and cost; the supplied excerpt does not specify comparative results or exact figures.

### Source excerpt

Learn how to integrate agentic AI code review into a continuous integration pipeline for iOS projects. You'll configure and compare multiple AI-assisted review tools -- GitHub Copilot, OpenAI Codex, and Claude Code -- as automated checks on pull requests, then build a practical framework for triaging the feedback they produce. Along the way, you'll see approximate token usage and cost considerations for running AI agents as part of CI, and learn how to judge when AI-driven review adds reliable value versus when human oversight should take the lead.

## How do we auto-approve and merge 60% of PRs?

DevFeed: [How do we auto-approve and merge 60% of PRs?](<https://devfeed.tech/articles/how-do-we-auto-approve-and-merge-60-of-prs-122498.md>)

Original publisher: [Read original article](<https://swizec.com/blog/how-do-we-auto-approve-and-merge-60p-of-prs>)

Author: hi@swizec.com (Swizec Teller)

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

Content type: opinion

Language: en

Sources: [Swizec Teller](<https://devfeed.tech/sources/swizec-teller.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Risk](<https://devfeed.tech/topics/risk.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [human centric design](<https://devfeed.tech/topics/human-centric-design.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-testing](<https://devfeed.tech/tags/agent-testing.md>), [agents](<https://devfeed.tech/tags/agents.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [getting](<https://devfeed.tech/tags/getting.md>), [i](<https://devfeed.tech/tags/i.md>), [it-s](<https://devfeed.tech/tags/it-s.md>), [merge](<https://devfeed.tech/tags/merge.md>), [review](<https://devfeed.tech/tags/review.md>)

### AI overview

The author argues that reaching 60% auto-merged PRs requires shifting human review toward design and user outcomes, while classifying and automating routine code changes. Their team discusses architecture and product direction before implementation, then tests working features and reviews UX; code review can follow once behavior is verified. Their current bot excludes migrations, public interfaces, finance, and medium- or high-risk changes, while merging approved medium-risk PRs without comments. Proposed changes include finer risk classification, detecting destructive migrations and API contract changes, auto-fixing simple issues, and end-to-end tests for critical flows. A staged process would review direction before coding, use agents and checks during coding, and evaluate behavior afterward, with some noncritical checks potentially deferred for quick follow-up fixes. The author presents these as plans and ideas, not proven results.

### Source excerpt

I'm still drowning in code review. Getting to ~16% auto-approved and merged PRs helped but it's not enough. How can we do 60%?

## Introducing CircleCI Functions: Reusable CI steps built for coding agents

DevFeed: [Introducing CircleCI Functions: Reusable CI steps built for coding agents](<https://devfeed.tech/articles/introducing-circleci-functions-reusable-ci-steps-built-for-coding-agents-117890.md>)

Original publisher: [Read original article](<https://circleci.com/blog/circleci-functions/>)

Author: Kevin Adoboe

Published: 2026-11-04T16:00:00Z

Content type: release

Language: en

Sources: [CircleCI](<https://devfeed.tech/sources/the-circleci-blog-feed-circleci.md>)

Topics: [CircleCI](<https://devfeed.tech/topics/circleci.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [circleci cli](<https://devfeed.tech/topics/circleci-cli.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [cursor](<https://devfeed.tech/topics/cursor.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai-agent-ci-setup](<https://devfeed.tech/tags/ai-agent-ci-setup.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [aws](<https://devfeed.tech/tags/aws.md>), [beta](<https://devfeed.tech/tags/beta.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-config-for-coding-agents](<https://devfeed.tech/tags/ci-config-for-coding-agents.md>), [circleci](<https://devfeed.tech/tags/circleci.md>), [circleci-cli](<https://devfeed.tech/tags/circleci-cli.md>), [circleci-functions](<https://devfeed.tech/tags/circleci-functions.md>), [circleci-news](<https://devfeed.tech/tags/circleci-news.md>), [circleci-orbs](<https://devfeed.tech/tags/circleci-orbs.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [code](<https://devfeed.tech/tags/code.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [command](<https://devfeed.tech/tags/command.md>), [commands](<https://devfeed.tech/tags/commands.md>), [config](<https://devfeed.tech/tags/config.md>), [functions](<https://devfeed.tech/tags/functions.md>), [orbs](<https://devfeed.tech/tags/orbs.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [reusable-ci-steps](<https://devfeed.tech/tags/reusable-ci-steps.md>)

### AI overview

CircleCI Functions are in beta as reusable, version-pinned CI steps that agents can discover and validate before a pipeline runs. They use compiled programs with defined inputs instead of typical orb shell-script commands, enabling specific input errors and platform-specific binaries; a Node setup step compiled to about seven times less configuration than its equivalent orb command. Language setup Functions cache downloads by default, with caches persisting through failed, timed-out, or canceled jobs; caching can be disabled per step. Agents can browse and add Functions through CircleCI CLI and validate configuration before pushing. The beta includes ten CircleCI-maintained Functions, requires CLI 1.8.0 or later for agent discovery, and does not require migration from orbs, which remain supported and usable alongside Functions. The article reports internal tests where agents set up working pipelines up to twice as fast using about 40% fewer tokens; results are company-reported.

### Source excerpt

CircleCI Functions, now in beta, are the next iteration of orbs: tested, versioned CI steps that coding agents can find, call, and validate before a pipeline runs.

## Moving Lightwell patches into production by orchestrating the release lifecycle

DevFeed: [Moving Lightwell patches into production by orchestrating the release lifecycle](<https://devfeed.tech/articles/moving-lightwell-patches-into-production-by-orchestrating-the-release-lifecycle-116372.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/moving-lightwell-patches-production-orchestrating-release-lifecycle>)

Author: Anshul Behl; Tricia McConnell

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

Content type: article

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [ibm red hat project lightwell](<https://devfeed.tech/topics/ibm-red-hat-project-lightwell.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [staging](<https://devfeed.tech/topics/staging.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [application](<https://devfeed.tech/tags/application.md>), [article](<https://devfeed.tech/tags/article.md>), [automation](<https://devfeed.tech/tags/automation.md>), [change](<https://devfeed.tech/tags/change.md>), [change-management](<https://devfeed.tech/tags/change-management.md>), [code](<https://devfeed.tech/tags/code.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [framework](<https://devfeed.tech/tags/framework.md>), [hat](<https://devfeed.tech/tags/hat.md>), [integration](<https://devfeed.tech/tags/integration.md>), [integration-testing](<https://devfeed.tech/tags/integration-testing.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [lightwell](<https://devfeed.tech/tags/lightwell.md>), [moving](<https://devfeed.tech/tags/moving.md>), [patches](<https://devfeed.tech/tags/patches.md>), [production](<https://devfeed.tech/tags/production.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

The article describes how Red Hat Ansible Automation Platform can coordinate the operational steps after CI validates a Lightwell-patched dependency. A CI webhook supplies build, commit, CVE, and change-ticket details; automation syncs the ticket, deploys to staging for integration tests, and pauses for contextual approval. After approval, it drains production traffic, takes a recovery snapshot, deploys and smoke-tests the patch, then either restores traffic and closes the change or automatically rolls back and records failure diagnostics. For OpenShift applications, OpenShift rebuilds and tests the image and OpenShift GitOps promotes it; Ansible handles surrounding steps, including infrastructure outside the cluster. For VM or bare-metal applications, Ansible handles production deployment, approvals, checks, and rollback. The workflow uses existing CI tools and Lightwell's signed, version-specific fixes to avoid requiring major framework or runtime upgrades.

### Source excerpt

In this article:Vulnerability remediation requires more than just merging code: While opening a pull request (PR) updates a dependency, that's not the end of the process. Safely moving that change to production requires integration testing, change management, controlled traffic draining, and patch verification.Lightwell provides stable, backported fixes: Lightwell delivers signed, version-specific binary fixes for eligible application dependencies without forcing major framework or runtime upgrades.Red Hat Ansible Automation Platform orchestrates the release lifecycle, from continuous integrat

## Transformers Model Integration Contracts

DevFeed: [Transformers Model Integration Contracts](<https://devfeed.tech/articles/transformers-model-integration-contracts-114921.md>)

Original publisher: [Read original article](<https://huggingface.co/blog/transformers-mic>)

Author: Tarek Ziadé

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

Content type: article

Language: en

Sources: [Hugging Face](<https://devfeed.tech/sources/hugging-face-blog.md>)

Topics: [Transformers](<https://devfeed.tech/topics/transformers.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [model architecture](<https://devfeed.tech/topics/model-architecture.md>), [ML model versioning](<https://devfeed.tech/topics/ml-model-versioning.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [approach](<https://devfeed.tech/tags/approach.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [attention](<https://devfeed.tech/tags/attention.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [guide](<https://devfeed.tech/tags/guide.md>), [integration](<https://devfeed.tech/tags/integration.md>), [model](<https://devfeed.tech/tags/model.md>), [source](<https://devfeed.tech/tags/source.md>), [transformers](<https://devfeed.tech/tags/transformers.md>)

### AI overview

Transformers' proposed Model Integration Contracts (MICs) use small fixtures derived from real checkpoint configurations to run API usage examples on CPU during PRs. Each contract pins a fixture, a runnable Markdown usage path, and human-reviewed output baselines; CI selects contracts based on changed files and records frozen revisions and package versions. In a five-month replay, a UMT5 fixture caught an SDPA decoder masking regression from its July 30, 2026 introduction through its September 28 fix; eager attention alone missed it. A selected T5 runner step took 13.4 seconds on CPU, excluding setup. Fixtures preserve preprocessing files and original weight formats, and shrink models while retaining layer types. Random weights are preferred when responsive; overfitting a small example can improve sensitivity, though it adds maintenance. In a Whisper study, overfit fixtures caught 24 of 24 synthetic faults versus 18 of 24 for random weights, but both missed an assisted-decoding bug exposed by real weights. As of November 1, 2026, CI reports MIC failures without blocking PRs. Real-world catch rates, false alarms, review effort, real-weight-only bugs, and coverage remain unknown or,

### Source excerpt

We're on a journey to advance and democratize artificial intelligence through open source and open science.

## Onboard your repository to Testing Farm with Claude Code

DevFeed: [Onboard your repository to Testing Farm with Claude Code](<https://devfeed.tech/articles/onboard-your-repository-to-testing-farm-with-claude-code-112342.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/02/onboard-your-repository-testing-farm-claude-code>)

Author: Petr Hracek

Published: 2026-11-02T14:17:25Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [CI/CD Pipeline](<https://devfeed.tech/topics/ci-cd-pipeline.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent-skill](<https://devfeed.tech/tags/agent-skill.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ci-cd](<https://devfeed.tech/tags/agentic-ci-cd.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [bash](<https://devfeed.tech/tags/bash.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-skills](<https://devfeed.tech/tags/claude-skills.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [farm](<https://devfeed.tech/tags/farm.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [repository](<https://devfeed.tech/tags/repository.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The Testing Farm onboarding skill for Claude Code interactively generates TMT/FMF metadata and CI workflows for repositories on GitHub, GitLab.com, and Red Hat internal GitLab. It can inspect existing test setups, guide users through API token and platform choices, and configure GitHub Actions or GitLab CI triggers and target operating system composes. The article's GitHub example adapts existing tox suites, generates .fmf plans and a workflow, then validates plans and tests with `tmt plan lint` and `tmt test lint`. Prerequisites include Claude Code CLI, a Testing Farm API token, Git, and `tmt`; the generated files should be reviewed before committing.

### Source excerpt

Configuring automated testing for open source projects usually means writing boilerplate continuous integration (CI) workflows and wrestling with test metadata by hand. The post Onboard your repository to Testing Farm with Claude Code appeared first on Red Hat Developer.

## Trust Is the Binding Constraint

DevFeed: [Trust Is the Binding Constraint](<https://devfeed.tech/articles/trust-is-the-binding-constraint-109729.md>)

Original publisher: [Read original article](<https://newsletter.kentbeck.com/p/trust-is-the-binding-constraint>)

Author: Kent Beck

Published: 2026-10-30T13:02:54Z

Content type: release

Language: en

Sources: [Software Design: Tidy First?](<https://devfeed.tech/sources/software-design-tidy-first.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [pair\_programming](<https://devfeed.tech/topics/pair-programming.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [ai-workflow](<https://devfeed.tech/tags/ai-workflow.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [class](<https://devfeed.tech/tags/class.md>), [code](<https://devfeed.tech/tags/code.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [continuous-deployment](<https://devfeed.tech/tags/continuous-deployment.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [days](<https://devfeed.tech/tags/days.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [flow](<https://devfeed.tech/tags/flow.md>), [humanity](<https://devfeed.tech/tags/humanity.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [observability](<https://devfeed.tech/tags/observability.md>), [teams](<https://devfeed.tech/tags/teams.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

The author argues that AI speeds up code production while collaboration, testing, review, and shared understanding--the practices that build trust--risk being sacrificed. The advertised live class, The Human Practices Behind Trustworthy Software, presents XP practices such as testing, pairing, continuous integration, and observability as a system for building trust. It also advocates small, verified changes, arguing that code trustworthiness falls with the square of change size, and team-based AI development over solo work. The paid class runs November 9-10, with two-hour lectures and an hour of Q&A each day; sessions are recorded, and exercises are based on participants' teams. The author says it may not be useful for teams that already trust one another and have an effective AI workflow.

### Source excerpt

Teams accumulate code faster than they accumulate trust.

## Omission-Safe Conditional Contracts for Evidence-Closed CI Qualification

DevFeed: [Omission-Safe Conditional Contracts for Evidence-Closed CI Qualification](<https://devfeed.tech/articles/omission-safe-conditional-contracts-for-evidence-closed-ci-qualification-107392.md>)

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

Author: Zhiheng Zhang

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

Content type: article

Language: en

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

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [audit](<https://devfeed.tech/topics/audit.md>), [test](<https://devfeed.tech/topics/test.md>)

Tags: [capture](<https://devfeed.tech/tags/capture.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [ci](<https://devfeed.tech/tags/ci.md>), [collection](<https://devfeed.tech/tags/collection.md>), [conditional](<https://devfeed.tech/tags/conditional.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [development](<https://devfeed.tech/tags/development.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [execution](<https://devfeed.tech/tags/execution.md>), [gate](<https://devfeed.tech/tags/gate.md>), [guards](<https://devfeed.tech/tags/guards.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [job](<https://devfeed.tech/tags/job.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [matrices](<https://devfeed.tech/tags/matrices.md>), [resistance](<https://devfeed.tech/tags/resistance.md>)

### AI overview

The method aims to prevent missing CI evidence from erasing the job requirements that should govern qualification. It compiles conditional requirements from a pinned workflow independently of target presence, keeps a fixed capture inventory, and checks source-complete derivation certificates with a separate implementation. It supports static matrices, dependency guards, and bounded pinned reusable workflows, while preserving unknown applicability and distinguishing tolerated outcomes from evidence coverage. Both implementations matched 45 authorization controls, rejected 180 certificate attacks, and showed no authorization gain across 704 proper development erasures. In a frozen collection of 240 runs across six projects, all 160 source certificates validated, but missing historical execution-source identities meant actual qualification remained open. A repair to unknown propagation brought retrospective diagnosis agreement from 155/160 to 160/160. The results establish bounded source extraction and omission resistance, not natural-fault prevalence or producer authenticity.

### Source excerpt

arXiv:2610.39241v1 Announce Type: new Abstract: Continuous-integration evidence is conditional: a workflow determines which jobs should run, while an archive records which jobs remain observable. Reconstructing requirements from those observations lets an omission erase its own obligation. We present a qualification method that compiles a pinned workflow into conditional job requirements independently of target presence, retains a fixed capture inventory, and checks source-complete derivation certificates with a separate implementation. For a fixed source, context, scope and binding universe, with sound obligations and applicability judgments that preserve established truth under information extension, withdrawing observation facts cannot create authorization. The implementation handles static matrices, dependency guards and bounded pinned reusable workflows, preserving unknown applicability and separating tolerated outcomes from evidence coverage. Both implementations match the 45 hand-specified authorization controls, reject 180 source-certificate attacks, and exhibit no authorization gain over 704 distinct proper development erasures. An explicitly witnessed 12-job platform run qualifies in both implementations; all 4,095 proper payload-subset erasures block authorization. A frozen collection spans 240 runs in eight workflow families across six projects. All 160 evaluation source certificates independently validate, but unavailable historical execution-source identities leave actual qualification open. Initial gate diagnoses agree on 155/160 runs; a preserved unknown-propagation repair yields 160/160 agreement in a retrospective rerun. The study establishes bounded source extraction and omission resistance, rather than natural-fault prevalence or producer authenticity.

## Why are good developers so wary of agentic development?

DevFeed: [Why are good developers so wary of agentic development?](<https://devfeed.tech/articles/why-are-good-developers-so-wary-of-agentic-development-106724.md>)

Original publisher: [Read original article](<https://martinfowler.com/rachels-ramblings/good-devs-wary.html>)

Author: Rachel Laycock (rlaycock@thoughtworks.com)

Published: 2026-10-29T13:50:00Z

Content type: opinion

Language: en

Sources: [Martin Fowler](<https://devfeed.tech/sources/martin-fowler.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [agents](<https://devfeed.tech/tags/agents.md>), [application](<https://devfeed.tech/tags/application.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [behaviour](<https://devfeed.tech/tags/behaviour.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [integration](<https://devfeed.tech/tags/integration.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [rachels-ramblings](<https://devfeed.tech/tags/rachels-ramblings.md>)

### AI overview

Experienced developers' caution about agentic coding reflects uncertainty about production reliability, maintainability and safeguards, not simply reluctance to use assistants. In a week-long experiment where agents wrote all code, the team spent much of its time defining the domain and boundaries, planning work, and building tests, contracts, architecture checks and delivery pipelines into a harness. The application ran, but the build was frequently red, leaving open whether parallel agents, system modularity, or changes outpacing checks caused the instability. The author notes DORA's 2025 finding that AI adoption correlates with higher delivery throughput but lower delivery stability. The experiment did not resolve questions about test-driven development, boundary checks, design upfront, or batch size. Leaders should make room for experiments and judge more than code volume; developers should contribute their experience while testing whether familiar practices still apply. The article's central limitation is that heavily agent-built systems need time in production and through later changes before their reliability is known.

### Source excerpt

TL;DR Good developers' caution about agentic development comes from knowing that built isn't the same as working in production. I've been surprised by how many excellent developers have been hesitant to go all in on coding agents. These are people who usually try new ways of working before anyone else and in many cases invent new tools and practices that support building the application well. So why have we had so much reluctance? The easy (lazy?) answer is that they love writing code, or they're worried about their jobs. I'm sure that's true for some people, some of the time. And I know it is true for some of the developers I talk to but I always felt there was something else, another fear hiding behind those obvious ones. When we put together the Technology Radar every six months I try to block out a chunk of time for us to do an open space. In September, a discussion we had on agentic development, which pushed it to its limits, finally helped me see clearly what that fear is. Building it right Thoughtworkers care deeply about building the right thing and building it right. It's pretty much our default way of working and thinking and it's where many of the practices and technologies we invented and championed came from. We want software that is useful and helpful, can be changed next year, and doesn't fall over in production. Our developers adopted, championed or invented some of the first versions of continuous integration, pairing, automated testing, continuous delivery, microservices and many others early because they helped us build the software right. Early coding agents made it very easy to produce code, including code we wouldn't have wanted anywhere near production, written by people who have not learned about the chasm between building something and making it run in production safely. The tools have improved enormously, but experienced developers still have questions. Are we confident this is the right behaviour? Does it work as expected? Are these the ri

## Meet GroeneAI: our autonomous contributor to ClickHouse

DevFeed: [Meet GroeneAI: our autonomous contributor to ClickHouse](<https://devfeed.tech/articles/meet-groeneai-our-autonomous-contributor-to-clickhouse-106306.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/meet-groeneai-our-autonomous-contributor-to-clickhouse>)

Author: James Cunningham; Artem Brustovetskii; Alex Soffronow Pagonidis

Published: 2026-10-29T12:53:19Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [3](<https://devfeed.tech/tags/3.md>), [agent](<https://devfeed.tech/tags/agent.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [contributed](<https://devfeed.tech/tags/contributed.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>)

### AI overview

ClickHouse's GroeneAI autonomously finds engineering work in CI failures, fuzzing and user reports, then investigates, tests, submits and maintains pull requests; maintainers make acceptance decisions. Built on the open-source Nerve runtime, its workflow preserves task checkpoints and memory across sessions, and uses separate planning, implementation and review phases, including Codex reviews of plans and changes. Examples show both its reach and safeguards: it fixed a query-cache correctness bug with regression tests, while a UNION DISTINCT optimization retained the old plan for one thread after measurements found a slowdown there. Reviewer feedback becomes reusable lessons, and CI fixes remain under verification for at least two days of subsequent master runs. By October 25, 2026, the article reports over 4,400 pull requests opened and over 3,100 merged, with 86.5% of completed decisions resulting in merges.

### Source excerpt

Meet GroeneAI, ClickHouse's autonomous engineering agent that contributed more than 3,000 merged pull requests in under seven months.

## CI Test Suite Slow? 6 Fixes We Measured in Harness

DevFeed: [CI Test Suite Slow? 6 Fixes We Measured in Harness](<https://devfeed.tech/articles/ci-test-suite-slow-6-fixes-we-measured-in-harness-130792.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/flaky-tests-slow-ci-pipeline>)

Author: Shibam Dhar

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

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [test impact analysis](<https://devfeed.tech/topics/test-impact-analysis.md>), [dynamic test splitting](<https://devfeed.tech/topics/dynamic-test-splitting.md>), [intermittent failures](<https://devfeed.tech/topics/intermittent-failures.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [added](<https://devfeed.tech/tags/added.md>), [after](<https://devfeed.tech/tags/after.md>), [ci](<https://devfeed.tech/tags/ci.md>), [flaky](<https://devfeed.tech/tags/flaky.md>), [harness](<https://devfeed.tech/tags/harness.md>), [intelligence](<https://devfeed.tech/tags/intelligence.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [lab](<https://devfeed.tech/tags/lab.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [sharding](<https://devfeed.tech/tags/sharding.md>), [state](<https://devfeed.tech/tags/state.md>), [test](<https://devfeed.tech/tags/test.md>), [time](<https://devfeed.tech/tags/time.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

In a controlled Harness lab, the full pipeline took about 100 seconds while Vitest ran in about 2 seconds, with initialization varying from 6 to 42 seconds. Measure pipeline steps before optimizing the test runner. Retries can make flaky tests appear green; the Harness Test Analysis Plugin can quarantine named failures while still rejecting failures absent from the quarantine list. Its demonstration used deliberate failures and did not test automatic flake detection. Isolate mutable test state before adding concurrency: fresh state changed four tests from two failures to four passes. Two shards did not speed up this small suite because initialization dominated. npm caching worked after using `/harness/.npm`, but restore took eight seconds and the warm install saved one second, so measure the full cost. In a separate Java/JUnit fixture, Harness Test Intelligence selected 17 of 21 tests after a change to DiscountEngine.java, skipping four unrelated tax tests; the time saving on this small suite was negligible. The lab recommends fixing determinism first, then measuring whether caching, sharding, or change-aware selection pays off. These results are from controlled examples, not a way

### Source excerpt

CI performance lab measuring test time vs pipeline time, flaky test quarantine, shared-state isolation, parallel sharding and Harness Test Intelligence. | Blog

## A Shared Language for Agent Defense: Introducing Project Quarry

DevFeed: [A Shared Language for Agent Defense: Introducing Project Quarry](<https://devfeed.tech/articles/a-shared-language-for-agent-defense-introducing-project-quarry-104463.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/ai/project-quarry-agent-security-detections>)

Author: Adam Swanda

Published: 2026-10-28T12:45:39Z

Content type: article

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-frameworks](<https://devfeed.tech/tags/agent-frameworks.md>), [agent-runtimes](<https://devfeed.tech/tags/agent-runtimes.md>), [agent-security](<https://devfeed.tech/tags/agent-security.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-security](<https://devfeed.tech/tags/ai-security.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [artificial-intelligence-ai](<https://devfeed.tech/tags/artificial-intelligence-ai.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [audio](<https://devfeed.tech/tags/audio.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [base64](<https://devfeed.tech/tags/base64.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [defense](<https://devfeed.tech/tags/defense.md>), [language](<https://devfeed.tech/tags/language.md>), [open](<https://devfeed.tech/tags/open.md>), [project](<https://devfeed.tech/tags/project.md>)

### AI overview

Project Quarry is an open-source detection language and engine for evaluating agent behavior across session traces. Rules combine machine-learning judgments with exact checks, can inspect tool calls, results, metadata, and multimodal signals, and can detect relationships that emerge over multiple steps. Matches return supporting evidence, which a product can map to alerts or actions such as blocking or redacting. Quarry complements per-action authorization, classifiers, and middleware; it does not replace them. Teams can scan stored traces, tune rules with exemptions, and integrate them at runtime. Rules compile on load and can be versioned and tested against matching and benign examples. Its coding-agent plugin can draft and test rules, but the authors recommend human review before enforcement. Quarry is already in production in Cisco AI Defense; other described integrations are planned and may change.

### Source excerpt

AI agents now read, decide, and act on their own, and the attacks against them unfold across many ordinary, permitted steps that most of today's defenses were not built to connect. Project Quarry ("Quarry"), which we are open sourcing today, is a...

## Part 3: From CI to Gating -- Validating Downstream OpenStack with Zuul

DevFeed: [Part 3: From CI to Gating -- Validating Downstream OpenStack with Zuul](<https://devfeed.tech/articles/part-3-from-ci-to-gating-validating-downstream-openstack-with-zuul-104604.md>)

Original publisher: [Read original article](<https://superuser.openinfra.org/articles/how-kt-cloud-connected-upstream-openstack-validation-assets-to-its-downstream-workflow-with-zuul-project-gating-keeping-local-changes-aligned-with-community-quality-standards/>)

Author: Geonhee Kim

Published: 2026-10-28T07:00:04Z

Content type: article

Language: en

Sources: [Superuser](<https://devfeed.tech/sources/superuser.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [openstack](<https://devfeed.tech/topics/openstack.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [code](<https://devfeed.tech/tags/code.md>), [digital-sovereignty](<https://devfeed.tech/tags/digital-sovereignty.md>), [openstack](<https://devfeed.tech/tags/openstack.md>), [operator](<https://devfeed.tech/tags/operator.md>), [ovn](<https://devfeed.tech/tags/ovn.md>), [sovereign-cloud](<https://devfeed.tech/tags/sovereign-cloud.md>), [technical-deep-dive](<https://devfeed.tech/tags/technical-deep-dive.md>), [validating](<https://devfeed.tech/tags/validating.md>), [validation](<https://devfeed.tech/tags/validation.md>), [zuul](<https://devfeed.tech/tags/zuul.md>)

### AI overview

kt cloud's KTC Gating System uses Zuul to require validation before downstream OpenStack changes merge, inheriting upstream jobs as the quality baseline while specifying downstream repositories and release targets. Its Kubernetes-hosted control plane coordinates pipelines, and an OpenStack resource provider supplies isolated, ephemeral VMs for job execution. Validation spans Python unit and Tox checks, DevStack environment setup, Tempest functional tests, Rally performance and regression checks, and Helm/GeneStack deployment validation. This approach reuses evolving upstream procedures instead of maintaining copied test logic, while allowing targeted KCP-specific checks. The system is still early and focused on OpenStack code; kt cloud says it has not yet demonstrated blocking production regressions. Planned work includes integrated testing closer to KCP architecture.

### Source excerpt

If Part 1 explored network sovereignty--the ability to explain traffic paths and security policy--Part 2 turns to validation sovereignty: the ability to explain code changes and the quality criteria behind them. For an operator running its own cloud platform, sovereignty depends not only on which changes enter the operational baseline, but also on how those [...]

## Skill Dreaming: Evolving Repository Skills through Pull Request Streams

DevFeed: [Skill Dreaming: Evolving Repository Skills through Pull Request Streams](<https://devfeed.tech/articles/skill-dreaming-evolving-repository-skills-through-pull-request-streams-103097.md>)

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

Author: Xinyuan Song, Hasibul Haque, Jay Somasundaram, Ryan Turner, Bowen Zhu, Liang Zhao

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

Content type: article

Language: en

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

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [components](<https://devfeed.tech/tags/components.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [development](<https://devfeed.tech/tags/development.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [library](<https://devfeed.tech/tags/library.md>), [llm](<https://devfeed.tech/tags/llm.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [repository](<https://devfeed.tech/tags/repository.md>), [skills](<https://devfeed.tech/tags/skills.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [streams](<https://devfeed.tech/tags/streams.md>)

### AI overview

Skill Dreaming proposes a feedback loop between repository pull requests and coding-agent skills. It extracts executable knowledge from validated PRs to build repository-specific skill libraries, then refines those skills as new PR information arrives. The skills guide implementation while accounting for repository conventions, related components, tests, documentation, and compatibility. The framework combines PR analysis, skill management, code execution, and continuous integration so PR outcomes can inform later skill updates. The supplied text describes the proposal but gives no evaluation results or comparative evidence.

### Source excerpt

arXiv:2610.36188v1 Announce Type: new Abstract: Large language model (LLM) agents increasingly rely on reusable skills for complex software engineering tasks, making skill libraries essential for repository development and maintenance. However, repository-specific skills must evolve with changing code structures, implementation conventions, and maintenance requirements. Pull requests (PRs) provide a natural source of such knowledge by recording how repositories evolve through implementation and review. Meanwhile, new PRs must follow repository-specific implementation patterns, modify related components consistently, and ensure that existing tests continue to pass while adding coverage for new functionality. This creates a mutually reinforcing cycle: PRs provide knowledge for updating skills, while these skills improve future PRs, maintain repositories, and support further skill evolution. To enable this co-evolution of PRs, repositories, and skills, we propose Skill Dreaming, a framework that learns from PR streams to guide continuous repository development and maintenance. Given a repository and its PR history, Skill Dreaming builds a repository-specific skill library by extracting executable knowledge from validated PRs and continuously refines the skills as new PR information becomes available. These skills guide coding agents not only in implementing requested features but also in maintaining associated tests, documentation, compatibility, and repository conventions. By integrating PR analysis, skill management, code execution, and continuous integration, Skill Dreaming provides an end-to-end workflow for applying learned skills to repository changes and incorporating subsequent PR outcomes into future skill updates.

## Lukewarm recommendations for improving AI agents' interactions with your projects

DevFeed: [Lukewarm recommendations for improving AI agents' interactions with your projects](<https://devfeed.tech/articles/lukewarm-recommendations-for-improving-ai-agents-interactions-with-your-projects-100137.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/25/renovate-agent-improvements/>)

Author: Jamie Tanna

Published: 2026-10-25T17:25:54Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [context-architecture](<https://devfeed.tech/topics/context-architecture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [claude](<https://devfeed.tech/tags/claude.md>), [code](<https://devfeed.tech/tags/code.md>), [code-style](<https://devfeed.tech/tags/code-style.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [development](<https://devfeed.tech/tags/development.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [llm](<https://devfeed.tech/tags/llm.md>), [projects](<https://devfeed.tech/tags/projects.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [standard](<https://devfeed.tech/tags/standard.md>), [standards](<https://devfeed.tech/tags/standards.md>), [structure](<https://devfeed.tech/tags/structure.md>), [style](<https://devfeed.tech/tags/style.md>), [things](<https://devfeed.tech/tags/things.md>)

### AI overview

Renovate found that a predictable codebase and contributor documentation helped agents produce mostly technically correct code even before AI-specific changes. The author recommends keeping AGENTS.md or CLAUDE.md brief and directing agents to fuller development standards; providing a single `check` command for CI-like checks, including selected-file and no-test modes; and using a Claude Code `Stop` hook to require checks before an agent finishes. Common review complaints can be encoded as lint rules. Renovate uses `mise` and a Claude Code `PreToolUse` hook to steer agents toward required tools such as pnpm and Vitest; cloud agents then need less preinstalled software. The author also reports better results by having Claude Sonnet review and improve code produced by Amp's Claude Opus, at the cost of more tokens. These practices are presented as useful to human contributors as well as agents.

### Source excerpt

Over the last week I've been chatting with some folks who are looking at integrating AI more into their development work. I shared a couple of things that we've found have worked well for Renovate, as a codebase that takes a lot of human (and since mid-last year, AI) contributions. Although I've written about this a bit in my reflection on the last year, this naturally deserves its own blogumentation. Before we did anything to explicitly optimise the codebase for AI agents, we ended up finding that we'd - for the most part - receive fairly technically correct code, although it wouldn't necessarily fit in the areas that it was added for, or wouldn't completely fit our code style, but would handle a lot of file-directory architecture choices. We credit this down to the fact that we've structured our codebase in a predictable and - in my opinion, reasonable - structure, which has been optimised for the humans who are interacting with it. As well as this, we've also had documentation for new contributors to understand how best to get started, which also helps the agents! I've called this a "lukewarm" set of recommendations because for anyone who's fairly invested in doing work with AI agents, these are going to feel like so last $timePeriod. I appreciate that they're not ground breaking, but they're useful for folks who may be earlier in their AI journey than others. These recommendations build on great work that Sergei Zharinov and Sebastian Poxhofer - as well as a few other folks - have been doing. AGENTS.md / CLAUDE.md I'm largely adding this for completeness - it's a fairly standard recommendation that you'll get from most people, but the interesting angle we've got is that it doesn't need to be exhaustive. You can see that we've barely updated AGENTS.md since adding it in May, but we have made many docs edits for our "development standards" documentation. These docs were originally built for human readers, and are still our recommended area for this information to

## Beyond API Compatibility: Building a Tool to Measure the Blast Radius of Library Changes

DevFeed: [Beyond API Compatibility: Building a Tool to Measure the Blast Radius of Library Changes](<https://devfeed.tech/articles/beyond-api-compatibility-building-a-tool-to-measure-the-blast-radius-of-library-changes-98391.md>)

Original publisher: [Read original article](<https://netflixtechblog.com/beyond-api-compatibility-building-a-tool-to-measure-the-blast-radius-of-library-changes-9474f2fd4f90?source=rss----2615bd06b42e---4>)

Author: Netflix Technology Blog

Published: 2026-10-23T18:32:51Z

Content type: article

Language: en

Sources: [Netflix](<https://devfeed.tech/sources/netflix-techblog-medium.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [deprecated](<https://devfeed.tech/topics/deprecated.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [code-analysis](<https://devfeed.tech/tags/code-analysis.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [impact](<https://devfeed.tech/tags/impact.md>), [java](<https://devfeed.tech/tags/java.md>), [java-libraries](<https://devfeed.tech/tags/java-libraries.md>), [library](<https://devfeed.tech/tags/library.md>), [migration](<https://devfeed.tech/tags/migration.md>), [netflix](<https://devfeed.tech/tags/netflix.md>), [quasar](<https://devfeed.tech/tags/quasar.md>), [release](<https://devfeed.tech/tags/release.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [risk](<https://devfeed.tech/tags/risk.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

Quasar links API changes to observed symbol references across Netflix repositories, helping library producers estimate downstream impact before merge or release. It indexes definitions and references using SCIP, compares API snapshots for commits, and queries affected repositories, dependency versions, and sample source locations. Compatibility tools identify contract changes but not actual users; dependency graphs show declared reach, and broad consumer builds are costly. Quasar reports observed reach without enforcing release policy: missing references do not prove safety, since reflection, stale branches, or incomplete indexing can hide consumers. Results depend on indexed commits and fresh coverage. It compares JVM APIs and traces Protobuf changes through generated Java; usage queries cover JVM, Go, Python, JavaScript/TypeScript, and Rust, while breaking-change assessment remains limited to JVM and Protobuf. Producers use the evidence to choose steps such as retaining and deprecating an API, publishing a migration path, or coordinating consumers.

### Source excerpt

By Roberto Perez Alcolea, Java Platform Team Quasar connects a proposed API change with observed references in consumer repositories, giving the producer evidence for a release decision At Netflix, shared Java libraries support applications developed across a large, independently evolving repository ecosystem. A library change begins in one repository, but its impact can reach many others. Producers can see the API diff in front of them. What they often cannot see is who still depends on the symbols that changed. The need for that visibility grows as coding agents take on more of the software development lifecycle. An agent can accelerate a local edit, but without cross-repository context it cannot judge downstream risk or help plan consumer migrations. The evidence a producer uses to assess a change can also guide the agent working on it. Consider a common case: removing a deprecated API. Deprecated entry points expand the surface producers must test, document, and support, and they can constrain how a library evolves. Suppose a replacement has been available for several releases and the old method cannot express options required by new behavior. The library's tests pass, and a compatibility checker flags the removal. The producer still cannot answer the questions that determine what to do next: Does any consumer still call this method? Are consumers concentrated on one version or spread across several generations? Does another library implement or wrap the API, multiplying its impact? Is direct coordination sufficient, or does this require a deprecation and migration campaign? At small scale, producers can ask nearby teams or search a handful of repositories. Across many repositories, it is harder to find every caller of a method and the library version each one uses. Those answers are scattered across consumer codebases and builds. Without that evidence, a producer may release a breaking change and discover the impact through consumer failures, or preserve an old

## I Am Just One Engineer Armed with AI

DevFeed: [I Am Just One Engineer Armed with AI](<https://devfeed.tech/articles/i-am-just-one-engineer-armed-with-ai-98269.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/10/23/i-am-just-one-engineer-armed-with-ai.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

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

Content type: opinion

Language: en

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

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [bot](<https://devfeed.tech/tags/bot.md>), [bug](<https://devfeed.tech/tags/bug.md>), [ci](<https://devfeed.tech/tags/ci.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [danger](<https://devfeed.tech/tags/danger.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [email](<https://devfeed.tech/tags/email.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [features](<https://devfeed.tech/tags/features.md>), [github](<https://devfeed.tech/tags/github.md>), [github-issue](<https://devfeed.tech/tags/github-issue.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [mongoid](<https://devfeed.tech/tags/mongoid.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [numbers](<https://devfeed.tech/tags/numbers.md>), [october](<https://devfeed.tech/tags/october.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [performance](<https://devfeed.tech/tags/performance.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [rust](<https://devfeed.tech/tags/rust.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Across ten days, the author reports 295 pull requests in 49 repositories, 257 merged, and 30 releases, spanning library features, maintenance, spelling tools, and app upgrades. Three spelling tools for Ruby, Rust, and JavaScript integrate with each language's lint workflow; the first two use Kotoshu and the JavaScript rule uses CSpell. Checking 618 Markdown files reportedly fell from over three minutes to 3.69 seconds. Other work included Hashie features and releases, provider-aware email parsing, GitHub issue automation, and Mongoid fixes found through legacy and modern compatibility testing. Eleven chat bots were upgraded after CVEs. The author says AI handled much of the typing, while they selected work, checked reproductions, reviewed changes, managed compatibility and release decisions, and drew on decades of programming experience to steer it. Usage records, after removing duplicates, totaled about 1.196 billion input-plus-output tokens, 97.4% of input tokens cache reads. These figures and examples come from the supplied excerpt.

### Source excerpt

I made 295 pull requests across 49 GitHub repos and did 30 project releases burning ~1.2 billion AI tokens in ten days. I am just one Engineer armed with AI. That is a lot of typing I did not do. I certainly did not read or write any code. This is a follow-up to AI Wants to Eat Your Project Backlog, where I described working through old Mongoid issues on two bus rides. I kept going. The work expanded into new spelling tools in three languages, library features, CI maintenance, releases, and application upgrades. First, let's count what actually happened. Then let's talk about what these numbers mean, or don't. The Numbers These are ten calendar dates, October 14 through October 23, 2026, with a cutoff of October 23 at 1:32 p.m. Eastern. measure count what it means opened 295 authored by dblock repositories 49 includes forks merged 257 of the 295 opened still open 30 awaiting review or further work closed unmerged 8 includes superseded work and approaches I abandoned all prs merged 271 includes 14 older PRs releases 30 across 22 repositories issues opened 27 new work and follow-ups The complete PR inventory includes every title, repository, URL, status, and category. The release inventory includes all 30 release links. GitHub's authored PR search and merged PR search are useful receipts, although their results will keep changing. The Work I assigned every PR to one category based on its repository. This avoids counting a PR three times because it contains a bug fix, tests, and documentation. category opened merged open abandoned mongoid ecosystem 119 97 19 3 three new spelling tools 60 60 0 0 hashie 31 27 0 4 email libraries 26 26 0 0 danger and maintainer automation 19 17 2 0 upstream integrations, examples, and this blog 16 6 9 1 github issue action 13 13 0 0 bot application upgrades 11 11 0 0 total 295 257 30 8 The work itself fell into several different kinds of engineering: new features, bug archaeology, regression coverage, compatibility testing, performance, A

## Code testing startup Blacksmith becomes a unicorn after raising $66M in Series C funding

DevFeed: [Code testing startup Blacksmith becomes a unicorn after raising $66M in Series C funding](<https://devfeed.tech/articles/code-testing-startup-blacksmith-becomes-a-unicorn-after-raising-66m-in-series-c-funding-94026.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/10/21/code-testing-startup-blacksmith-becomes-a-unicorn-after-raising-66m-in-series-c-funding/>)

Author: Mike Wheatley

Published: 2026-10-22T02:02:17Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [apps](<https://devfeed.tech/tags/apps.md>), [blacksmith](<https://devfeed.tech/tags/blacksmith.md>), [ci-cloud](<https://devfeed.tech/tags/ci-cloud.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code-checks](<https://devfeed.tech/tags/code-checks.md>), [code-testing](<https://devfeed.tech/tags/code-testing.md>), [code-validation](<https://devfeed.tech/tags/code-validation.md>), [coding-assistants](<https://devfeed.tech/tags/coding-assistants.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [funding](<https://devfeed.tech/tags/funding.md>), [news](<https://devfeed.tech/tags/news.md>), [series-c](<https://devfeed.tech/tags/series-c.md>), [software-testing](<https://devfeed.tech/tags/software-testing.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [unicorn](<https://devfeed.tech/tags/unicorn.md>)

### AI overview

Blacksmith raised $66 million in a Series C led by Sequoia Capital, bringing its reported valuation to $1 billion and total funding to $125 million. Founded in 2024, it runs customers' continuous integration jobs on dedicated servers across multiple locations, with its own software automating setup work. The company says owning its hardware helps it control performance and handle sharply fluctuating workloads, but leaves it exposed to component shortages and makes capacity planning difficult as AI coding tools drive more code validation. Blacksmith reports that customers grew from about 5,000 in August to more than 10,000, weekly code checks rose from about 5 million to 90 million in early 2026, and annual recurring revenue increased 17-fold over that period. It plans to spend most of the new funding on servers and grow its team from about 40 to 75 by year's end. The text also notes that AI model vendors could take on code validation themselves, posing a potential competitive risk.

### Source excerpt

Blacksmith Software Inc., a continuous integration cloud startup that helps companies to test and verify new code before they ship it into production, says it's now valued at $1 billion after closing on a $66 million Series C round of funding today. The round was led by Sequoia Capital and saw participation from Peak XV [...] The post Code testing startup Blacksmith becomes a unicorn after raising $66M in Series C funding appeared first on SiliconANGLE.

## How Hamlet uses Databricks Lakebase Postgres to test changes against production data

DevFeed: [How Hamlet uses Databricks Lakebase Postgres to test changes against production data](<https://devfeed.tech/articles/how-hamlet-uses-databricks-lakebase-postgres-to-test-changes-against-production-data-91067.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/how-hamlet-uses-databricks-lakebase-postgres-test-changes-against-production-data>)

Author: Sara Steffen

Published: 2026-10-20T14:45:00Z

Content type: news

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [databricks](<https://devfeed.tech/topics/databricks.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [sql-database](<https://devfeed.tech/topics/sql-database.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>), [AI-Ready Data](<https://devfeed.tech/topics/ai-ready-data.md>), [Data analysis](<https://devfeed.tech/topics/data-analysis.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [changes](<https://devfeed.tech/tags/changes.md>), [company](<https://devfeed.tech/tags/company.md>), [customers](<https://devfeed.tech/tags/customers.md>), [data](<https://devfeed.tech/tags/data.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [decision-making](<https://devfeed.tech/tags/decision-making.md>), [government](<https://devfeed.tech/tags/government.md>), [lakebase](<https://devfeed.tech/tags/lakebase.md>), [local](<https://devfeed.tech/tags/local.md>), [platform](<https://devfeed.tech/tags/platform.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [production](<https://devfeed.tech/tags/production.md>), [test](<https://devfeed.tech/tags/test.md>), [uses](<https://devfeed.tech/tags/uses.md>)

### AI overview

Hamlet creates a Lakebase Postgres branch of production data for each pull request, linked to its preview environment. Engineers and AI coding agents can run pipelines and test fixes against the data that exposed a bug without affecting production; a person still approves every merge, and schema changes reach the parent through code migrations. Hamlet says this replaced 15-30 minutes of staging setup per pull request and several hours per engineer each week spent maintaining test data. Lakebase branches start with the parent's schema and data and use copy-on-write, while standard Postgres database creation copies data. Branch compute scales to zero when idle. Expiring branches are billed for changed data; permanent branches without expiration are billed for their full data size.

### Source excerpt

Hamlet, an AI-powered platform that makes local government decision-making accessible...

[Next page](<https://devfeed.tech/topics/continuous-integration.md?cursor=WyIyMDI2LTEwLTIwVDE0OjQ1OjAwKzAwOjAwIiwgIjgzODEyYWI4LWVjOTYtNDNkOS04OTEyLWQyZDY1NzgyZTcxZSJd>)