# ci A software development practice of frequently integrating code changes into a shared repository and automatically building and testing them. 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 ## Starting Android at Khan Academy DevFeed: [Starting Android at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-29T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [android-development](), [Development](), [Library](), [modules](), [ci](), [Mocking]() Tags: [android](), [android-development](), [development](), [engineering](), [libraries](), [mobile](), [mocking](), [module](), [modules](), [news](), [open-source](), [picasso](), [play-store](), [pre-commit](), [retrofit](), [test](), [tests]() ### AI overview Khan Academy describes its first Android app, launched in August 2015, and the engineering practices used to build it. The team adopted established Android and open-source libraries, separated Android-independent core code from the app module, and used fast JVM tests and continuous integration. ### Source excerpt By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more ## 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. ## 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. ## Stop AI code sprawl before it destroys your software design DevFeed: [Stop AI code sprawl before it destroys your software design]() Original publisher: [Read original article]() Author: Emmanuel Akita Published: 2026-09-10T12:30:00Z Content type: opinion Language: en Sources: [The New Stack]() Topics: [AI-assisted coding](), [CI/CD](), [ci]() Tags: [ai](), [ai-coding](), [ai-engineering](), [andela](), [architecture](), [ci-cd](), [post-contributed](), [python](), [sponsor-andela](), [sponsored-post-contributed](), [testing]() ### AI overview The article argues that AI-generated code can create "Comprehension Debt" by silently violating architectural boundaries. It advocates enforcing architecture through automated tests and CI/CD pipelines rather than relying on documentation and manual review. ### Source excerpt While AI code generators help teams ship faster than ever, that speed brings a hidden killer: Comprehension Debt. As soon The post Stop AI code sprawl before it destroys your software design appeared first on The New Stack. ## 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 ## 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. ## 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. ## 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. ## Test Replay now redacts sensitive network data before upload DevFeed: [Test Replay now redacts sensitive network data before upload]() Original publisher: [Read original article]() Published: 2026-08-31T22:12:34Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Authorization](), [data](), [ci](), [Cloud]() Tags: [authorization](), [ci](), [cloud](), [cypress](), [data](), [logs]() ### AI overview Cypress Test Replay now redacts sensitive authorization and credential-like values from captured network logs on the user's machine before uploading them to Cypress Cloud. Redaction is enabled by default, while project-level settings allow teams to disable it. ### Source excerpt Test Replay automatically redacts sensitive values from captured network logs before that data reaches Cypress Cloud. If your team turned Test Replay off in the past because of what your network logs held, this is the change that may let you turn it back on. You keep full CI debugging, and the values you didn't want stored are removed on your machine before Test Replay data is uploaded. Redaction is on by default, and you can turn it off for one project at a time in project settings. What g ## Introducing symfony lsp:check: Symfony-Aware Diagnostics in Your CI DevFeed: [Introducing symfony lsp:check: Symfony-Aware Diagnostics in Your CI]() Original publisher: [Read original article]() Author: Fabien Potencier Published: 2026-08-31T12:03:00Z Content type: article Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [ci](), [Command-line interface](), [configuration](), [PHP](), [Stimulus]() Tags: [ci](), [cli](), [command-line](), [github](), [php](), [symfony](), [validation]() ### AI overview The Symfony Language Tools introduce a headless Symfony-aware diagnostics command for CI. It detects framework-specific issues that type checkers and code review may miss, including unknown routes, missing templates and translation keys, invalid configuration, unknown services, and other integration errors. ### Source excerpt A Symfony application is full of strings that mean something: route names, template paths, translation keys, service ids, bundle configuration keys. To PHP, they are strings like any others. Your CI pipeline verifies types with PHPStan or Psalm, style with... ## 150,000 Commits Later -- Zephyr Podcast #048 DevFeed: [150,000 Commits Later -- Zephyr Podcast #048]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-08-28T15:10:59Z Content type: article Language: en Sources: [Zephyr Project]() Topics: [Code](), [ci](), [Hardware](), [Microcontroller](), [qemu](), [Raspberry Pi](), [ESP32-C3]() Tags: [blog](), [ci](), [code](), [esp32-c3](), [hardware](), [podcast](), [qemu](), [raspberry-pi-5]() ### AI overview Zephyr Podcast #048 covers Zephyr's main branch reaching 150,000 commits, increased pull-request activity, a batch-based merge experiment, AI-assisted commits, custom debug adapters, new VirtIO and I2C libraries, test monitoring, and expanded hardware and QEMU support. ### Source excerpt Pre-orders open for the Arduino VENTUNO Q, and what $300 actually buys you 150,000 commits in main, and 1,455 PRs merged in August against 700 a year ago Create your... ## 150,000 Commits Later -- Zephyr Podcast #048 DevFeed: [150,000 Commits Later -- Zephyr Podcast #048]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-08-28T15:10:59Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Code](), [ci](), [debug](), [qemu](), [ESP32](), [Raspberry Pi](), [Arduino]() Tags: [arduino](), [blog](), [ci](), [code](), [debug](), [esp32](), [podcast](), [qemu](), [raspberry-pi](), [zephyr]() ### AI overview Zephyr Podcast #048 covers the project's main branch reaching 150,000 commits, increased pull-request merging in August, a trial merge-batch workflow, and new or updated hardware, driver, testing, and QEMU support. It also discusses a custom debug adapter and an I2C register-set library. ### Source excerpt Pre-orders open for the Arduino VENTUNO Q, and what $300 actually buys you 150,000 commits in main, and 1,455 PRs merged in August against 700 a year ago Create your... ## The Real Python Podcast - Episode #309: Exploring Complex Systems & Maintainable Data Science Pipelines DevFeed: [The Real Python Podcast - Episode #309: Exploring Complex Systems & Maintainable Data Science Pipelines]() Original publisher: [Read original article]() Author: Real Python Published: 2026-08-28T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Complex Systems](), [Data Science](), [Python](), [systems](), [configuration](), [ci](), [YAML](), [releases](), [Django](), [VS Code Extension]() Tags: [code](), [complex-systems](), [configuration](), [data-science](), [django](), [podcast](), [python](), [release](), [systems](), [vs-code](), [workflow]() ### AI overview This Real Python podcast episode explores complex versus complicated coding problems and practical patterns for designing maintainable systems. It also covers repeatable data science pipelines, DataFrame validation with Pointblank, configuration-driven modular workflows, Python releases, PEPs, Django's release cycle, and several Python community projects. ### Source excerpt What are the key characteristics of complex systems, and what are practical patterns for tackling complex coding problems? Christopher Trudeau is back on the show this week with another batch of PyCoder's Weekly articles and projects. ## Vercel Security Dashboard is now generally available DevFeed: [Vercel Security Dashboard is now generally available]() Original publisher: [Read original article]() Author: Jathin Singaraju Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [dashboards](), [Security](), [Vercel](), [Command-line interface](), [OpenID connect (OIDC)](), [Terminal](), [ci](), [CSV](), [JSON]() Tags: [ci](), [cli](), [coding-agents](), [documentation](), [git](), [json](), [oidc](), [report](), [scope](), [security](), [terminal](), [ui](), [vercel]() ### AI overview Vercel Security Dashboard is generally available on all plans. It centralizes security findings across accounts and projects, supports risk-ordered remediation and CSV export, and provides equivalent checks through the Vercel CLI. Agents can inspect findings, apply supported fixes, and re-check results, with JSON output available in CI and other non-interactive environments. ### Source excerpt The Vercel Security Dashboard is now generally available on all plans, giving you one place to see your security posture across every account and project. You can access the Security Dashboard in the UI or run vercel security check in the Vercel CLI. As teams grow and coding agents make it faster to spin up projects, small misconfigurations add up quietly. The Security Dashboard automatically flags issues like: Team members without 2FA Long-lived credentials that can be replaced with OIDC Public preview deployments Non-sensitive and stale environment variables The Security Dashboard UI Misconfigurations are ordered by risk with the most severe first, and each finding links to the settings that fix them. Findings that are just noise for your team can also be muted, and all results can be exported to a CSV file for triage or reporting. The Security Dashboard CLI You can also run the same checks in your terminal through the new Vercel CLI vercel security check command, allowing your agents to work through the findings for you. An agent using vercel security check --findings can read what failed, apply the fix and re-check to confirm. Fixes an agent can apply include: Turning on Git fork protection Marking an environment variable as sensitive Replacing a static credential with OIDC federation You can also scope the check to one project with --project when you want a narrow change set. In CI or any other non-interactive environment, the command writes the report to stdout as JSON automatically, giving agents structured output without extra flags. Get started by running your first scan from the Security Dashboard, and learn more in the Security Dashboard documentation. Read more ## Keeping Documentation Honest with an OpenAPI Snapshot Diff DevFeed: [Keeping Documentation Honest with an OpenAPI Snapshot Diff]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-25T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [OpenAPI Specification](), [FastAPI](), [ci](), [Pytest](), [Documentation](), [JSON](), [test]() Tags: [api-documentation](), [ci](), [ci-cd](), [documentation](), [fastapi](), [json](), [openapi](), [pytest](), [test](), [testing]() ### AI overview The article explains how to keep API documentation aligned with a FastAPI application by generating its OpenAPI schema from the running code, comparing it with a committed snapshot in CI, normalizing the JSON diff, and requiring deliberate snapshot regeneration. ### Source excerpt FastAPI app.openapi() snapshot test in pytest: fail CI when the live OpenAPI schema drifts from the committed openapi.snapshot.json. ## Scale software delivery pipelines in isolation without owning the runner fleet DevFeed: [Scale software delivery pipelines in isolation without owning the runner fleet]() Original publisher: [Read original article]() Author: Kyurim Rhee Published: 2026-08-25T00:00:00Z Content type: article Language: en Sources: [GitLab]() Topics: [ci](), [GitLab](), [Software as a service](), [Security](), [cloud-infrastructure](), [Provisioning]() Tags: [agentic](), [ci](), [compliance](), [cost](), [developers](), [devsecops-platform](), [infrastructure](), [operations](), [platform](), [product](), [saas](), [scale](), [security](), [software-delivery](), [workflows]() ### AI overview GitLab presents Hosted Runners for GitLab Dedicated, a fully managed CI execution SaaS offering with isolated runner infrastructure. Each job runs in a newly provisioned VM that is deleted after completion, helping enterprises address security, compliance, scalability, reliability, and runner-operations demands without owning the runner fleet. ### Source excerpt Many enterprises choose GitLab Dedicated for a clear reason: a secure and compliant, single-tenant GitLab instance, managed by GitLab. As agentic workflows drive more pipeline volume, full data isolation and runner infrastructure operational burden become a challenge. This leads to the question, "Does owning the runner fleet still make sense?" With GitLab Dedicated, there is no more need to provision, patch, build, and scale your own runner fleet. Hosted Runners for GitLab Dedicated handles the heavy lifting and delivers a seamless experience across the entire software development lifecycle so your team can focus on shipping. Hosted Runners for GitLab Dedicated provides a runner fleet isolated from other customers. To support job-level security, each job runs in a newly provisioned, isolated VM that is deleted after the job completes. We provide a scalable and highly reliable runner fleet to support your bursty CI demands and resiliency needs. Creating and managing runners is self-serviceable through Switchboard (GitLab Dedicated management console). The runner ownership trade-off: Cost vs. user experience Pipeline load can be unpredictable. To account for this, runner infrastructure can be over-provisioned to give developers the best experience and maintain low wait times. But this drives up the infrastructure cost. Conversely, under-provisioning can save on infrastructure cost, but your developers will waste time waiting for their CI jobs to be picked up. Efforts to fine-tune this balance can monopolize your platform team's time. Shift runner operations to GitLab while maintaining control Hosted Runners for GitLab Dedicated is a fully managed CI execution SaaS offering. It's backed by a high-performing and reliable runner infrastructure. Key benefits include: Supports compliance: Full isolation/single-tenant runners with same data residency as GitLab Dedicated. Job level security: "One runner for one job" -- hosted runners run every job in a standalone, short-lived ## RISC-V is now officially supported by CPython! DevFeed: [RISC-V is now officially supported by CPython!]() Original publisher: [Read original article]() Author: Stan Ulbrych Published: 2026-08-24T00:00:00Z Content type: news Language: en Sources: [Python Insider]() Topics: [RISC-V](), [Python](), [Hardware](), [ci]() Tags: [ci](), [community](), [contributed](), [contributors](), [hardware](), [platform](), [python](), [testing]() ### AI overview CPython now officially supports RISC-V as a tier 3 platform. The article describes the community contributions, real-hardware testing, and build support that enabled the milestone, as well as plans to integrate RISC-V into CPython's CI and eventually pursue tier 2 support. ### Source excerpt I'm happy to announce that RISC-V platforms are now officially supported by CPython. 🎉 🚀 [Next page]()