<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - DevOps - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ DevOps News feed</description>
    <item>
      <title>More Incidents Don't Necessarily Mean Less Reliability</title>
      <link>https://www.infoq.com/news/2026/08/incidents-reliability-metrics/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/incidents-reliability-metrics/en/headerimage/generatedHeaderImage-1785853951990.jpg"/&gt;&lt;p&gt;One of the most common assumptions in engineering leadership is that a rising number of reported incidents signals declining system reliability. However, a recent article from Great Circle argues that the opposite is often true: an increase in incident counts may actually indicate that an organization's incident management culture is improving.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>Service Reliability</category>
      <category>Metrics</category>
      <category>Incident Response</category>
      <category>Observability</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/incidents-reliability-metrics/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-08-14T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/incidents-reliability-metrics/en</dc:identifier>
    </item>
    <item>
      <title>Kubeflow Expands AI Capabilities as CNCF Graduation Nears</title>
      <link>https://www.infoq.com/news/2026/08/kubeflow/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/kubeflow/en/headerimage/generatedHeaderImage-1786662140696.jpg"/&gt;&lt;p&gt;The Kubeflow project has unveiled several technical updates to enhance distributed AI and high-performance computing on Kubernetes. These advancements include Kale 2.0, a modernised SDK with native Spark support, and expanded capabilities for the Kubeflow Trainer. The developments arrive as the project moves towards graduation from the Cloud Native Computing Foundation.&lt;/p&gt; &lt;i&gt;By Matt Saunders&lt;/i&gt;</description>
      <category>Kubernetes</category>
      <category>AIOps</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 14 Aug 2026 08:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/kubeflow/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Matt Saunders</dc:creator>
      <dc:date>2026-08-14T08:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/kubeflow/en</dc:identifier>
    </item>
    <item>
      <title>Anthropic's Claude Breaches Sandbox During Model Security Evaluations</title>
      <link>https://www.infoq.com/news/2026/08/claude-sandox-breach/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Anthropic conducted an audit of 141006 evaluation runs after OpenAI's sandbox escape disclosure. The review identified three incidents where Claude models accessed the internet due to misconfigurations. These incidents involved unauthorised attacks on live targets. Anthropic has suspended offensive evaluations and plans to enhance security measures and collaborate with external auditors.&lt;/p&gt; &lt;i&gt;By Olimpiu Pop&lt;/i&gt;</description>
      <category>Frontier Model</category>
      <category>Cloud Security</category>
      <category>Security Breach</category>
      <category>Large language models</category>
      <category>AI Security</category>
      <category>Model Evaluation</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Thu, 13 Aug 2026 10:10:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/claude-sandox-breach/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Olimpiu Pop</dc:creator>
      <dc:date>2026-08-13T10:10:00Z</dc:date>
      <dc:identifier>/news/2026/08/claude-sandox-breach/en</dc:identifier>
    </item>
    <item>
      <title>Netflix Adopts Cloud-Native Job Queueing System Kueue to Replace an In-House Solution</title>
      <link>https://www.infoq.com/news/2026/08/netflix-kueue-kubernetes-batch/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/netflix-kueue-kubernetes-batch/en/headerimage/generatedHeaderImage-1786536066027.jpg"/&gt;&lt;p&gt;Netflix migrated most of its batch workloads onto Kueue, an open-source cloud-native batch job execution system that has outgrown its homegrown solution over the years. The company mapped the capabilities previously created in-house to Kueue’s functionality and also benefited from new features that would have been costly to incorporate into its homegrown solution.&lt;/p&gt; &lt;i&gt;By Rafał Gancarz&lt;/i&gt;</description>
      <category>Batch Processing</category>
      <category>Cloud Native Architecture</category>
      <category>Kubernetes</category>
      <category>Cell-Based Architecture</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Wed, 12 Aug 2026 14:30:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/netflix-kueue-kubernetes-batch/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Rafał Gancarz</dc:creator>
      <dc:date>2026-08-12T14:30:00Z</dc:date>
      <dc:identifier>/news/2026/08/netflix-kueue-kubernetes-batch/en</dc:identifier>
    </item>
    <item>
      <title>MCP Goes Stateless, and Developers Ask Whether That Just Makes It an API Again</title>
      <link>https://www.infoq.com/news/2026/08/mcp-stateless-gateway/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/mcp-stateless-gateway/en/headerimage/generatedHeaderImage-1786118533592.jpg"/&gt;&lt;p&gt;The MCP 2026-07-28 specification removes the initialize handshake and session header, and adds required method and tool-name headers so gateways can route agent traffic without parsing JSON. Reaction split between developers calling it a rediscovery of REST and those arguing the standard itself was always the point.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>API Gateway</category>
      <category>Cloudflare</category>
      <category>Cloud</category>
      <category>Serverless</category>
      <category>Standardization</category>
      <category>AI Architecture</category>
      <category>Model Context Protocol (MCP)</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Wed, 12 Aug 2026 09:48:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/mcp-stateless-gateway/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-12T09:48:00Z</dc:date>
      <dc:identifier>/news/2026/08/mcp-stateless-gateway/en</dc:identifier>
    </item>
    <item>
      <title>IBM and Red Hat Expand Lightwell to Strengthen Trust and Governance for AI-Era Open Source</title>
      <link>https://www.infoq.com/news/2026/08/lightwell-ai-open-source/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/lightwell-ai-open-source/en/headerimage/generatedHeaderImage-1785852993652.jpg"/&gt;&lt;p&gt;IBM and Red Hat have announced an expansion of Lightwell, introducing new commercial offerings designed to help organizations establish trusted, verifiable software supply chains for the age of AI-assisted software development.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>Open Source</category>
      <category>Cloud</category>
      <category>Artificial Intelligence</category>
      <category>IBM</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Tue, 11 Aug 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/lightwell-ai-open-source/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-08-11T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/lightwell-ai-open-source/en</dc:identifier>
    </item>
    <item>
      <title>JetBrains Details its First Steps to Bring Rapidly Growing AI Spend under Control</title>
      <link>https://www.infoq.com/news/2026/08/jetbrains-ai-spend/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/jetbrains-ai-spend/en/headerimage/generatedHeaderImage-1786384052458.jpg"/&gt;&lt;p&gt;JetBrains has described how it began centralising AI usage after development-related spending increased roughly tenfold in six months. Rather than restricting engineers to a small set of approved tools, the company built a shared access and accounting layer intended to preserve tool choice while giving teams greater visibility and control over consumption.&lt;/p&gt; &lt;i&gt;By Matt Foster&lt;/i&gt;</description>
      <category>Generative AI</category>
      <category>Cost Optimization</category>
      <category>FinOps</category>
      <category>Platform Engineering</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Tue, 11 Aug 2026 07:25:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/jetbrains-ai-spend/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Matt Foster</dc:creator>
      <dc:date>2026-08-11T07:25:00Z</dc:date>
      <dc:identifier>/news/2026/08/jetbrains-ai-spend/en</dc:identifier>
    </item>
    <item>
      <title>How Pinterest Secures AWS Infrastructure at Scale with a Centralized Terraform Pipeline</title>
      <link>https://www.infoq.com/news/2026/08/pinterest-secures-aws-infra/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/pinterest-secures-aws-infra/en/headerimage/generatedHeaderImage-1786109760765.jpg"/&gt;&lt;p&gt;Pinterest has revealed the Resource Provisioner Pipeline (RPP), its own Terraform execution engine. It ensures least-privilege access and needs dual-control reviews. This is important for the company’s AWS infrastructure, as it adds strict guardrails to the GitHub Actions workflows.&lt;/p&gt; &lt;i&gt;By Claudio Masolo&lt;/i&gt;</description>
      <category>AWS</category>
      <category>Cloud Security</category>
      <category>GitHub Actions</category>
      <category>Terraform</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Mon, 10 Aug 2026 10:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/pinterest-secures-aws-infra/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Claudio Masolo</dc:creator>
      <dc:date>2026-08-10T10:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/pinterest-secures-aws-infra/en</dc:identifier>
    </item>
    <item>
      <title>GitHub Code Quality Targets Maintainability as AI-Generated Code Increases</title>
      <link>https://www.infoq.com/news/2026/08/github-code-quality/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/github-code-quality/en/headerimage/generatedHeaderImage-1786036140230.jpg"/&gt;&lt;p&gt;GitHub Code Quality is now generally available on GitHub Enterprise Cloud and GitHub Team. The service combines CodeQL analysis with AI-assisted detection of maintainability and reliability problems, then uses Copilot Autofix to suggest changes for review in pull requests, according to an announcement from GitHub.&lt;/p&gt; &lt;i&gt;By Matt Saunders&lt;/i&gt;</description>
      <category>AI Assisted Coding</category>
      <category>github</category>
      <category>Code Quality</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Mon, 10 Aug 2026 08:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/github-code-quality/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Matt Saunders</dc:creator>
      <dc:date>2026-08-10T08:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/github-code-quality/en</dc:identifier>
    </item>
    <item>
      <title>Buildpacks Move the Container Hardening Control Point Away from the Dockerfile</title>
      <link>https://www.infoq.com/news/2026/08/buildpacks-dockerfile-patching/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/buildpacks-dockerfile-patching/en/headerimage/header-1786050230489.jpeg"/&gt;&lt;p&gt;Cloud Native Buildpacks, which graduated within the CNCF in July 2026, move base image choice out of per-service Dockerfiles into a single builder owned by platform engineering, enabling fleet-wide patching. BellSoft's hardened Paketo builder is the latest sign that vendors now treat the builder, not the Dockerfile, as the container security control point.&lt;/p&gt; &lt;i&gt;By Mark Silvester&lt;/i&gt;</description>
      <category>Cloud Native Computing Foundation</category>
      <category>Application Security</category>
      <category>Platform Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Mon, 10 Aug 2026 07:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/buildpacks-dockerfile-patching/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Mark Silvester</dc:creator>
      <dc:date>2026-08-10T07:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/buildpacks-dockerfile-patching/en</dc:identifier>
    </item>
    <item>
      <title>Stripe Uses Graph Search and State Machines to Automate Database Remediation</title>
      <link>https://www.infoq.com/news/2026/08/database-remediation-graph/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/database-remediation-graph/en/headerimage/generatedHeaderImage-1785167911858.jpg"/&gt;&lt;p&gt;The engineering team at Stripe recently described how they automated database incident recovery by modeling their global infrastructure as a graph. Using graph search algorithms together with state machines, the team computes and executes remediation plans automatically.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>GraphDB</category>
      <category>MongoDB</category>
      <category>State-machine</category>
      <category>Database</category>
      <category>Site Reliability Engineering</category>
      <category>Incident Response</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Sun, 09 Aug 2026 06:55:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/database-remediation-graph/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-08-09T06:55:00Z</dc:date>
      <dc:identifier>/news/2026/08/database-remediation-graph/en</dc:identifier>
    </item>
    <item>
      <title>GitHub Hardens npm and Actions Defaults, Drawing Debate over Delays versus Signing</title>
      <link>https://www.infoq.com/news/2026/08/github-npm-actions-defaults/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/github-npm-actions-defaults/en/headerimage/generatedHeaderImage-1785830307506.jpg"/&gt;&lt;p&gt;GitHub consolidated the npm and Actions changes it shipped from March to July 2026 against supply chain attacks, several of which alter defaults rather than add options. Hacker News discussion focused less on the individual controls than on whether waiting periods are the right instrument, or a substitute for author-side package signing.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Software Supply Chain</category>
      <category>Automation</category>
      <category>GitHub Actions</category>
      <category>Open Source</category>
      <category>github</category>
      <category>Continuous Delivery</category>
      <category>Security</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Sat, 08 Aug 2026 07:45:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/github-npm-actions-defaults/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-08T07:45:00Z</dc:date>
      <dc:identifier>/news/2026/08/github-npm-actions-defaults/en</dc:identifier>
    </item>
    <item>
      <title>Instacart Builds Blueberry, an AI-Powered Assistant to Help On-Call Engineers Investigate Incidents</title>
      <link>https://www.infoq.com/news/2026/08/instacart-blueberry-sre-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/instacart-blueberry-sre-ai/en/headerimage/generatedHeaderImage-1785721280661.jpg"/&gt;&lt;p&gt;Instacart introduced Blueberry, an AI-assisted incident response system that helps on-call engineers investigate production issues faster. It combines AI agents, operational data, and historical incident knowledge to generate grounded root cause hypotheses in Slack. It uses parallel subagents, MCP integrations, and incident history to reduce investigation time while keeping engineers in control.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Reliability</category>
      <category>Large language models</category>
      <category>Artificial Intelligence</category>
      <category>Site Reliability Engineering</category>
      <category>Model Context Protocol (MCP)</category>
      <category>Operational Intelligence</category>
      <category>Developer Experience</category>
      <category>Slack</category>
      <category>Incident Response</category>
      <category>Platform Engineering</category>
      <category>Observability</category>
      <category>Development</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 14:34:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/instacart-blueberry-sre-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-08-07T14:34:00Z</dc:date>
      <dc:identifier>/news/2026/08/instacart-blueberry-sre-ai/en</dc:identifier>
    </item>
    <item>
      <title>AI Is Transforming Incident Response - But the Hardest Problems May Still Belong to Humans</title>
      <link>https://www.infoq.com/news/2026/08/ai-incident-response/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/ai-incident-response/en/headerimage/generatedHeaderImage-1785503516175.jpg"/&gt;&lt;p&gt;Artificial intelligence is rapidly changing how engineering teams respond to production incidents, offering the ability to summarize incident channels, analyze unfamiliar code, suggest remediation steps, generate pull requests, and increasingly assist with diagnosis.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>Artificial Intelligence</category>
      <category>Observability</category>
      <category>Incident Response</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/ai-incident-response/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-08-07T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/ai-incident-response/en</dc:identifier>
    </item>
    <item>
      <title>Rootly Drops Small PR Rule as Agentic AI Changes Code Review Economics</title>
      <link>https://www.infoq.com/news/2026/08/rootly-small-pr-agentic-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/rootly-small-pr-agentic-ai/en/headerimage/generatedHeaderImage-1786029342014.jpg"/&gt;&lt;p&gt;Incident management platform provider Rootly has published an account of its decision to drop its long-standing small pull request rule, arguing that the practice no longer serves its purpose now that AI agents generate most of its code. The company describes a shift from measuring PR size to assessing blast radius, with feature flags and rollback capability taking precedence over line counts.&lt;/p&gt; &lt;i&gt;By Matt Saunders&lt;/i&gt;</description>
      <category>Agents</category>
      <category>Code Reviews</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 08:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/rootly-small-pr-agentic-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=DevOps-news</guid>
      <dc:creator>Matt Saunders</dc:creator>
      <dc:date>2026-08-07T08:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/rootly-small-pr-agentic-ai/en</dc:identifier>
    </item>
  </channel>
</rss>
