# CI/CD

CI/CD is a build automation strategy and part of DevOps Continuous integration: Frequent merging of several small changes into a main branch. Continuous delivery: When teams produce software in short cycles with high speed and frequency so that reliable software can be released at any time, and with a simple and repeatable deployment process when deciding to deploy. Continuous deployment: When new software functionality is rolled out completely automatically.

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

## Borealis Isolated Postgres: Serious Database Security for the Common Runtime

DevFeed: [Borealis Isolated Postgres: Serious Database Security for the Common Runtime](<https://devfeed.tech/articles/borealis-isolated-postgres-serious-database-security-for-the-common-runtime-146521.md>)

Original publisher: [Read original article](<https://www.heroku.com/blog/borealis-isolated-postgres/>)

Author: Joel Andrews

Published: 2026-11-20T17:24:16Z

Content type: article

Language: en

Sources: [Heroku](<https://devfeed.tech/sources/heroku.md>)

Topics: [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>), [Database](<https://devfeed.tech/topics/database.md>), [Security](<https://devfeed.tech/topics/security.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [SELinux](<https://devfeed.tech/topics/selinux.md>), [Fail2ban](<https://devfeed.tech/topics/fail2ban.md>)

Tags: [add-ons](<https://devfeed.tech/tags/add-ons.md>), [database](<https://devfeed.tech/tags/database.md>), [database-security](<https://devfeed.tech/tags/database-security.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [heroku-postgres](<https://devfeed.tech/tags/heroku-postgres.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [runtime](<https://devfeed.tech/tags/runtime.md>)

### AI overview

Borealis Isolated Postgres provides network-isolated PostgreSQL for apps on Heroku's Common Runtime. Each database cluster sits in its own VPC and rejects incoming traffic by default, while three access paths support different needs: a buildpack creates secure app-to-database tunnels and can use a read-only URL; a Heroku CLI plugin opens temporary tunnels for administration and CI/CD, with CLI access read-only by default unless `--write-access` is supplied; and third-party integrations can connect through SSH port forwarding, read-only by default unless write access is enabled at creation. The article also describes TLS 1.2+ in transit, AES-256 at rest, restricted staff access and audit logging, temporary CLI credentials, weekly app credential rotation, and automatic minor PostgreSQL updates. Major upgrades are CLI-initiated and have under a minute of downtime. This is the vendor's account of its security features.

### Source excerpt

The power of Heroku lies in its simplicity. Developers can spin up an entire app stack, complete with its own database and caching layers with just a single command. No need for the specialized, time-consuming work of managing servers and virtual machines. This convenience applies to interacting with your app stack as well. Need to [...] The post Borealis Isolated Postgres: Serious Database Security for the Common Runtime appeared first on Heroku.

## How to Perform eSIM Testing: Steps, Scenarios, and Automation Approach

DevFeed: [How to Perform eSIM Testing: Steps, Scenarios, and Automation Approach](<https://devfeed.tech/articles/how-to-perform-esim-testing-steps-scenarios-and-automation-approach-146866.md>)

Original publisher: [Read original article](<https://testgrid.io/blog/esim-testing/>)

Author: Sanjaykumar Ghinaiya

Published: 2026-11-20T13:29:09Z

Content type: tutorial

Language: en

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

Topics: [Mobile Testing](<https://devfeed.tech/topics/mobile-testing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [approach](<https://devfeed.tech/tags/approach.md>), [automation](<https://devfeed.tech/tags/automation.md>), [esim](<https://devfeed.tech/tags/esim.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mobile-app-testing](<https://devfeed.tech/tags/mobile-app-testing.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

eSIM testing must verify the full path from profile provisioning through network registration and usable services: successful installation alone does not ensure data, SMS, or voice will work. The guide recommends covering profile download and integrity, lifecycle state changes, activation and recovery, security and authorization, connectivity, roaming, and device compatibility. Its workflow is to define supported devices, operators, and consumer (SGP.22) or IoT (SGP.32) architecture; prepare physical devices, authorized profiles, and diagnostics; provision and activate; run functional, network, and end-to-end checks; then analyze logs and traces. Real-device coverage, standardized configurations, detailed diagnostics, and repeatable regression automation can improve scale and reproducibility. Automation depends on exposed device, app, API, operator, and provisioning controls; some carrier- or device-controlled operations may need specialized access or manual validation. Functional testing is distinct from formal GSMA conformance testing.

### Source excerpt

What happens when an eSIM profile installs successfully, but the device still cannot register on the right network or establish the services the subscriber expects? That's why eSIM testing has to cover more than the activation screen. You need to validate profile provisioning and management, device behavior, network registration, connectivity, recovery, and the application experience [...]

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

## A single pull request could have handed attackers the keys to Microsoft's software supply chain

DevFeed: [A single pull request could have handed attackers the keys to Microsoft's software supply chain](<https://devfeed.tech/articles/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-145215.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4251130/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsofts-software-supply-chain-2.html>)

Author: Taryn Plumb

Published: 2026-11-20T03:15:48Z

Content type: news

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-control-authentication-github-identity-and-access-management-security-software-developme](<https://devfeed.tech/tags/access-control-authentication-github-identity-and-access-management-security-software-developme.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [github](<https://devfeed.tech/tags/github.md>), [github-personal-access-token](<https://devfeed.tech/tags/github-personal-access-token.md>), [http](<https://devfeed.tech/tags/http.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [internal-tooling](<https://devfeed.tech/tags/internal-tooling.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [package-registries](<https://devfeed.tech/tags/package-registries.md>), [powershell](<https://devfeed.tech/tags/powershell.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [review](<https://devfeed.tech/tags/review.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [version-control-systems](<https://devfeed.tech/tags/version-control-systems.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Cycode researchers found a now-patched WinGet vulnerability in a Microsoft moderator's PowerShell triage tool: it attached a moderator's full-identity GitHub Personal Access Token to requests without checking the destination host. A crafted pull request could trigger automated validation to fail, prompting a background triage script to send an authenticated request to an attacker-controlled server, exposing the token without moderator interaction. Exploitation required at least one moderator to have the tracker running in its designed continuous loop; the article reports no evidence of in-the-wild exploitation. Microsoft fixed the flaw by limiting token attachment to authorized GitHub hosts. The article says the corresponding C# tool did not share the flaw, while Cycode calls the broader credential model flawed and recommends destination-bound credentials, host validation, auditing internal tools, retiring classic PATs, and limiting token permissions and scope.

### Source excerpt

The most dangerous actor in a software supply chain may now be an automated script with powerful credentials and no idea where it's sending them. Researchers from pen-testing company Cycode have discovered a now patched critical zero-click supply chain vulnerability in the open-source Windows Package Manager (WinGet), which sits on billions of devices worldwide. A single pull request could have tricked Microsoft's internal tooling into freely handing over a moderator's GitHub access token, with no phishing, no malware, no moderator clicking or approval required. There is currently no evidence that the flaw has been exploited in the wild. But it serves as a cautionary tale for enterprises that the automation they trust is becoming an attacker entry point, and package repositories are particularly enticing targets. "Package registries have become the highest-profile target in the software supply chain," Moriel Harush, Cycode security research lead, wrote in a blog post. "Compromise a single maintainer, and you reach everyone who trusts them. Compromise the gatekeepers, and you reach the entire ecosystem." Whatever the employee can do, the attacker can do WinGet is Microsoft's free, open source command line tool that helps users discover, install, upgrade, configure, and remove apps. It exists on more than 1.4 billion active devices running Windows 10, Windows 11, and Windows Server 2025. WinGet's catalog is a public GitHub repository, and its gatekeeper, so to speak, is a small, official group of Microsoft moderators who review a constant stream of community pull requests and proposed changes. By default, WinGet installations on every Windows machine trust the actions those keepers take. The hole is in the moderators' own internal triage tool. This PowerShell helper attached the moderator's secret GitHub Personal Access Token (PAT) to any HTTP request, without checking who owned that address. This meant an attacker merely had to supply an address. Theoretically, if th

## Do You Still Need Airflow for Snowflake Pipelines? An Honest Answer From Someone Who's Run Both

DevFeed: [Do You Still Need Airflow for Snowflake Pipelines? An Honest Answer From Someone Who's Run Both](<https://devfeed.tech/articles/do-you-still-need-airflow-for-snowflake-pipelines-an-honest-answer-from-someone-who-s-run-both-145278.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/do-you-still-need-airflow-for-snowflake-pipelines-an-honest-answer-from-someone-whos-run-both-0e8d4a5a9036?source=rss----34b6daafc07---4>)

Author: Sanket Prabhu

Published: 2026-11-20T01:56:59Z

Content type: opinion

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [Snowflake streaming data architecture](<https://devfeed.tech/topics/snowflake-streaming-data-architecture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [airflow](<https://devfeed.tech/tags/airflow.md>), [apache-airflow](<https://devfeed.tech/tags/apache-airflow.md>), [dag](<https://devfeed.tech/tags/dag.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [task-graph](<https://devfeed.tech/tags/task-graph.md>)

### AI overview

Snowflake task graphs may now cover many pipelines that previously needed Airflow, but the new graph object, atomic deployments, advanced branching, and DCM support are described as Preview features. The article says native graphs suit end-to-end Snowflake workloads owned by one team, with data arriving in Snowflake and a preference for centralized lineage, logs, cost, and access. Airflow remains useful for cross-system dependencies, routine date-range backfills, and a company-wide orchestration control plane; Preview risk may also argue against moving critical production pipelines. A suggested middle ground is to let Airflow handle external readiness and triggers, then execute one Snowflake task graph for retries, branching, notifications, and transformations. Regular tasks with AFTER dependencies are identified as generally available.

### Source excerpt

Snowflake task graphs just grew up. That doesn't mean your DAGs are obsolete. Apache Airflow and Snowflake Graph Every time Snowflake ships a new orchestration feature, I see the same post on my feed: "Airflow is dead." I don't buy it. But I also don't buy the opposite reflex, where every Snowflake pipeline gets an Airflow DAG by default because "that's how we do orchestration here." I've run Airflow in production and I've spent about a decade building data platforms on Snowflake. Over that time, my answer to "do we need Airflow for this?" has changed more than once. With the task graph changes Snowflake released in late October, it changed again. If every step of your pipeline already runs inside Snowflake, Airflow is often a second system you're paying to babysit. That's the short version. The longer version has some important exceptions. Status note up front: the new TASK GRAPH object, atomic deployments, advanced branching and DCM DEFINE TASK GRAPH are all in Preview as of this writing (released Oct 23 and Oct 27, 2026). Regular tasks with AFTER dependencies have been GA for a long time. 1. Why Airflow ended up in so many Snowflake stacks It's worth being fair to Airflow here. Most teams didn't choose it by accident. For years, native Snowflake tasks were fine for simple chains but awkward for real pipelines: Configuration was scattered across every task in the graph Changing a running graph meant suspending the root, editing tasks one by one, and resuming Branching was limited. A child ran when its predecessors succeeded, and handling a failure path cleanly took workarounds Deployment wasn't atomic. A half-applied change could leave the graph in a state nobody intended So teams reached for an orchestrator that already handled all of that. My team was using Airflow because of the operator versatility. Is that still the right call today? 2. What actually changed in October Two releases matter here. Task graphs as a first-class object (Preview, Oct 23). You can no

## Why My Kids are Learning to Program - The New Baseline

DevFeed: [Why My Kids are Learning to Program - The New Baseline](<https://devfeed.tech/articles/why-my-kids-are-learning-to-program-the-new-baseline-146236.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/why-my-kids-are-learning-to-program/>)

Author: Shai Almog

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

Content type: opinion

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Learning](<https://devfeed.tech/topics/learning.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [backend](<https://devfeed.tech/tags/backend.md>), [business-processes](<https://devfeed.tech/tags/business-processes.md>), [kids](<https://devfeed.tech/tags/kids.md>), [learning](<https://devfeed.tech/tags/learning.md>), [program](<https://devfeed.tech/tags/program.md>), [programmers](<https://devfeed.tech/tags/programmers.md>), [ship](<https://devfeed.tech/tags/ship.md>)

### AI overview

The article argues that coding agents can now build, test and submit complete Codename One apps through a single conversation, including cloud builds and store submission gated by user-approved permissions. Because agents can sound convincing while producing incorrect code, the author says learning Java and understanding architecture, testing and failure modes remain important for judging and directing their work. The article also argues that generated code is costly to maintain, making a broad framework valuable; it cites Codename One's 4.5 million lines and cross-platform testing costs. For enterprises that cannot send code or data outside their network, it describes an optional on-premises or dedicated private-cloud Corporate Server. The excerpt also details additions including a million-row grid and spreadsheet engine, tenant-aware backend features, PDF tools, scheduling, diagrams, and a game studio.

### Source excerpt

An agent can now build and ship an app to the stores with no programmer involved. That's exactly why programmers matter more: the baseline moved, and the apps worth building got much bigger.

## Java4Shell: GitLab helps find and remediate a critical Java flaw

DevFeed: [Java4Shell: GitLab helps find and remediate a critical Java flaw](<https://devfeed.tech/articles/java4shell-gitlab-helps-find-and-remediate-a-critical-java-flaw-146875.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/java4shell-critical-java-flaw-how-gitlab-helps/>)

Author: Daniel Abeles

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

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [x86](<https://devfeed.tech/topics/x86.md>)

Tags: [base64](<https://devfeed.tech/tags/base64.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cpus](<https://devfeed.tech/tags/cpus.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [java](<https://devfeed.tech/tags/java.md>), [java-flaw](<https://devfeed.tech/tags/java-flaw.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [november-17](<https://devfeed.tech/tags/november-17.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [option](<https://devfeed.tech/tags/option.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [security-labs](<https://devfeed.tech/tags/security-labs.md>), [security-research](<https://devfeed.tech/tags/security-research.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Java4Shell is a memory corruption flaw in optimized Base64 decoding in recent x86-64 Java runtimes; researchers demonstrated unauthenticated remote code execution in several products' default configurations. The excerpt says GitLab assessed its own managed infrastructure as not exploitable, while proactively upgrading one component containing the affected bundle. It recommends upgrading Java runtimes from 17.0.6 onward to listed fixed builds or distribution patches; until then, `-XX:-UseBASE64Intrinsics` disables the vulnerable optimization with a slight performance cost and requires restarting Java processes. For discovery, it pairs static checks (package and optional binary container scanning, Orbit, and Java/Kotlin project filters) with runtime workload inventories, since each view can miss Java installations. It also outlines GitLab Duo agent workflows for proposing per-project fixes, with human review and merge.

### Source excerpt

GitLab has internally assessed the impact of Java4Shell, and concluded it is not exploitable in GitLab-managed infrastructure. Exploitation requires a specific combination of conditions, which we confirmed are not present in our production environment. A single component was found to contain the impacted bundle in its runtime environment, which we are proactively upgrading as a hardening measure. On November 17, 2026, OpenJDK, the project that most Java runtimes are built from, fixed a memory corruption flaw known as Java4Shell (CVE-2026-114938, CVSS 8.1) in the optimized java.util.Base64 decoding used on recent x86-64 CPUs. Web servers and frameworks routinely decode Base64 values from users, such as authentication headers and cookies, before the application sees the request. Researchers have demonstrated unauthenticated remote code execution in the default configurations of several widely used Java products. Upgrade Java to a fixed version now To mitigate this issue, upgrade every Java runtime from 17.0.6 onward, including unsupported releases such as Java 18 and 24, to a build based on OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1, or to your distribution's patched package. If you can't upgrade right away, turn off the vulnerable optimization with the -XX:-UseBASE64Intrinsics JVM option. Here are fixed builds and packages as of November 19: Vendor or distributionFixed build or packageOpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1Eclipse Temurin17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, 27.0.1.1+4Amazon Corretto17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4Azul Zulu17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1BellSoft Liberica17.0.21.1+5, 21.0.13.1+5, 25.0.5.1+5, 27.0.1.1+5SapMachine17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1Microsoft Build of OpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1Oracle Java SE 8 Performance Pack8u513-perf. Other Java 8 builds aren't affectedUbuntu 26.10, 26.04, 24.04, 22.04openjdk-17 17.0.21.1, openjdk-21 21.0.13.1, openjdk-25 25.0.5.1, and on 26.10

## Android developer verification will reach every install source, with a side door for power users

DevFeed: [Android developer verification will reach every install source, with a side door for power users](<https://devfeed.tech/articles/android-developer-verification-will-reach-every-install-source-with-a-side-door-for-power-users-144524.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/20/android-developer-verification-power-users/>)

Author: Anamarija Pogorelec

Published: 2026-11-19T23:03:24Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [appstores](<https://devfeed.tech/topics/appstores.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2027](<https://devfeed.tech/tags/2027.md>), [android](<https://devfeed.tech/tags/android.md>), [android-developer-verification](<https://devfeed.tech/tags/android-developer-verification.md>), [app](<https://devfeed.tech/tags/app.md>), [app-stores](<https://devfeed.tech/tags/app-stores.md>), [apps](<https://devfeed.tech/tags/apps.md>), [country](<https://devfeed.tech/tags/country.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [devices](<https://devfeed.tech/tags/devices.md>), [experience](<https://devfeed.tech/tags/experience.md>), [extend](<https://devfeed.tech/tags/extend.md>), [galaxy](<https://devfeed.tech/tags/galaxy.md>), [galaxy-store](<https://devfeed.tech/tags/galaxy-store.md>), [google](<https://devfeed.tech/tags/google.md>), [identity-verification](<https://devfeed.tech/tags/identity-verification.md>), [install](<https://devfeed.tech/tags/install.md>), [mobile-devices](<https://devfeed.tech/tags/mobile-devices.md>), [mobile-security](<https://devfeed.tech/tags/mobile-security.md>), [news](<https://devfeed.tech/tags/news.md>), [power-users](<https://devfeed.tech/tags/power-users.md>), [smartphones](<https://devfeed.tech/tags/smartphones.md>), [source](<https://devfeed.tech/tags/source.md>), [users](<https://devfeed.tech/tags/users.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

Starting in January 2027, Google plans to extend developer verification worldwide across Android install sources. On certified devices, unregistered apps will lose the normal install experience; the rollout begins with Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo, then expands to sideloading and open-source registries. Google says registration takes under ten minutes. Students and hobbyists can use limited distribution accounts without registration fees or government ID checks, with sharing allowed to 50 authorized devices. Teams can automate registration using two APIs. Play developers must also register apps distributed outside Play. Google describes an advanced flow for experienced users to install unregistered apps if they accept the risk, while retaining guardrails against social engineering scams. The excerpt says verification already applies at participating stores in Brazil, Indonesia, Singapore and Thailand; Google reports registered apps account for over 99% of worldwide Android installs.

### Source excerpt

Google will extend Android developer verification to every country starting in January 2027, a check that already applies at participating app stores in four countries. Developers who have not verified their identity with Google and registered their apps will see those apps lose the normal install experience on certified Android devices. The rollout opens with seven app distributors: Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo. Over several months it widens to every ... More -> The post Android developer verification will reach every install source, with a side door for power users appeared first on Help Net Security.

## Introducing CodePen Commander, a CLI tool (cdpn) to manage your CodePen 2.0 Pens

DevFeed: [Introducing CodePen Commander, a CLI tool (cdpn) to manage your CodePen 2.0 Pens](<https://devfeed.tech/articles/introducing-codepen-commander-a-cli-tool-cdpn-to-manage-your-codepen-2-0-pens-144562.md>)

Original publisher: [Read original article](<https://www.bram.us/2026/11/19/codepen-commander-cli-tool-cdpn/>)

Author: Bramus!

Published: 2026-11-19T22:51:03Z

Content type: article

Language: en

Sources: [Bram.us](<https://devfeed.tech/sources/bram-us.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [codepen](<https://devfeed.tech/tags/codepen.md>), [command](<https://devfeed.tech/tags/command.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [local](<https://devfeed.tech/tags/local.md>), [manage](<https://devfeed.tech/tags/manage.md>), [npm](<https://devfeed.tech/tags/npm.md>), [original-content](<https://devfeed.tech/tags/original-content.md>), [pens](<https://devfeed.tech/tags/pens.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [rules](<https://devfeed.tech/tags/rules.md>), [sync](<https://devfeed.tech/tags/sync.md>), [terminal](<https://devfeed.tech/tags/terminal.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

CodePen Commander (`cdpn`) syncs local folders with CodePen 2.0 Pens using API v2, and supports publishing, deployment, domain management, privacy settings, and other Pen operations from the terminal. It requires Node.js 20 or newer and a CodePen API key; named profiles are stored under `~/.cdpn` with owner-only permissions, and key selection can use a profile flag, environment variable, folder configuration, or Pen owner matching. The Git-like workflow supports cloning, checking status, pulling, and pushing text edits, binary assets, and deletions as one version; pushes wait for CodePen's build and may write compiler patches back to local files. Classic Pen conversion requires a manual browser step, and forking is limited to the user's own Pens. Data and state commands offer non-interactive JSON output for scripts and CI.

### Source excerpt

I scratched my own itch (again 😅) and built CodePen Commander -- a CLI cdpn command to sync local folders with CodePen 2.0 Pens, deploy them, and manage privacy rules right from the terminal.

## How the BMW Group governs hundreds of agents across thousands of developers

DevFeed: [How the BMW Group governs hundreds of agents across thousands of developers](<https://devfeed.tech/articles/how-the-bmw-group-governs-hundreds-of-agents-across-thousands-of-developers-144472.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/how-the-bmw-group-governs-hundreds-of-agents-across-thousands-of-developers/>)

Author: Dr. Jens Kohl

Published: 2026-11-19T22:20:23Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>)

Tags: [2023](<https://devfeed.tech/tags/2023.md>), [a2a](<https://devfeed.tech/tags/a2a.md>), [a2a-protocol](<https://devfeed.tech/tags/a2a-protocol.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [agent-infrastructure](<https://devfeed.tech/tags/agent-infrastructure.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [automotive](<https://devfeed.tech/tags/automotive.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bmw](<https://devfeed.tech/tags/bmw.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-scale](<https://devfeed.tech/tags/enterprise-scale.md>), [governance](<https://devfeed.tech/tags/governance.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [practices](<https://devfeed.tech/tags/practices.md>), [quality](<https://devfeed.tech/tags/quality.md>), [scale](<https://devfeed.tech/tags/scale.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

BMW Group's approach to governing agents across its R&D organization centers on reusable architecture and lifecycle controls that let teams experiment while enforcing safety, security, quality, and compliance. Governance rules live outside individual agents--in integration layers, a central registry, and deterministic CI/CD and policy checks--so they can survive framework or model changes. Teams set autonomy per workflow step, from explicit human approval to bounded autonomy, and increase it based on evaluation evidence. Agents are built from composable MCP tools, skills, and flows, with specialized agents and least-privilege access used to contain complexity. CI pipelines run tests, security and governance checks, and ground-truth evaluations before deployment; runtime monitoring flags data or model drift for human review. IaC templates, shared registries, and centrally curated checks support distributed team contributions without mandating a single framework. The article describes these practices and reported benefits but provides no quantitative outcome measures.

### Source excerpt

When hundreds of agents serve thousands of developers, governance cannot be an afterthought. The BMW Group shares the practices and patterns its R&D teams use to build, govern, and operate AI agents at enterprise scale without sacrificing speed, quality, or compliance.

## NIST SP 800-218 and Kubernetes: what policy can enforce

DevFeed: [NIST SP 800-218 and Kubernetes: what policy can enforce](<https://devfeed.tech/articles/nist-sp-800-218-and-kubernetes-what-policy-can-enforce-144282.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/20/nist-sp-800-218-ssdf-and-kubernetes-which-controls-policy-can-enforce/>)

Author: Ritesh Patel

Published: 2026-11-19T20:41:35.692178Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [policy-as-code](<https://devfeed.tech/topics/policy-as-code.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [federal information processing standards](<https://devfeed.tech/topics/federal-information-processing-standards.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [admission](<https://devfeed.tech/tags/admission.md>), [ci](<https://devfeed.tech/tags/ci.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [continuous-compliance](<https://devfeed.tech/tags/continuous-compliance.md>), [image-verification](<https://devfeed.tech/tags/image-verification.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-policy](<https://devfeed.tech/tags/kubernetes-policy.md>), [kubernetes-supply-chain-security](<https://devfeed.tech/tags/kubernetes-supply-chain-security.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>), [nist](<https://devfeed.tech/tags/nist.md>), [pod-security](<https://devfeed.tech/tags/pod-security.md>), [policy](<https://devfeed.tech/tags/policy.md>), [records](<https://devfeed.tech/tags/records.md>), [settings](<https://devfeed.tech/tags/settings.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

The excerpt maps NIST SP 800-218 v1.1's 42 active practices to enforcement: three can be checked at Kubernetes admission, eleven through CI gates, and the remaining 28 require records or human review. Admission checks cover approved image registries, image provenance attestations, and a baseline for deployed pods; they cannot establish that an image's SBOM is complete or that software itself has secure defaults. CI gates can check code and tests, pinned build tools, approved dependencies, and artifact signing and archiving. The mapping is the guide's classification, not NIST guidance. It recommends starting the Kyverno registry policy and Pod Security checks in audit or warning mode, reviewing findings before enforcement; registry examples must be customized, and the policy does not cover custom resources that create pods.

### Source excerpt

NIST SP 800-218 names no cluster settings. Admission policy can enforce 3 of its 42 practices, CI gates can check 11, and 28 need records or human review.

## An engineer didn't message his AI for 22 of 44 days. It built an Android app anyway.

DevFeed: [An engineer didn't message his AI for 22 of 44 days. It built an Android app anyway.](<https://devfeed.tech/articles/an-engineer-didn-t-message-his-ai-for-22-of-44-days-it-built-an-android-app-anyway-144301.md>)

Original publisher: [Read original article](<https://thenewstack.io/cognition-devin-bots-management/>)

Author: Amanda Caswell

Published: 2026-11-19T20:22:18Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.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-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [automation](<https://devfeed.tech/tags/automation.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [bots](<https://devfeed.tech/tags/bots.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [build](<https://devfeed.tech/tags/build.md>), [ci](<https://devfeed.tech/tags/ci.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [code-verification](<https://devfeed.tech/tags/code-verification.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cognition](<https://devfeed.tech/tags/cognition.md>), [compute](<https://devfeed.tech/tags/compute.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [devin](<https://devfeed.tech/tags/devin.md>)

### AI overview

Devin Bots shifts Cognition's Devin from handling individual tickets to coordinating coding sessions around ongoing goals. For an Android app project, Cognition says a Bot assigned tickets to Devin sessions, merged changes after CI and Devin Review, and sent daily Slack updates. Over 44 days it merged 1,134 pull requests; its overseeing engineer sent no messages on 22 days. The app is in Google Play open testing but still needs work to match the iOS version. Cognition also says its Layout Bot ran visual checks every three hours and engineers merged 159 fixes over three weeks, reducing layout lag by 70%. Oversight remains a limitation: Cognition has not explained how Bots resolve conflicts among parallel agents, decide code is ready to merge, or escalate repeated failures. Tasks needing approval go to a "Needs You" inbox; engineers can protect CI checks and set compute spending limits.

### Source excerpt

Cognition has spent nearly three years developing Devin as an autonomous engineer that takes a ticket and ships a pull The post An engineer didn't message his AI for 22 of 44 days. It built an Android app anyway. appeared first on The New Stack.

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

## Me and my son made a vibe coding app for kids!

DevFeed: [Me and my son made a vibe coding app for kids!](<https://devfeed.tech/articles/me-and-my-son-made-a-vibe-coding-app-for-kids-144247.md>)

Original publisher: [Read original article](<https://stack.convex.dev/vibe-coding-app-for-kids>)

Author: Stack

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

Content type: article

Language: en

Sources: [Stack](<https://devfeed.tech/sources/stack.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Image](<https://devfeed.tech/topics/image.md>), [ipad](<https://devfeed.tech/topics/ipad.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [bdd](<https://devfeed.tech/tags/bdd.md>), [behind-the-scenes](<https://devfeed.tech/tags/behind-the-scenes.md>), [convex](<https://devfeed.tech/tags/convex.md>), [games](<https://devfeed.tech/tags/games.md>), [kids](<https://devfeed.tech/tags/kids.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [state-machines](<https://devfeed.tech/tags/state-machines.md>), [ui](<https://devfeed.tech/tags/ui.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

### AI overview

Let's Build It is a Convex-backed iPhone and iPad app that lets children create and revise games by voice. A Convex job turns a conversation into a brief with GPT-6 Sol, adds an image-generated mockup and design notes, then uses GPT-6 Sol again to write HTML, CSS and JavaScript. The author says the process takes about a minute; Sol was selected through blind comparisons for a balance of cost, speed and quality, currently costing about 16 cents per project. Three development lessons emerge: define expected behavior in plain-English BDD stories and enforce it with end-to-end tests, verify that tests check every detail they claim to cover, and model project/version status as discriminated unions to prevent conflicting database states. For UI work, the author found broad restyling attempts ineffective and improved results by iterating on individual screens in Storybook against mockups.

### Source excerpt

This is Let's Build It, a Convex powered iPhone and iPad app that lets kids build their own apps and games just by talking to it. I've been building it with my son Josh for the past year or so. Here's what's going on behind the scenes, why getting the UI to look right was a bit of a nightmare, and three lessons I learnt along the way: BDD, state machines and how I picked which model builds the games.

## Automate Spring 5.3.x CVE remediation with Lightwell

DevFeed: [Automate Spring 5.3.x CVE remediation with Lightwell](<https://devfeed.tech/articles/automate-spring-5-3-x-cve-remediation-with-lightwell-144329.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/19/automate-spring-5-3-x-cve-remediation-lightwell>)

Author: Vivek Koul, Shailendra Kumar Singh

Published: 2026-11-19T14:16:40Z

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: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Spring Framework](<https://devfeed.tech/topics/spring-framework.md>), [ibm red hat project lightwell](<https://devfeed.tech/topics/ibm-red-hat-project-lightwell.md>), [Spring Boot](<https://devfeed.tech/topics/spring-boot.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Ansible](<https://devfeed.tech/topics/ansible.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [automate](<https://devfeed.tech/tags/automate.md>), [build](<https://devfeed.tech/tags/build.md>), [common-vulnerabilities-and-exposures](<https://devfeed.tech/tags/common-vulnerabilities-and-exposures.md>), [common-vulnerabilities-and-exposures-cve](<https://devfeed.tech/tags/common-vulnerabilities-and-exposures-cve.md>), [cve](<https://devfeed.tech/tags/cve.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [developer](<https://devfeed.tech/tags/developer.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [failed](<https://devfeed.tech/tags/failed.md>), [framework](<https://devfeed.tech/tags/framework.md>), [gate](<https://devfeed.tech/tags/gate.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [java](<https://devfeed.tech/tags/java.md>), [latest](<https://devfeed.tech/tags/latest.md>), [latest-release](<https://devfeed.tech/tags/latest-release.md>), [lightwell](<https://devfeed.tech/tags/lightwell.md>), [manage](<https://devfeed.tech/tags/manage.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [remediation](<https://devfeed.tech/tags/remediation.md>), [security](<https://devfeed.tech/tags/security.md>), [spring](<https://devfeed.tech/tags/spring.md>), [spring-boot](<https://devfeed.tech/tags/spring-boot.md>)

### AI overview

Spring Framework 5.3.x has no free upstream fix for CVE-2025-41249: the line ended at 5.3.39, which is also affected, while moving to Spring 6 requires Java 17 and a `javax` to `jakarta` migration. The article demonstrates a pipeline that reports vulnerabilities separately from a policy gate, then optionally replaces only `spring-core` with a binary-compatible Lightwell backport. It warns that Spring Boot's BOM and artifact version need separate Maven properties so the dependency tree still resolves. Before deployment, the pipeline keylessly signs and verifies the image through Red Hat Trusted Artifact Signer, publishes its CycloneDX SBOM to Trusted Profile Analyzer, and checks the image with Advanced Cluster Security. Event-Driven Ansible can launch remediation automatically from critical or high severity alerts and record the alert-to-workflow chain. The excerpt also recommends querying OSV.dev to identify affected versions and applications.

### Source excerpt

If you manage pipelines or platform security for Java teams running Spring Framework 5.3.x, this is how to automate remediation without forcing application rewrites. Your build failed a security gate. The scanner is right. There's a high-severity Common Vulnerabilities and Exposures (CVE) in a dependency you ship to production, so you do the obvious thing and upgrade to the latest release on that line. The build fails again. The CVE is still there. The post Automate Spring 5.3.x CVE remediation with Lightwell appeared first on Red Hat Developer.

## Fig Announces Elastic Integration to Help Security Teams Protect Detection Coverage as Data Changes

DevFeed: [Fig Announces Elastic Integration to Help Security Teams Protect Detection Coverage as Data Changes](<https://devfeed.tech/articles/fig-announces-elastic-integration-to-help-security-teams-protect-detection-coverage-as-data-changes-143905.md>)

Original publisher: [Read original article](<https://hackernoon.com/fig-announces-elastic-integration-to-help-security-teams-protect-detection-coverage-as-data-changes?source=rss>)

Author: Kevin John

Published: 2026-11-19T14:09:46Z

Content type: news

Language: en

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

Topics: [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [changes](<https://devfeed.tech/tags/changes.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [detection](<https://devfeed.tech/tags/detection.md>), [detection-as-code](<https://devfeed.tech/tags/detection-as-code.md>), [detection-coverage](<https://devfeed.tech/tags/detection-coverage.md>), [detection-coverage-validation](<https://devfeed.tech/tags/detection-coverage-validation.md>), [detection-engineering](<https://devfeed.tech/tags/detection-engineering.md>), [detection-rule-drift](<https://devfeed.tech/tags/detection-rule-drift.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [elastic-security](<https://devfeed.tech/tags/elastic-security.md>), [integration](<https://devfeed.tech/tags/integration.md>), [map](<https://devfeed.tech/tags/map.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [secops](<https://devfeed.tech/tags/secops.md>), [secops-cicd](<https://devfeed.tech/tags/secops-cicd.md>), [security](<https://devfeed.tech/tags/security.md>), [security-data-lineage](<https://devfeed.tech/tags/security-data-lineage.md>), [security-data-pipelines](<https://devfeed.tech/tags/security-data-pipelines.md>), [siem-migrations](<https://devfeed.tech/tags/siem-migrations.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

Fig's Elastic Security integration maps data sources through pipelines, mappings and fields to the detection rules that depend on them. Using a read-only API key, Fig retrieves Elastic configuration and identifies detections affected when upstream data changes, pinpoints breaks and recommends fixes. Teams can test changes against their own data before production, then ship validated changes as code through CI/CD with version control and one-click rollback. For migrations to Elastic, Elastic Automatic Migration translates existing rules; Fig checks them against destination data before cutover and flags rules needing rework. Elastic provides its platform and prebuilt integrations and rules, while Fig focuses on data dependencies and change validation.

### Source excerpt

Fig announces an Elastic Security integration to help SecOps teams map data dependencies, validate detection changes, and protect coverage during migrations.

## Exclusive: Fig Security partners with Elastic to show how data changes affect detection coverage

DevFeed: [Exclusive: Fig Security partners with Elastic to show how data changes affect detection coverage](<https://devfeed.tech/articles/exclusive-fig-security-partners-with-elastic-to-show-how-data-changes-affect-detection-coverage-143693.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/19/exclusive-fig-security-partners-with-elastic-to-show-how-data-changes-affect-detection-coverage/>)

Author: Duncan Riley

Published: 2026-11-19T14:00:04Z

Content type: news

Language: en

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

Topics: [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [automatic-import](<https://devfeed.tech/tags/automatic-import.md>), [automatic-migration](<https://devfeed.tech/tags/automatic-migration.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [changes](<https://devfeed.tech/tags/changes.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [detection](<https://devfeed.tech/tags/detection.md>), [detection-coverage](<https://devfeed.tech/tags/detection-coverage.md>), [detection-rules](<https://devfeed.tech/tags/detection-rules.md>), [drift](<https://devfeed.tech/tags/drift.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [elastic-security](<https://devfeed.tech/tags/elastic-security.md>), [fig-security](<https://devfeed.tech/tags/fig-security.md>), [gal-shafir](<https://devfeed.tech/tags/gal-shafir.md>), [google-cloud-security](<https://devfeed.tech/tags/google-cloud-security.md>), [integration](<https://devfeed.tech/tags/integration.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [jamie-hynds](<https://devfeed.tech/tags/jamie-hynds.md>), [mapping](<https://devfeed.tech/tags/mapping.md>), [news](<https://devfeed.tech/tags/news.md>), [nir-loya-dahan](<https://devfeed.tech/tags/nir-loya-dahan.md>), [operations](<https://devfeed.tech/tags/operations.md>), [partners](<https://devfeed.tech/tags/partners.md>), [partnership](<https://devfeed.tech/tags/partnership.md>), [platform](<https://devfeed.tech/tags/platform.md>), [roy-haimof](<https://devfeed.tech/tags/roy-haimof.md>), [secops](<https://devfeed.tech/tags/secops.md>), [security](<https://devfeed.tech/tags/security.md>), [security-data-lineage](<https://devfeed.tech/tags/security-data-lineage.md>), [security-information-and-event-management](<https://devfeed.tech/tags/security-information-and-event-management.md>), [security-operations](<https://devfeed.tech/tags/security-operations.md>), [startup](<https://devfeed.tech/tags/startup.md>), [team8](<https://devfeed.tech/tags/team8.md>), [ten-eleven-ventures](<https://devfeed.tech/tags/ten-eleven-ventures.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>)

### AI overview

Fig Security's integration with Elastic Security maps data sources through pipelines, mappings, and fields to the detection rules that depend on them. Fig says it identifies rules affected by data changes and suggests repairs, helping teams detect coverage gaps even when rules remain active. Teams can test changes against their own environment and ship them as code with CI/CD, version control, and one-click rollback. For migrations, Fig checks rules translated by Elastic Automatic Migration against available Elastic data and flags rules needing rework with recommended fixes. The article describes the integration as available now; these capabilities are presented as company claims.

### Source excerpt

Security operations startup Fig Security Inc. today announced an integration partnership with Elastic N.V. that it says gives security teams visibility into how data changes affect their detection coverage. The partnership sees Fig's capabilities for mapping detection dependencies now integrating with Elastic Security, the open security operations platform from Elastic. The platform offers prebuilt integrations [...] The post Exclusive: Fig Security partners with Elastic to show how data changes affect detection coverage appeared first on SiliconANGLE.

## How I Use AI to Turn Digital Health Product Ideas into an Executable Backlog

DevFeed: [How I Use AI to Turn Digital Health Product Ideas into an Executable Backlog](<https://devfeed.tech/articles/how-i-use-ai-to-turn-digital-health-product-ideas-into-an-executable-backlog-144757.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/digital-health-product-backlog/>)

Author: Nathaniel Gittlen

Published: 2026-11-19T13:00:09Z

Content type: tutorial

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>), [roadmaps](<https://devfeed.tech/topics/roadmaps.md>)

Tags: [acceptance](<https://devfeed.tech/tags/acceptance.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-for-developers](<https://devfeed.tech/tags/ai-for-developers.md>), [app](<https://devfeed.tech/tags/app.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-devops](<https://devfeed.tech/tags/azure-devops.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [build](<https://devfeed.tech/tags/build.md>), [developer](<https://devfeed.tech/tags/developer.md>), [digital](<https://devfeed.tech/tags/digital.md>), [digital-health](<https://devfeed.tech/tags/digital-health.md>), [feature](<https://devfeed.tech/tags/feature.md>), [health](<https://devfeed.tech/tags/health.md>), [meeting](<https://devfeed.tech/tags/meeting.md>), [product](<https://devfeed.tech/tags/product.md>), [roadmap](<https://devfeed.tech/tags/roadmap.md>), [team](<https://devfeed.tech/tags/team.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The author describes a phased AI skill for turning digital health product concepts into developer-ready backlogs. It gathers briefs, designs and existing code; confirms scope, assumptions and priorities with the human before drafting; then builds epics and stories with plain-language descriptions, checkable acceptance criteria, technical details, dependencies and exclusions. The agent verifies claims against code, drafts each story for approval before saving, and uses placeholders where designs are unfinished. Stories are kept current in Markdown and Jira or Azure DevOps, with numbering and cross-references maintained by a companion skill. The author reports using the process on three projects, including planning six weeks of work for a prosthetic-arm calibration app. It works best with clear near-term priorities, code access and an available decision-maker; it cannot resolve unclear priorities. The author recommends detailing the first two weeks, planning later work more loosely, and balancing foundational engineering with visible progress when a concept is still forming.

### Source excerpt

Every product team has the same gap. On one side is a concept: a product brief, a roadmap item, a feature someone sketched in a meeting. On the other is a backlog a developer can pick up and build. Closing that gap is usually slow, manual work. In digital health, it also has to be [...] The post How I Use AI to Turn Digital Health Product Ideas into an Executable Backlog appeared first on Atomic Spin.

## AI Software Factory Building Blocks for 2027

DevFeed: [AI Software Factory Building Blocks for 2027](<https://devfeed.tech/articles/ai-software-factory-building-blocks-for-2027-143902.md>)

Original publisher: [Read original article](<https://hackernoon.com/ai-software-factory-building-blocks-for-2027?source=rss>)

Author: QA.tech

Published: 2026-11-19T12:17:47Z

Content type: article

Language: en

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

Topics: [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [2027](<https://devfeed.tech/tags/2027.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [addy-osmani](<https://devfeed.tech/tags/addy-osmani.md>), [agentic-coding](<https://devfeed.tech/tags/agentic-coding.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-software](<https://devfeed.tech/tags/ai-software.md>), [ai-software-building-blocks](<https://devfeed.tech/tags/ai-software-building-blocks.md>), [ai-software-factory](<https://devfeed.tech/tags/ai-software-factory.md>), [ai-testing](<https://devfeed.tech/tags/ai-testing.md>), [autonomous-software-engineerin](<https://devfeed.tech/tags/autonomous-software-engineerin.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [building](<https://devfeed.tech/tags/building.md>), [can](<https://devfeed.tech/tags/can.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [factory](<https://devfeed.tech/tags/factory.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-factory](<https://devfeed.tech/tags/software-factory.md>), [tools](<https://devfeed.tech/tags/tools.md>), [trust](<https://devfeed.tech/tags/trust.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

An AI software factory runs multiple coding agents in parallel on queued work, with automated checks and review gates. Because code generation can scale faster than verification, safe autonomy depends on checking the running product, not just the diff: unit tests check code, review bots inspect changes, and an independent QA agent can exercise user goals on a live app. The excerpt describes verification before a PR through MCP tools in Claude Code, Cursor, or Codex, and PR checks against a preview deployment (or staging after merge), reporting pass, fail, or unable to verify. It recommends previews, running-app checks on every PR, risk-based review gates, and increasing autonomy only as verification capacity allows. Human judgment remains important for regulated domains, legacy systems, and usability decisions; the source favors a light factory for many teams and warns that dark factories can increase comprehension debt.

### Source excerpt

Eight building blocks of an AI software factory, the tools behind them, and why verification determines how much autonomy you can trust.

## Keeping your databases up to date: From upstream release to you

DevFeed: [Keeping your databases up to date: From upstream release to you](<https://devfeed.tech/articles/keeping-your-databases-up-to-date-from-upstream-release-to-you-144299.md>)

Original publisher: [Read original article](<https://blog.ovhcloud.com/en/posts/managed-database-image-updates/>)

Author: Elena Luoto

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

Content type: article

Language: en

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

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [staging](<https://devfeed.tech/topics/staging.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [builds](<https://devfeed.tech/topics/builds.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [version](<https://devfeed.tech/topics/version.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [api](<https://devfeed.tech/tags/api.md>), [apt](<https://devfeed.tech/tags/apt.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [automation](<https://devfeed.tech/tags/automation.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [builds](<https://devfeed.tech/tags/builds.md>), [databases](<https://devfeed.tech/tags/databases.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [image](<https://devfeed.tech/tags/image.md>), [pre-production](<https://devfeed.tech/tags/pre-production.md>), [production](<https://devfeed.tech/tags/production.md>), [release](<https://devfeed.tech/tags/release.md>), [sign-off](<https://devfeed.tech/tags/sign-off.md>), [tests](<https://devfeed.tech/tags/tests.md>), [upstream](<https://devfeed.tech/tags/upstream.md>), [upstream-release](<https://devfeed.tech/tags/upstream-release.md>), [version](<https://devfeed.tech/tags/version.md>), [weekly](<https://devfeed.tech/tags/weekly.md>)

### AI overview

Emile checks 15 engine/version pairs weekly and skips rebuilding when the current production tag matches the newest upstream package; for Valkey, it checks GitHub, and accepts a version only once release notes appear. When a rebuild is needed, it starts from clean Debian using shared Packer and Ansible recipes. New images go to a snapshot registry and must pass pre-production checks, including upgrades from current and earlier major versions. A team member manually approves promotion from the master branch; afterward, 5% of the production fleet moves to the image daily in randomized customer order. Builds also fail when vendor defaults have changed, prompting human review. If no version is new, a manual rebuild remains available for base-image fixes and follows the same tests and approval gate.

### Source excerpt

Learn how we keep databases up to date: a weekly version check, clean image builds, pre-production tests, and a human sign-off before release.

## Who Changed the AI Agent's Rules? Measuring How AI Coding Agents Escalate Authority in CI/CD Pipelines

DevFeed: [Who Changed the AI Agent's Rules? Measuring How AI Coding Agents Escalate Authority in CI/CD Pipelines](<https://devfeed.tech/articles/who-changed-the-ai-agent-s-rules-measuring-how-ai-coding-agents-escalate-authority-in-ci-cd-pipelines-142128.md>)

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

Author: Miroslaw Staron

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

Content type: article

Language: en

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

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>)

Tags: [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [framework](<https://devfeed.tech/tags/framework.md>), [governance](<https://devfeed.tech/tags/governance.md>), [model](<https://devfeed.tech/tags/model.md>), [risk](<https://devfeed.tech/tags/risk.md>)

### AI overview

The study evaluates a joint penalty model combining execution cost and governance risk across 932,791 agent-authored pull requests from five coding agents. Control-plane changes had a higher mean joint penalty than data-plane changes (0.498 vs. 0.218) and higher mean governance risk (0.530 vs. 0.135); all 775 extreme-risk pull requests modified the control plane. Policy-violation flags appeared in 46.6% of control-plane pull requests and 63.6% of merged ones. Mean joint penalty varied by agent, from 0.166 for Cursor to 0.328 for Copilot, with differences not explained by execution cost or merge rate. Manual review of 34 pull requests gave the authority-scope classifier a Cohen's kappa of 0.72. These findings suggest the metric can support risk detection and agent-specific authority tuning, though the supplied text describes an abstract rather than the full study.

### Source excerpt

arXiv:2611.23251v1 Announce Type: new Abstract: AI coding agents can modify CI/CD control-plane structures, including workflows and permission settings, thereby extending their authority beyond routine code changes. Because such modifications can affect an entire development pipeline, this study examines the trade-off between execution cost and governance risk in agentic CI/CD. We introduce a joint penalty model, P(M), that combines these two dimensions and evaluate it on all 932,791 agent-authored pull requests in the AIDev dataset, covering five autonomous coding agents. Each pull request is automatically classified by authority scope - data-plane or control-plane - and assigned a penalty score. We found that control-plane actions have a 2.3x higher mean joint penalty than data-plane actions (0.498 vs. 0.218) and a 3.9x higher mean governance risk (0.530 vs. 0.135), which means that they indeed increase the risk. All 775 pull requests in the extreme-risk category, defined as P(M) > 0.8, modify the control plane. Policy-violation flags occur in 46.6% of all control-plane pull requests and in 63.6% of merged control-plane pull requests. We have also found an indication that governance risk differs substantially across agent implementations, ranging from 0.166 for Cursor to 0.328 for Copilot in mean joint penalty. These differences are not explained by execution cost or merge rate, suggesting that authority policies should be calibrated for individual agents. Manual assessment of 34 pull requests yielded a Cohen's kappa of 0.72 for the authority-scope classifier. The results show that a single compound metric can identify and measure changes to CI/CD governance structures at scale. The proposed framework supports detecting high-risk pull requests and comparing governance behavior across agent implementations, providing a basis for authority tuning and pipeline governance in agentic software development.

## Rotate a leaked GitLab token and let GitLab Duo fix the code

DevFeed: [Rotate a leaked GitLab token and let GitLab Duo fix the code](<https://devfeed.tech/articles/rotate-a-leaked-gitlab-token-and-let-gitlab-duo-fix-the-code-144779.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/secret-detection-token-rotate-and-fix/>)

Author: Mark Mishaev

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

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>)

Tags: [acting](<https://devfeed.tech/tags/acting.md>), [actions](<https://devfeed.tech/tags/actions.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [beta](<https://devfeed.tech/tags/beta.md>), [branch](<https://devfeed.tech/tags/branch.md>), [build](<https://devfeed.tech/tags/build.md>), [can](<https://devfeed.tech/tags/can.md>), [cd](<https://devfeed.tech/tags/cd.md>), [chat](<https://devfeed.tech/tags/chat.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code](<https://devfeed.tech/tags/code.md>), [duo](<https://devfeed.tech/tags/duo.md>), [features](<https://devfeed.tech/tags/features.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [let](<https://devfeed.tech/tags/let.md>), [product](<https://devfeed.tech/tags/product.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Starting with GitLab 19.6 beta for GitLab Ultimate, an active leaked GitLab PAT can be rotated from its vulnerability finding: GitLab revokes it, stores a replacement in Secrets Manager, and GitLab Duo opens an MR to update CI/CD jobs. The replacement value is not shown to the user or agent; rotation happens before the agent starts. Review and merge the MR, then resolve the finding. Rotation is immediate and irreversible, and the replacement is scoped to the current project, so scripts outside GitLab CI/CD or jobs in other projects need another token. The feature supports GitLab PATs, including fine-grained PATs, but not other detected secret types. GitLab.com users can rotate their own tokens; Self-Managed administrators can also rotate others' tokens. If the Duo session fails, rotation and secret storage still occur, leaving code updates manual. A dependency-free CLI can batch-rotate group findings and eligible CI/CD variable tokens; it defaults to dry-run, caps runs at 10 rotations unless configured, and omits token values from reports.

### Source excerpt

Secret detection alerts you when an active personal access token (PAT) is exposed in your default branch. Acting on that finding is harder: revoking the token breaks dependent pipelines, and replacing it safely takes several manual steps. While the finding waits in your vulnerability report, the token stays live. Starting in GitLab 19.6 in beta for GitLab Ultimate, you can remediate a leaked GitLab PAT directly from the vulnerability page. Select Rotate and fix, and GitLab revokes the token, stores a replacement in GitLab Secrets Manager, and uses GitLab Duo Agent Platform to open a merge request (MR) to update your CI/CD jobs. You review and merge the MR. GitLab never exposes the new token value to you or your agents. Why leaked tokens stay active after detection Imagine that secret detection flags an active PAT in deploy.sh: export GITLAB_TOKEN="glpat-..." Fixing this manually requires tracking down the token's owner, revoking it, generating a replacement with matching scopes, storing it securely, and opening MRs to update your scripts and CI/CD jobs. Because this process is tedious, remediations often stall or go wrong: The finding ages: Nobody wants to break the pipeline, so the finding sits in the vulnerability report while the token remains active. The fix stops halfway: Someone revokes the token immediately, breaking the build. In a rush to recover, they paste a replacement into a less secure CI/CD variable. The new token leaks: Someone shares the replacement token in a chat thread so a teammate can configure it. In the gap between detected and rotated, the token still works for anyone who can read the repository. Rotate and fix in a snap The Rotate and fix function closes this gap by combining secret detection and validity checks, GitLab Secrets Manager, and GitLab Duo Agent Platform. When you open an active PAT finding and select AI actions > Fix with AI > Rotate and fix, GitLab: Revokes the leaked token and creates a replacement with the same name, scopes,

## GitLab 19.6 released

DevFeed: [GitLab 19.6 released](<https://devfeed.tech/articles/gitlab-19-6-released-144780.md>)

Original publisher: [Read original article](<https://docs.gitlab.com/releases/19/gitlab-19-6-released/>)

Author: GitLab

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

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [1-5](<https://devfeed.tech/tags/1-5.md>), [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>), [actions](<https://devfeed.tech/tags/actions.md>), [added](<https://devfeed.tech/tags/added.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [after](<https://devfeed.tech/tags/after.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>), [availability](<https://devfeed.tech/tags/availability.md>), [duo](<https://devfeed.tech/tags/duo.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [slack](<https://devfeed.tech/tags/slack.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

GitLab 19.6 adds governance, agent workflows, faster merge request reviews, and security controls. MCP server tool calls now create audit events, while group Owners can deny tools, require approval, or allow them (the control is in beta). Duo in Slack is in limited availability on GitLab.com; `/goal` starts long-running Developer Flow sessions that can commit, push, and create merge requests without per-action approval, and scheduled automations are in beta. Rapid Diffs is generally available, streaming server-rendered diffs; the first file is reported to appear in about 1.5 seconds versus 4.5 seconds previously. Security updates include Rust scanning in Advanced SAST (added in 19.5 and still beta), malware rules for merge request approvals requiring SBOM-based dependency scanning, and configurable pipeline-variable limits. Web search in Agentic Chat is off by default and requires group or instance enablement; searches create audit events. The notes also flag upgrade guidance, including potential custom NGINX configuration breaks after the bundled version update.

### Source excerpt

GitLab 19.6 released with GitLab Duo in Slack in limited availability on GitLab.com

## Cut your vulnerability backlog with agentic remediation

DevFeed: [Cut your vulnerability backlog with agentic remediation](<https://devfeed.tech/articles/cut-your-vulnerability-backlog-with-agentic-remediation-144776.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/gitlab-agentic-remediation/>)

Author: Mark Settle

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

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [Agentic SOC](<https://devfeed.tech/topics/agentic-soc.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-remediation](<https://devfeed.tech/tags/agentic-remediation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-reasoning](<https://devfeed.tech/tags/ai-reasoning.md>), [api](<https://devfeed.tech/tags/api.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [application-security-testing](<https://devfeed.tech/tags/application-security-testing.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [context](<https://devfeed.tech/tags/context.md>), [cves](<https://devfeed.tech/tags/cves.md>), [developer](<https://devfeed.tech/tags/developer.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [duo](<https://devfeed.tech/tags/duo.md>), [features](<https://devfeed.tech/tags/features.md>), [product](<https://devfeed.tech/tags/product.md>), [remediation](<https://devfeed.tech/tags/remediation.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

GitLab 19.6 adds tools to scale vulnerability triage and remediation while keeping fixes under normal developer review and approval. Security managers can apply automated triage and remediation (ATR) profiles across projects by group or attribute, choosing Conservative, Standard, or Proactive settings for severity and automatic versus on-demand flows; ATR profiles require GitLab Ultimate. Vulnerability Context Flow, in beta for Ultimate, adds SAST risk context such as authentication requirements, sensitive-data handling, and exposure to untrusted input. A security dashboard MTTR chart tracks weekly fixes across first-party code and dependencies, with project, severity, and scan-type filters; it excludes dismissed findings and counts only vulnerabilities detected in the prior 90 days. Business Logic Security Analyzer is in beta: Ultimate customers can enable it themselves on GitLab.com, while Self-Managed and Dedicated customers must contact GitLab for access. Agents can propose fixes and rerun tests and scans, but developers review changes and existing approvals still apply.

### Source excerpt

Vulnerability backlogs are growing faster than teams can clear them. AI writes more code and finds more flaws, while fixes still move at human speed. NIST's National Vulnerability Database has already published twice as many CVEs in 2026 as in all of 2025, and ceased enriching most CVEs this past April. Compounding the problem, a finding that looks safe to defer may not stay that way. Attackers now use AI to find and exploit flaws in hours, even those long written off as theoretical. In October, frontier models uncovered PHP2Shell, a pair of unauthenticated remote code execution bugs in PHP that had been dismissed as unexploitable in 2012. Discovery and exploitation now run at machine speed. To keep up, defenders need agentic security tools that detect and remediate vulnerabilities with minimal manual effort while leaving teams in full control. GitLab 19.6 helps teams shrink their security findings backlog. Security managers can now turn on agentic triage and remediation across entire groups of projects without scripting against the API. A new agentic flow adds exploitability context to static application security testing (SAST) findings, so teams can prioritize the ones that pose real risk. Security leaders can then track the results on a new mean time to remediation (MTTR) chart. Find and fix faster with agentic security GitLab 19.6 builds on a platform that finds and fixes vulnerabilities with agentic security. GitLab Duo security agents use frontier AI reasoning to examine your codebase and every merge request for the logic flaws scanners miss, while built-in scanners catch known vulnerabilities from source to runtime. Agents filter out false positives before they reach a developer's queue, then help teams prioritize the rest by severity, exploitability, reachability, and blast radius. GitLab Orbit, our native knowledge graph, grounds that reasoning in the live state of your system. For confirmed findings, an agent writes a fix, opens a merge request, and trigge

[Next page](<https://devfeed.tech/topics/cicd.md?cursor=WyIyMDI2LTExLTE5VDAwOjAwOjAwKzAwOjAwIiwgIjQ1ZmQwMTZkLTNhOTAtNDgzYi1hYjE0LTNjOTFiNWQwMTZmMSJd>)