# ci Published articles for ci. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Fixed release schedule scrapped (old schedule restored) DevFeed: [Fixed release schedule scrapped (old schedule restored)]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T16:33:13.815653Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [releases](), [audit](), [builds](), [ci](), [coreboot](), [Linux]() Tags: [article](), [audit](), [bios](), [build-system](), [canoeboot](), [ci](), [coreboot](), [free-software](), [libre](), [libreboot](), [linux](), [news](), [opensource](), [releases](), [uefi]() ### AI overview Libreboot has abandoned its fixed annual release schedule after skipping the June 2026 release and deciding to skip December 2026. The next release is expected sometime in 2027. The project is also considering automated build and release testing, potentially through CI and regular snapshot builds, while continuing an audit and simplification of its build system. ### Source excerpt Article: Fixed release schedule scrapped (old schedule restored) Web link: https://libreboot.org/news/resolutions.html ## Libreboot Git repositories now on Codeberg (RIP Notabug) DevFeed: [Libreboot Git repositories now on Codeberg (RIP Notabug)]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [forgejo](), [Git](), [ci](), [pull-requests](), [Gitea]() Tags: [bios](), [canoeboot](), [ci](), [coreboot](), [forgejo](), [free-software](), [git](), [go](), [libre](), [libreboot](), [opensource](), [pull-requests](), [repositories](), [uefi]() ### AI overview Libreboot is moving its advertised Git repositories to Codeberg because Notabug has become unreliable and frequently returns HTTP 500 errors. Notabug remains available as a backup, while Codeberg provides features including issue search and built-in CI through Woodpecker. ### Source excerpt Article: Libreboot Git repositories now on Codeberg (RIP Notabug) Web link: https://libreboot.org/news/codeberg.html ## ESPHome 2026.9.0: Faster builds and encrypted updates DevFeed: [ESPHome 2026.9.0: Faster builds and encrypted updates]() Original publisher: [Read original article]() Author: Jesse Hills Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [ESPHome - Smart Home Made Simple - Blog]() Topics: [esphome](), [PlatformIO](), [ESP8266](), [Encryption](), [build performance](), [ChaCha](), [toolchain](), [Home Assistant]() Tags: [2026](), [benchmarks](), [builds](), [ci](), [encryption](), [esp32](), [esp8266](), [esphome](), [ota](), [parallel](), [releases](), [toolchain](), [updates]() ### AI overview ESPHome 2026.9.0 improves build performance by parallelizing PlatformIO setup, lays groundwork for a native ESP8266 toolchain, adds Noise-encrypted OTA updates, and reduces ESP8266 RAM usage. The release also includes component additions, platform updates, and fixes. ### Source excerpt ESPHome 2026.9.0 parallelizes PlatformIO installs, lays the groundwork for a native ESP8266 toolchain, adds Noise-encrypted OTA updates, and frees ESP8266 RAM. ## How to operate shared platforms safely at agent scale DevFeed: [How to operate shared platforms safely at agent scale]() Original publisher: [Read original article]() Author: Candace Shamieh; T Zhang; Gabriele Baldoni Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Platform Engineering](), [Loop Engineering](), [AI Agent](), [sdlc](), [Latency](), [Low Latency](), [Concurrency](), [Software]() Tags: [agent](), [agent-observability](), [agentic-workflows](), [agents](), [ai](), [ai-agent](), [ci](), [concurrency](), [latency](), [low-latency](), [operational](), [performance](), [platform-engineering](), [platforms](), [queue](), [recovery](), [timeout]() ### AI overview This Datadog article explains how platform teams can operate shared platforms safely as AI agent workloads scale across teams. It discusses modeling demand across agent trajectories, planning capacity across dependencies such as CI queues and sandbox pools, handling contention and recovery behavior, and preserving control across system boundaries. ### Source excerpt Learn how Datadog models agent demand, allocates capacity under contention, and preserves control as AI agent workloads scale across shared platforms. ## How to Catch Security Vulnerabilities in Code Before They Reach Your Pull Requests DevFeed: [How to Catch Security Vulnerabilities in Code Before They Reach Your Pull Requests]() Original publisher: [Read original article]() Author: Umair Mirza Published: 2026-09-14T22:23:01Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [Application Security](), [Security](), [Vulnerabilities](), [Secret Scanning](), [Git](), [pull-requests](), [ci](), [Command-line interface](), [.NET](), [Python](), [coding]() Tags: [application-security](), [ci](), [cli](), [code](), [devsecops](), [git](), [net](), [pull-requests](), [python](), [sast](), [secret-scanning](), [security](), [security-vulnerabilities](), [software-development](), [testing](), [vulnerabilities]() ### AI overview This tutorial explains how to shift security checks earlier in development by running SAST locally with Git pre-commit hooks. It demonstrates using the DevSkim CLI to detect insecure coding patterns, pairing it with Gitleaks for dedicated secret scanning, validating the setup with an intentional failure, and enforcing the checks in CI. ### Source excerpt Security reviews are most effective when developers receive feedback while the code is still fresh in their minds. Waiting until a pull request, CI build, or penetration test to find exposed credentia ## PostgreSQL Monitoring and Schema Linting for Laravel with Vacuum DevFeed: [PostgreSQL Monitoring and Schema Linting for Laravel with Vacuum]() Original publisher: [Read original article]() Author: Paul Redmond Published: 2026-09-14T04:24:35Z Content type: article Language: en Sources: [Laravel]() Topics: [Laravel](), [PostgreSQL](), [Monitoring](), [ci](), [Databases](), [Structured-data]() Tags: [ci](), [github](), [laravel](), [laravel-packages](), [monitoring](), [postgresql](), [schema](), [sql]() ### AI overview Vacuum is a PostgreSQL monitoring and schema-linting package for Laravel. It analyzes PostgreSQL statistics, reports issues such as bloat, wraparound, dead tuples, unused indexes, slow statements, and unindexed foreign keys, and provides SQL remediation guidance, health scores, dashboards, CI commands, history, and explainers. ### Source excerpt Vacuum checks PostgreSQL in Laravel apps for bloat, wraparound, and unused indexes, and flags unindexed foreign keys in migrations during CI. The post PostgreSQL Monitoring and Schema Linting for Laravel with Vacuum appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## It passed CI. It passed your evals. The customer still got the wrong answer. DevFeed: [It passed CI. It passed your evals. The customer still got the wrong answer.]() Original publisher: [Read original article]() Author: Sean O'Dell Published: 2026-09-13T14:00:00Z Content type: article Language: en Sources: [The New Stack]() Topics: [AI Agent](), [agent observability](), [observability](), [tracing](), [dynatrace](), [ci](), [coding]() Tags: [ai](), [ai-agent](), [ai-agents](), [ai-engineering](), [ci](), [coding](), [dynatrace](), [observability](), [post-contributed](), [sponsor-dynatrace](), [sponsored](), [sponsored-post-contributed](), [traces]() ### AI overview The article explains how AI-agent failures can pass CI and evaluations while still producing slow or incorrect customer-facing results. It presents distributed traces and agent trajectories--model calls, tool calls, arguments, and results--as evidence for debugging retrieval behavior, release context, and feature-flag state. ### Source excerpt A diff is not evidence. It's a statement of intent. The tests passed. The review's done. The change is live. The post It passed CI. It passed your evals. The customer still got the wrong answer. appeared first on The New Stack. ## Agent and Model Evaluations in Gemini Enterprise Agent Platform are now GA DevFeed: [Agent and Model Evaluations in Gemini Enterprise Agent Platform are now GA]() Original publisher: [Read original article]() Author: Alex Martin; Dima Melnyk Published: 2026-09-12T11:04:33.891311Z Content type: release Language: en Sources: [Google Developers Blog]() Topics: [ai observability](), [SDKs](), [ci]() Tags: [agent](), [agents](), [ci](), [cli](), [development](), [enterprise](), [evaluation](), [experiments](), [gemini](), [llm](), [metrics](), [model](), [platform](), [production](), [telemetry](), [testing](), [traces]() ### AI overview Gemini Enterprise Agent Platform's evaluation service is generally available. It provides consistent evaluation of agents and models across local experiments and production traffic, with pre-built metrics, adaptive rubrics, custom metrics, simulators, and workflow integrations. ### Source excerpt Agent Platform's evaluation service is now generally available, providing developers with a unified engine to measure agent quality consistently across local development experiments and live production traffic. You can evaluate agents using over 20 pre-built metrics, DeepMind-backed adaptive rubrics, or custom code-based and LLM-as-a-judge metrics stored in a centralized, versioned registry. The service integrates directly into existing workflows via the Agent Platform SDK, agents-cli, and ADK, offering built-in user and environment simulators to automate complex multi-turn testing and streamline CI pipelines. ## PostgreSQL Migrator 1.0 : first stable release DevFeed: [PostgreSQL Migrator 1.0 : first stable release]() Original publisher: [Read original article]() Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [migration](), [Databases](), [releases](), [MySQL](), [Oracle Database](), [ci]() Tags: [ci](), [migration](), [mysql](), [open-source](), [oracle](), [postgresql](), [release]() ### AI overview PostgreSQL Migrator 1.0 is the first stable release of an open-source tool for migrating Oracle, MySQL, and MariaDB databases to PostgreSQL. It supports full inspection and limited conversion and migration for selected database objects, with compatibility promised across 1.x releases. ### Source excerpt Paris, 7th september 2026. The Dalibo team is pleased to announce the release of PostgreSQL Migrator 1.0 stable, a free and open-source tool designed to help migrate databases from Oracle and MySQL/MariaDB to PostgreSQL. Key features Easy installation: pure Go binary with zero proprietary dependencies. Fast, offline inspection: Extract the full source catalog once, then iterate on conversion offline. Complexity scoring: Quickly assess and compare the difficulty of migration projects. Interactive web UI: Browse both the original and converted catalogs, search objects, and identify migration blockers. Schema and data conversion: Converts datatype and SQL expression, convert column to boolean. Code analysis and transpilation: Transpiles and analyzes SQL, PL/SQL and routines with the companion transqlate tool. High-performance data copy: Streamed bulk COPY to PostgreSQL (or to files / pipes), with low memory usage and significantly higher throughput than traditional tools in our tests. Hackable & configurable: Reliable JSON catalog data, TOML configuration, and templating for fine-tuning. Supported features PostgreSQL Migrator supports migrating from Oracle Database 11g to 26ai, MySQL 8.4+ and MariaDB 10+ to PostgreSQL 16 up to 19. Version 1.0 has full inspection including jobs, system triggers, etc. However, conversion and migration is limited to role, schema, sequences, table, virtual columns, constraints and indexes. The documentation describes implemented and planned features including views, procedural objects, SQL Server and more. Stability We have built a demanding CI pipeline including end-to-end tests based on Oracle Free container and cypress. This effectively prevents regression and ensure quality. After one year of beta and rc, PostgreSQL Migrator is stable. We'll ensure configuration, CLI and project compatibility for all 1.x releases. License and availability PostgreSQL Migrator is released under the PostgreSQL License. Documentation: https://postgresql-mi ## Distributed tracing for CI pipelines without touching a single workflow file DevFeed: [Distributed tracing for CI pipelines without touching a single workflow file]() Original publisher: [Read original article]() Author: George Sims, downtherabbithole.dev Published: 2026-09-08T11:00:00Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [ci]() Tags: [blog](), [ci](), [github](), [github-actions](), [instrumentation](), [jobs](), [opentelemetry](), [tracing](), [workflow](), [workflows]() ### AI overview The article describes collecting GitHub Actions events at the organization level and converting them into OpenTelemetry spans to trace CI workflows without editing individual workflow files. ### Source excerpt You've probably felt this one: GitHub Actions usage creeps up across your org, and your actual visibility into it doesn't keep pace. Which workflows are slow? Which are flaky? How long are jobs sitting queued for... ## A Week of Symfony #1027 (August 31 - September 6, 2026) DevFeed: [A Week of Symfony #1027 (August 31 - September 6, 2026)]() Original publisher: [Read original article]() Author: Javier Eguiluz Published: 2026-09-06T07:46:00Z Content type: news Language: en Sources: [Symfony Blog]() Topics: [bug](), [ci](), [Command-line interface](), [pull-requests]() Tags: [bug](), [ci](), [command-line](), [diagnostics](), [pull-requests](), [symfony]() ### AI overview Symfony released versions 6.4.45, 7.4.18, and 8.1.6 with bug fixes and hardening improvements. The update also introduces the symfony lsp:check command for CI diagnostics covering unknown routes, missing templates, and configuration errors. ### Source excerpt This week, Symfony 6.4.45, 7.4.18, and 8.1.6 were released with numerous bug fixes and hardening improvements. Meanwhile, we introduced symfony lsp:check, a new command that brings Symfony-aware diagnostics to your CI pipeline, catching unknown routes, missing... ## Standardizing Exception Message Style in Ruby DevFeed: [Standardizing Exception Message Style in Ruby]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-09-05T00:00:00Z Content type: article Language: en Sources: [Daniel Doubrovkine]() Topics: [Ruby](), [Exception](), [ci]() Tags: [ci](), [exception](), [exceptions](), [grape](), [lint](), [open-source](), [plugin](), [ruby](), [standard]() ### AI overview The article explains a convention for Ruby exception messages: they should generally begin with lowercase and omit trailing punctuation because they follow the exception class name and a colon. It describes fixing seven inconsistent sites in Grape, documenting the convention, and releasing the rubocop-exception_messages RuboCop plugin to enforce casing and punctuation, with additional checks for redundant class names and interpolation markers. ### Source excerpt While reviewing dozens of PRs from ericproulx optimizing Grape's internals recently, I noticed that the bare raise ArgumentError, "..." calls scattered across the codebase were inconsistent: some messages were capitalized, some ended in a period, most were not. Longtime readers know where this is going. Ruby's own core and standard library exceptions don't do this - TypeError: no implicit conversion from nil to integer, ArgumentError: wrong number of arguments, and so on all read lowercase and unpunctuated, because the message is meant to be read after the exception class name and a colon, not as a standalone sentence. Grape's own Grape::Exceptions::* classes already follow this convention. The bare raise ArgumentError, "..." calls in dsl/entity.rb, dsl/inside_route.rb, dsl/validations.rb, and validations/types/dry_type_coercer.rb didn't, so I fixed those seven sites and documented the convention in CONTRIBUTING.md, in #2909. To avoid regressions, I wrote rubocop-exception_messages, a RuboCop plugin gem with two cops: ExceptionMessages/Casing flags (and autocorrects) messages that don't start with a lowercase letter. ExceptionMessages/Punctuation flags (and autocorrects) messages with a trailing period, with an exception for a literal ellipsis ("still processing.."), which is stylistic rather than a sentence ending. Both cops recognize raise Class, "message" and raise Class.new("message") forms, and handle interpolated (dstr) messages by only checking the literal string segments (the first segment for casing, the last for punctuation), since interpolated values in the middle are out of the cop's control. # bad raise ArgumentError, 'Missing required option.' # good raise ArgumentError, 'missing required option' The gem ships as a modern RuboCop plugin (via lint_roller), so it's a one-line addition to a consuming project's .rubocop.yml: plugins: - rubocop-exception_messages rubocop-exception_messages 0.2.0 is out now, and I've added it back to Grape's own Gemfile and ## ArduinoCore-Zephyr 1.0.0 adds support for Arduino VENTUNO Q, updates to Zephyr 4.4.1, and more DevFeed: [ArduinoCore-Zephyr 1.0.0 adds support for Arduino VENTUNO Q, updates to Zephyr 4.4.1, and more]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-04T10:27:38Z Content type: release Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Arduino](), [Zephyr RTOS](), [Embedded Systems](), [Embedded Software Dev](), [Hardware](), [Microcontroller](), [webcam](), [ci]() Tags: [arduino](), [bug-fixes](), [camera](), [ci](), [development-board](), [embedded-systems](), [hardware](), [mcu](), [real-time](), [release](), [software-management](), [ventuno-q](), [vision](), [zephyr](), [zephyr-os]() ### AI overview Arduino has released ArduinoCore-Zephyr 1.0.0 with support for the VENTUNO Q SBC and Nicla Vision camera, an update to Zephyr 4.4.1, and bug-fix and CI improvements. The article also lists supported Arduino platforms and installation steps. ### Source excerpt Arduino has just announced the release of ArduinoCore-Zephyr version 1.0.0, with new hardware support, including the VENTUNO Q SBC, an updated Zephyr 4.4.1 base, support for the Nicla Vision camera, and various fixes and improvements. Arduino first announced its plans to switch from Arm Mbed to Zephyr RTOS in July 2024, before releasing the first beta of Arduino Core for Zephyr in December of the same year. ArduinoCore-Zephyr 1.0.0 is not the first stable version, since that was version 0.90.0 released on July 29, 2026. The new release builds on that, so let's see what's new. ArduinoCore-Zephyr 1.0.0 highlights Support for Arduino VENTUNO Q SBC, specifically the STM32H5F5 real-time MCU on the board Update to Zephyr 4.4.1 with the latest upstream improvements, security fixes, and driver support Added Nicla Vision camera support to capture and process image data directly through the Zephyr core Various bug fixes and CI improvements Currently [...] The post ArduinoCore-Zephyr 1.0.0 adds support for Arduino VENTUNO Q, updates to Zephyr 4.4.1, and more appeared first on CNX Software - Embedded Systems News. ## Beyond the Merge: Enforcing Policy Before the Terraform Apply DevFeed: [Beyond the Merge: Enforcing Policy Before the Terraform Apply]() Original publisher: [Read original article]() Author: Sachin Agarwal Published: 2026-09-03T17:25:32Z Content type: article Language: en Sources: [Nirmata]() Topics: [iac-security](), [Terraform](), [Security](), [Kyverno](), [Tooling]() Tags: [ci](), [cloud-security](), [code-security](), [infrastructure-as-code](), [kyverno](), [other](), [policy-as-code](), [pull-request](), [scanner](), [security](), [shift-left](), [terraform]() ### AI overview The article describes using Nirmata Control and its nctl CLI to evaluate Terraform plans against policy-as-code rules before deployment. It presents pre-apply CI checks for detecting infrastructure misconfigurations, including unrestricted ingress, missing S3 public-access blocking, wildcard IAM resources, and missing VPC deployment. ### Source excerpt Run Terraform security scanning on the plan, not the live account. nctl checks 4 critical misconfigs in CI, with exceptions scoped to one resource. ## Xen on RISC-V just ran on real hardware! DevFeed: [Xen on RISC-V just ran on real hardware!]() Original publisher: [Read original article]() Author: Baptiste Le Duc Published: 2026-09-03T08:00:27Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [RISC-V](), [virtualization](), [systems](), [ci](), [cpu](), [Emulator]() Tags: [ci](), [cpu](), [qemu](), [risc-v](), [systems](), [virtualization]() ### AI overview Xen now boots a guest domain on physical RISC-V hardware using a HiFive Premier P550. Supporting changes accommodate the board's pre-ratification hypervisor extension and add reproducible hardware-based CI that boots Xen and a Linux guest. ### Source excerpt Xen now boots a guest domain on physical RISC-V hardware, not just in QEMU. The board we used ships a CPU designed before the hypervisor extension was ratified, which turned out to be the whole challenge. ## Announcing Rust 1.98.1 DevFeed: [Announcing Rust 1.98.1]() Original publisher: [Read original article]() Author: The Rust Release Team Published: 2026-09-03T00:00:00Z Content type: release Language: en Sources: [Rust Blog]() Topics: [releases](), [ci]() Tags: [bugs](), [ci](), [release](), [rust](), [update]() ### AI overview Rust 1.98.1 is a point release that fixes a vtable-generation miscompilation which could produce undefined behavior, including null-pointer segfaults or arbitrary effects. ### Source excerpt The Rust team has published a new point release of Rust, 1.98.1. Rust is a programming language that is empowering everyone to build reliable and efficient software. If you have a previous version of Rust installed via rustup, getting Rust 1.98.1 is as easy as: rustup update stable If you don't have it already, you can get rustup from the appropriate page on our website. What's in 1.98.1 Rust 1.98.1 fixes a miscompilation in vtable generation. In Rust 1.98.0, in some circumstances, rustc would incorrectly generate a trait object vtable with a null pointer where a function pointer should be. This leads to undefined behavior in the emitted code. In some cases this may 'just' cause segfaults due to the null pointer being loaded, but it is possible for it to be justification for arbitrary effects (as is typical for UB). If you'd like to help us out by testing future releases, you might consider using the beta (rustup default beta) and nightly (rustup default nightly) channels locally and in your CI. Please report any bugs you might come across! Contributors to 1.98.1 Many people came together to create Rust 1.98.1. We couldn't have done it without all of you. Thanks! ## Orchestrating Playwright test suites with Temporal for independent retries DevFeed: [Orchestrating Playwright test suites with Temporal for independent retries]() Original publisher: [Read original article]() Author: Simon Emms Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Playwright](), [Orchestration](), [ci](), [test]() Tags: [browsers](), [ci](), [orchestration](), [playwright](), [retry](), [temporal-voices](), [tests]() ### AI overview This article explores using Temporal to orchestrate Playwright end-to-end test suites as independent, durable units of work. The approach allows failed tests to retry independently while preserving progress instead of restarting the entire CI job. ### Source excerpt Learn how Temporal can orchestrate end-to-end test suites so failed tests retry independently, preserving progress without restarting the entire CI job. ## How River takes security work from a fix to merge DevFeed: [How River takes security work from a fix to merge]() Original publisher: [Read original article]() Author: Erin Son Published: 2026-09-02T16:30:45Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Vulnerabilities](), [AI Bots]() Tags: [agentic](), [ai-agent](), [autonomous](), [ci](), [security](), [shopify](), [slack](), [vulnerability](), [workflow]() ### AI overview Shopify describes River, an AI agent that manages vulnerability remediation from patch review through merge and verification against the repository head and dependency graph. The article reports a 70% reduction in open dependency issues during the workflow's first 11 days. ### Source excerpt River, Shopify's AI agent in Slack, enables autonomous vulnerability remediation, not just detection. ## Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup DevFeed: [Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup]() Original publisher: [Read original article]() Author: Zelmar Michelini Published: 2026-09-02T11:38:40Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [MongoDB](), [Terminal](), [Command-line interface](), [ci](), [dashboards](), [Streams]() Tags: [ci](), [code](), [commands](), [database](), [mongodb](), [state](), [terminal](), [tests](), [ui]() ### AI overview This article introduces mongorewind, a terminal UI tool that records MongoDB data changes through a cluster-wide change stream and reverses them in reverse chronological order. It is designed to restore test data to its pre-test state without restoring a backup and supports interactive and CI use. ### Source excerpt Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup One day, my friend Martín told me about a problem he and his team were dealing with. Every time they needed to run a pre-production test, they had to restore a copy of the production database into their test cluster. That process alone takes about ... Continued The post Mongorewind: Rewind Your MongoDB Test Data Without Restoring a Backup appeared first on Percona. ## Fragments: September 1 DevFeed: [Fragments: September 1]() Original publisher: [Read original article]() Author: Martin Fowler (martin@martinfowler.com) Published: 2026-09-01T19:50:00Z Content type: article Language: en Sources: [Martin Fowler]() Topics: [AI Bots](), [AI Chat]() Tags: [agents](), [ai](), [architecture](), [autonomous](), [autonomous-agents](), [benchmark](), [ci](), [claude](), [evaluation](), [gpu](), [kernel](), [llm](), [mcp](), [memory](), [nvidia](), [optimization](), [reasoning]() ### AI overview A fragment-style developer roundup covers concerns about detecting AI-generated prose, a long-horizon autonomous-agent architecture used for GPU kernel optimization and reasoning benchmarks, a brief MCP comparison, and the effect of AI agents on CI workflows. ### Source excerpt Like many readers, I'm wary of AI generated prose. Simon Wilison has written an LLM cliché highlighter - paste in some text, or a URL, and it will flag various patterns common to LLMs. It references a wikipedia page of signs of AI writing. That page points out that: Humans are notoriously bad at distinguishing human and LLM-generated text. While research on humans' abilities to detect AI-generated text is still limited, a 2025 study has shown that human ability to distinguish LLM text from human is no better than random chance. Another 2025 study on German theses has shown that humans managed a "recognition rate of 57% for AI texts and 64% for human-generated texts".[ Not just do I find myself repelled by prose with an LLM-voice, I also wonder how accurate my reaction is. I'm old enough to see all sorts of new tic-phrases appear, and in the past would just chalk it up to youngsters or airport business books. (Not to mention Americanisms, which I'll get used to momentarily.) ❄ ❄ ❄ ❄ ❄ NVIDIA's technical blog reports on an Architecture for Long-Horizon Autonomous Agents. Their research group used a combination of Claude Opus 5 and a harness called AVO, and used it first to do GPU kernel optimization and then a broader reasoning benchmark (ARC-AGI-3). Both of these were long-term tasks, for the kernel optimization the agent ran for seven days. AVO is designed to preserve progress beyond a single model context. Two mechanisms are particularly important: persistent memory and supervision. Persistent memory carries forward prior implementations, evaluation results, compiler and profiler outputs, and accumulated reasoning, allowing the agent to resume from the current state rather than repeatedly reconstructing the search. The supervisor monitors the broader trajectory for stagnation or repeated unproductive cycles and can redirect the main agent toward alternative strategies when needed. During the seven-day attention-kernel run, the main agent remained responsible for de ## CircleCI is now available on Cursor Origin DevFeed: [CircleCI is now available on Cursor Origin]() Original publisher: [Read original article]() Author: Nathan Fish Published: 2026-09-01T18:45:00Z Content type: release Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [CI/CD](), [Testing](), [AI-assisted coding](), [Pull Request]() Tags: [agentic-ci-cd](), [ai-coding-agents](), [ai-development](), [ci](), [ci-cd](), [circleci](), [circleci-cursor-origin](), [circleci-news](), [cursor-origin](), [cursor-origin-ci-cd](), [integrations](), [mcp](), [origin-ci-cd-integration](), [pull-request](), [testing]() ### AI overview CircleCI has released a beta integration with Cursor Origin, allowing teams to connect Origin-hosted repositories and run CI/CD pipelines on pushes and pull requests. The integration supports agent-oriented validation through parallel execution, targeted testing, and feedback via the CircleCI CLI and MCP. ### Source excerpt CircleCI now integrates with Cursor Origin in beta. Connect an Origin repo, keep your existing .circleci/config.yml, and add agent-friendly CI/CD to your Origin projects. ## Cypress 16: faster tests, starting with HTTP/2 support DevFeed: [Cypress 16: faster tests, starting with HTTP/2 support]() Original publisher: [Read original article]() Published: 2026-09-01T17:28:34Z Content type: release Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [HTTP](), [Chromium](), [Node.js](), [Streaming](), [Vite]() Tags: [chromium](), [ci](), [cypress](), [http](), [node-js](), [streaming](), [tests](), [vite]() ### AI overview Cypress 16 improves end-to-end test performance with HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie and storage commands, and automatic memory management. The release also updates Node.js, Electron, and Chromium versions and removes Cypress.env() as part of its security work. ### Source excerpt Cypress 16 goes after slow test suites from every angle: HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie commands, and automatic memory management. Most of it arrives without editing a single test. Here's what changed, why, and how to upgrade. ## Finding three-way API drift with the AI Engineer DevFeed: [Finding three-way API drift with the AI Engineer]() Original publisher: [Read original article]() Author: Talia Kohan Published: 2026-09-01T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [API](), [Postman](), [OpenAPI Specification](), [Claude](), [Tooling](), [client](), [servers]() Tags: [ai-engineer](), [api](), [api-drift](), [apis](), [ci](), [fintech](), [general](), [openapi](), [postman-ai-engineer](), [production](), [qa]() ### AI overview The article explains how to detect three-way API drift by comparing an OpenAPI specification, the requests in Postman Collections, and the responses returned by a running server. It argues that pairwise checks can miss cases where all three sources disagree, and describes using Postman AI Engineer and the Context Graph to identify these inconsistencies. ### Source excerpt Find three-way API drift with Postman AI Engineer and the Context Graph. Compares your OpenAPI spec, collection requests, and live server responses. The post Finding three-way API drift with the AI Engineer appeared first on Postman Blog. ## Building patterns unlocked by scale to zero DevFeed: [Building patterns unlocked by scale to zero]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2026-09-01T12:00:00Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Databases](), [autoscaling](), [ci]() Tags: [autoscaling](), [building](), [ci](), [compute](), [database](), [postgres](), [product](), [scale]() ### AI overview The article explains how autoscaling and scale to zero reduce idle Postgres compute costs. It presents ephemeral database branches for previews, tests, and individual development work as patterns enabled by suspending inactive compute. ### Source excerpt Most hosted Postgres pricing works like this: you pick an instance size, the vendor assumes the instance will run for about 730 hours a month, and you pay for those hours. Lakebase Postgres addresses that waste with autoscaling and scale to zero. [Next page]()