platformchangelog.dev
43 tools

Platform Changelog: what shipped in platform engineering, developer experience and DevOps

feedsince 2026-10-26patches hidden unless security or breaking
2026-10-301 day ago
InfoQ: Netflix Titus Adds Single-Tenant VM Isolation for ContainerspostNetflix added a single-tenant mode to its Titus container platform that runs one task alone on a right-sized EC2 instance, with the Compute/Platform team still owning host patching. The post says first adopters are stateful, high-throughput streaming workloads and that shared-kernel tuning did not fully close the performance isolation gap. Netflix describes the mode's launch latency cost and that it published no benchmark scores.platform teamsPlatform teams running shared Kubernetes can borrow the pattern of dedicated tainted node pools with anti-affinity and repacking disabled, which Netflix recommends only for large, long-running, disruption-sensitive workloads. The trade-off is slower launches and lower packing efficiency for small instances.InfoQ ↗Kubernetes MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
CNCF: The boundary problem in agentic AI is a platform problempostThe post argues that the risk of autonomous agents comes from tools and credentials that accumulate beyond what anyone decided, and that instructions alone cannot hold an agent to its scope. It proposes a Safe Operating Model with concentric rings: verified workload identity, declared service-mesh reach, admission-controlled and per-call capability checks, and data-plane authorization keyed to that identity. The agent's own identity is denied rights to modify the objects that define its authority, and changes go through reviewed version-controlled configuration. The source text is cut off before the concrete integration work it refers to.platform teamsPlatform teams would enforce agent boundaries through workload identity, mesh authorization, admission policy on tool bindings, and per-invocation gateway checks, with agent authority changes made only through reviewed config. The article is a conceptual model and names no specific tools or releases in the text provided.CNCF Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The New Stack: Why MCP servers should tell agents what to do nextpostAWS developer advocate James Ward argues that MCP servers should return guidance with data, telling the agent what it just did, what it might do next, and where to find more. He describes AWS adding a session ID parameter to tools so individual calls can be traced as one journey, with a second parameter carrying the user's goal for evaluation. Ward also said AWS ships a CLI and skills alongside MCP because MCP's OAuth model cannot switch between AWS profiles the way the CLI can.platform teamsPlatform teams exposing MCP servers can add session and goal parameters to tools and build evals that compare user intent with agent paths, then adjust tool descriptions or batch tools based on observed patterns. The article presents these as AWS practices rather than a released standard, so no protocol change is implied.The New Stack ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The New Stack: Why Kubernetes platforms keep rebuilding a layer they could sharepostThe article argues that many Kubernetes tools rebuild the same composition layer for grouping resources, ordering them, and passing values between them. It describes kro's ResourceGraphDefinition, which expresses dependencies as CEL references that set order, and kro 0.10's Graph primitive, which runs composition without a custom API. The author suggests composition could be a shared primitive in Kubernetes.platform teamsPlatform teams that write glue controllers or ordering logic between Helm, Argo CD or Crossplane resources can consider expressing dependencies as references in one shared composition layer. Teams adopting it would take on ownership of every API they publish, since schema changes can break existing instances.The New Stack ↗kroHelmArgo CDCrossplanewritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The New Stack: The 5 essential layers of AI agent sandboxing on KubernetespostThe article lays out five layers for isolating AI agent workloads on Kubernetes: the isolation runtime (runc, gVisor, or Kata Containers), node configuration, access controls on network, credentials and storage, RuntimeClass selection in the pod request, and the Agent Sandbox project for session management. It gives a RuntimeClass and Pod example and notes that runtime overhead should be measured rather than copied from examples. The piece is written from Oracle Cloud Infrastructure's perspective and describes community projects as the basis for its approach.platform teamsPlatform teams running agents on shared clusters need to choose a sandbox runtime, configure nodes for it, and add its measured overhead to RuntimeClass so scheduling and quotas account for it. Egress default-deny, short-lived task-scoped credentials, and separate authorization for MCP servers and APIs outside the sandbox also fall to the platform team.The New Stack ↗Kubernetes MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
InfoQ: Datadog Builds a Specialist AI Model for SRE InvestigationsannouncementDatadog has released Scout, a model trained with reinforcement learning to investigate production alerts inside its Bits Investigation AI SRE product. It is in closed preview with Datadog engineers and a small number of customers. Datadog says Scout matched larger models on its own AlertEval benchmark at a lower estimated inference cost, and resolved 71 to 80 of 90 faults on the public SREGym set depending on effort level.platform teamsPlatform and SRE teams evaluating AI incident investigation should note that the cost and benchmark figures come from Datadog's own tests and no prices are published, so independent results are needed. Scout only diagnoses and proposes recovery actions, and an engineer still makes any change.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
GitLab Orbit: Find vulnerability blast radius without the manual huntannouncementGitLab has made Orbit generally available for Premium and Ultimate customers, starting on GitLab.com with Self-Managed and GitLab Dedicated to follow. Orbit builds a graph from merge requests, pipelines, deployments, security findings and ownership data so users can ask which projects contain a vulnerable component and who owns them. GitLab's Security Analyst Agent and external agents such as Claude Code and Codex can query the same graph over MCP, subject to existing roles.platform teamsPlatform teams on GitLab can use the graph to map which services, base images and pipelines depend on a shared component, instead of assembling that list from scanners and spreadsheets. Teams should still check the graph against runtime inventory, since it only covers what repositories declare on the default branch.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
GitLab Orbit is GA: Higher agent accuracy, lower token costannouncementGitLab announced general availability of Orbit, a context graph that indexes code, merge requests, pipelines, deployments, vulnerabilities and ownership for GitLab customers. GitLab says agents connected to Orbit needed up to 45x fewer retries and used up to 4.5x fewer tokens on the same tasks, based on its own testing. Orbit is available to Premium and Ultimate customers on GitLab.com first, with Self-Managed and Dedicated following, and is priced as a shared pool of queries.platform teamsPlatform teams using GitLab could query dependency, pipeline and ownership data through MCP or REST instead of building their own graph, but the efficiency figures are vendor-reported and unverified. Teams should budget for the per-organization query pool, which costs $30 per user per month for 1,000 queries plus about $0.03 per query beyond the pool.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
From one prompt to a governed Dataverse app: the Dataverse plugin lands in Copilot CoworkannouncementMicrosoft announced that the Dataverse plugin is now available in Copilot Cowork. The post demonstrates a workflow where a single prompt creates Dataverse tables, relationships, sample data and a published app, with each change shown to the user as an approval card before it happens. The app runs in Microsoft Copilot Managed Runtime (preview), and building in Cowork currently requires enrollment in the Frontier program.platform teamsPlatform teams that govern Power Platform get an agent path into Dataverse where the connection signs in as the user and is limited by Dataverse security roles, with changes requiring approval and resulting in ordinary solution-ready tables. The post does not describe new admin controls beyond existing Microsoft 365 admin center visibility.Microsoft Power Platform Blog ↗Microsoft Power PlatformAgentforcewritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon Bedrock AgentCore CLI version 1.0 is now availablepostAWS made Amazon Bedrock AgentCore CLI version 1.0 (@aws/agentcore 1.0.0) generally available. The rebuilt CLI offers faster startup, a consistent command structure, and support for more AgentCore resources including harnesses, runtimes, memory, identity, gateways, and payments. Existing projects can be moved to version 1 with a new agentcore migrate command.platform teamsPlatform teams that evaluate or support AgentCore get a terminal tool to create, deploy and operate agent resources, with the ability to work on resources by ID or ARN without a project. Teams with existing AgentCore projects will need to run the migration command to move to version 1.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon EKS Dashboard now provides fleet-wide visibility into certificate authority (CA) rotationannouncementAmazon EKS announced CA rotation visibility in the Amazon EKS Dashboard, which shows CA rotation status across clusters, clusters with CAs approaching expiration, and upcoming automated rotation events. The dashboard aggregates data across accounts and Regions through AWS Organizations, requires trusted access enabled in the management account, and is available at no additional cost. The source says CA rotation support extends to all commercial AWS Regions.platform teamsPlatform teams operating many EKS clusters can check CA rotation status and upcoming rotation events from one dashboard instead of per cluster. Enabling it requires trusted access for the dashboard in the organization's management account.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon ECS Managed Instances adds cross-instance and Spot consolidationannouncementAmazon ECS Managed Instances added cross-instance consolidation, which evaluates and repacks tasks across multiple underutilized instances together instead of one instance at a time. It also added Spot consolidation, which consolidates underutilized Spot Instances after verifying replacement capacity is available. AWS says the features are available at no additional cost in all Regions and apply automatically to existing and new capacity providers.platform teamsPlatform teams running ECS Managed Instances with narrow instance type ranges may see fewer instances and higher utilization without configuration changes. In AWS's own test with 261 tasks, the fleet dropped from 19 to 13 instances, which AWS reports as a sign of the savings but has not been independently verified.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon EKS Auto Mode now supports Kubernetes Gateway APIpostAmazon EKS Auto Mode now supports the Kubernetes Gateway API, letting users configure application load balancing with Gateway and HTTPRoute resources. EKS Auto Mode provisions and manages the underlying AWS load balancing infrastructure. Existing Ingress resources continue to work alongside Gateway API resources.platform teamsPlatform teams on EKS Auto Mode can adopt Gateway API for HTTP and gRPC routing, cross-namespace routing, weighted splitting and header-based routing without installing a separate controller. Standard charges apply for the AWS load balancing resources provisioned.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The New Stack: What happens when the agent is long gone, but its access key lives on?postThe article argues that access keys created for agents or deployments persist after their tasks end, since AWS IAM user access keys do not expire automatically. It provides a CloudQuery SQL query to list active IAM keys older than 90 days and unused for 90 days, and an env zero OPA policy that denies creation of selected long-lived credential types in Terraform and OpenTofu plans. It also notes that TTL-driven teardown does not guarantee revocation and shows AWS CLI commands to deactivate a specific key.platform teamsPlatform teams running agent or deployment pipelines can use the inventory query and deploy-time policy to find and block long-lived keys, but must still verify revocation separately, since TTL destroys and policies do not cover credentials created outside managed deployments.The New Stack ↗Terraform MCP ServerOpenTofuAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon ECS now supports GPU sharing with NVIDIA Multi-Process Service (MPS)announcementAmazon ECS now supports GPU sharing using NVIDIA Multi-Process Service (MPS), so multiple ECS tasks can run concurrently on a single NVIDIA GPU. Users set a GPU memory amount per container and can optionally cap GPU compute share, and ECS places tasks on GPUs with spare capacity during scaling and deployments. It is available on ECS Managed Instances and ECS on EC2 in all AWS commercial and GovCloud (US) Regions.platform teamsPlatform teams running GPU workloads on ECS can increase GPU utilization by packing tasks per instance, which AWS says reduces infrastructure cost, with no application code changes. On ECS Managed Instances, ECS monitors the MPS control daemon and replaces unhealthy instances, moving tasks to healthy capacity.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The New Stack: The hidden failure paths that affect Kubernetes control plane availabilitypostThe article describes three control plane failure paths: an extension API server that published an invalid OpenAPI v2 schema after a dependency upgrade, which made Helm reject charts using only core resources; a DaemonSet rolling restart whose many agents rebuilt cluster-wide Pod informers at once, creating a request storm; and a deep liveness probe on a component in the API request path that restarted it repeatedly during a dependency outage. The author recommends testing the published OpenAPI documents, narrowing informer watch scopes, and reconsidering probe contracts. The source text is cut off before the KMS section finishes.platform teamsPlatform teams running aggregated API servers should fetch and validate /openapi/v2 and /openapi/v3 output after upgrades, since process health checks do not catch schema breakage. Teams running DaemonSet agents should narrow informer scopes and consider how recovery restarts synchronize list calls.The New Stack ↗Helmwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The New Stack: One pod, one node: The architecture behind serverless Kubernetes on AWSpostThe article walks through how Amazon EKS Fargate places a pod: a mutating admission webhook assigns it to a Fargate scheduler before the default scheduler can claim it, the scheduler requests dedicated capacity, and a node runtime registers the pod's environment. It also describes three network namespaces, one ENI per pod, and EKS periodically replacing pods for security patching via the Eviction API. The piece is an architectural explainer and does not announce a new release.platform teamsPlatform teams using Fargate should plan for one ENI and private subnet capacity per pod, a pod-level patching cycle that respects PodDisruptionBudgets, and the lack of DaemonSets, host networking, EBS volumes and GPUs. Every pod must match a Fargate profile.The New Stack ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
CNCF: OpenTelemetry-powered distributed tracing and Kubernetes events in OpenChoreopostOpenChoreo, a CNCF Sandbox internal developer platform, uses the OpenTelemetry Collector to add distributed tracing to its observability plane. A local Collector in each data plane receives OTLP spans, enriches them with Kubernetes metadata via k8sattributes, applies tail sampling, and exports to a central Collector or cloud backend. The article also describes a custom Collector distribution with a k8seventenrich processor that persists Kubernetes events with OpenChoreo labels beyond the API server's default retention of about an hour.platform teamsPlatform teams running OpenChoreo or a similar IDP get traces and persisted, labeled Kubernetes events in the portal and through the observability MCP server. Teams building their own pipeline can reuse the pattern of pod-association enrichment for spans and informer-cache enrichment for events, which needs a custom processor because events do not map to pods.CNCF Blog ↗Kubernetes MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Extend GitLab Duo Agent Platform into your business systemspostGitLab published a tutorial showing how Salesforce can call a custom GitLab Duo Agent Platform flow through the Flows API when an Apex error occurs. The flow reads the repository, identifies a likely cause and suspect commit, and opens a GitLab issue with the analysis. The tutorial limits the agent to four read tools and one issue-creation tool, and uses a project access token and Named Credential.platform teamsPlatform teams that manage Salesforce metadata in GitLab could adapt this pattern to route runtime errors to agent triage with narrow privileges and an audit trail. Teams must still handle data stripping, token scoping, and privilege limits before production use, and the tutorial omits response checks, retries, and tests.GitLab Blog ↗GitLabSalesforce PlatformAgentforcewritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Continuous Delivery Office Hours Ep.12: The platform adoption shockpostA Continuous Delivery Office Hours episode discusses mandatory versus optional platform adoption, citing Octopus Deploy's Future of Platform Engineering report. The source says platforms now have about six times as many features as before, that mandatory platforms outperform optional ones on goal attainment, and that platforms meeting more goals have more budget security. The hosts argue platform teams must show value in terms the organization understands.platform teamsPlatform teams evaluating adoption policy get a reasoned argument to pair optional adoption with mandatory standards and to track developer satisfaction and feedback. Teams should also expect to justify funding with metrics, since the source warns that platforms without demonstrated value risk being defunded.Octopus Deploy Blog ↗Octopus DeployState of Platform Engineering reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-265 days ago
Fluxv2.10.0minorbreaking++~~~~~~~~~~~~~~~*Flux v2.10.0 shipped with 94 changes: 10 added, 73 changed, 4 fixed, and 4 marked breaking. Breaking changes include object identity always on with a narrowed default RBAC (no create on serviceaccounts/token), notification Alert and Provider APIs promoted to v1 with dropped v1beta3 fields, the artifact storage backend becoming the default for ImageRepository tag database, and a change to kubeConfig audiences key. The release also adds SPIFFE mTLS between controllers, OCIRepository as a HelmRelease chart source, and Zoom, incident.io and Mastodon notification providers, and updates Kubernetes to 1.37 and Go to 1.27.platform teamsPlatform teams upgrading Flux must bind a ClusterRole with serviceaccounts/token create permission to the controller ServiceAccount if they rely on default RBAC, and migrate v1beta3 notification resources to v1. Expect a full ImageRepository rescan after upgrade unless FluxStorage=false is set.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
InfoQ: OpenTofu 1.13 Lets Module Authors Reduce Unknown Values at Plan TimepostOpenTofu released version 1.13, adding functions such as convert and assumenotnull that let module authors resolve count and for_each values at plan time when input is unknown. The release adds experimental linting with four built-in warning rules, an opt-in Symbol Libraries experiment, and removes WinRM support from the remote-exec and file provisioners. It also changes base64gzip output bytes, requires macOS 13 or later, and is the last series with official 32-bit builds.platform teamsPlatform teams maintaining OpenTofu modules can plan conditional resources with unknown YAML inputs, but must ensure generated values always match the declared object type or apply will fail. Teams using WinRM provisioners or base64gzip need migration work, and base64gzip changes may trigger unexpected resource updates.InfoQ ↗OpenTofuwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
InfoQ: AGNTCon + MCPCon 2026: Agentic AI Foundation Adds Four Projects as MCP Turns to SecuritypostAt AGNTCon + MCPCon 2026 in San Jose, the Agentic AI Foundation added four projects, bringing its total to ten in its first year. Speakers focused on MCP security and identity, including stateless servers, tool annotations, and agents carrying their own identity. Many figures were stage claims without published data, and some security extensions are still drafts.platform teamsPlatform teams running MCP servers should annotate every tool, keep tool schemas small, and plan for agents that authenticate with their own identity rather than a borrowed user token. The security and identity extensions discussed are still drafts, so no settled controls can be relied on yet.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon ECR now supports replication backfill for existing container imagesannouncementAmazon ECR now supports replication backfill, which replicates existing images in a private registry to configured replication destinations. Previously, replication only applied to images pushed after replication was enabled, so teams had to retag images manually. Backfill jobs can be started with a single API call, up to ten can run concurrently, and per-image progress is visible through new APIs.platform teamsPlatform teams can seed new or existing Regions and disaster recovery destinations with an full image catalog without retagging images. Jobs can be stopped at any time without deleting already replicated images, and the feature is available in all Regions where ECR is offered.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Measuring developer experience on an Amazon EKS developer platformpostThe AWS Containers Blog post explains the DORA metrics (deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time) and how to collect them on an Amazon EKS developer platform. It walks through a demo setup that connects Argo Events, Argo Workflows, Argo CD, Argo Rollouts, Apache DevLake and Grafana. The post cites State of Platform Engineering Report Volume 4 and Enterprise Strategy Group figures on platform measurement and time to market.platform teamsPlatform teams on EKS can use the described Argo and DevLake pipeline to compute DORA metrics from existing deployment, rollout and pipeline events. The post's walkthrough is a demo, and the source text is cut off before the setup steps are complete.AWS Containers Blog ↗Amazon EKSArgo CDArgo RolloutsArgo WorkflowsDORA State of DevOps / AI-assisted development reportHelmwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Tracing failures across Terraform state boundaries with AWS DevOps AgentpostAWS publishes a walkthrough of using AWS DevOps Agent to trace failures across separate Terraform state files. The sample has an infrastructure team tighten a security group egress rule, which breaks an application Lambda's DynamoDB access, and the agent correlates CloudWatch alarms and CloudTrail to point at the networking change. The post also covers provisioning the agent space with the hashicorp/awscc provider and bridging CloudWatch alarms to the agent's HMAC-signed webhook through a Lambda function. The source text is cut off before the walkthrough is complete.platform teamsPlatform teams that split infrastructure into multiple Terraform stacks could use an AI agent to trace cross-stack root causes, but the source shows only a demo. The webhook is console-only and not exposed as a Terraform resource, so it needs manual setup.AWS DevOps Blog ↗AWS DevOps AgentOpenTofuwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Custom APIs just landed in the Dataverse MCP Server, Agents just got smarterannouncementThe Dataverse MCP Server now exposes Custom APIs, so agents can invoke custom business operations hosted in Dataverse regardless of where the agent runs. A Custom API backed by a plug-in runs its steps inside a single Dataverse transaction and rolls back fully if any step fails. The post describes a search, describe, and invoke_api sequence the agent uses to discover and call these APIs from metadata, with a sample case-creation example. Custom Actions are not supported yet.platform teamsPlatform teams can expose multi-step business logic as one atomic, typed operation that agents discover automatically, rather than letting agents chain separate record writes. Teams should note that Custom Actions are not yet supported through the MCP server.Microsoft Power Platform Blog ↗Microsoft Power Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The New Stack: The sandbox wasn’t enough: Why AI agent governance requires runtime observabilitypostThe article uses two incidents, an OpenAI cybersecurity evaluation that reached the public internet and an Anthropic review of 141,006 evaluation runs, to argue that a configured isolation boundary does not show what is reachable at runtime. It proposes four properties for runtime evidence: coverage, correlation, timeliness and auditability. It also describes how agent traces from Langfuse and infrastructure telemetry from ClickStack could share OpenTelemetry trace context.platform teamsPlatform teams running agents should instrument every trust boundary, including network egress, credential use and production writes, and link agent tool calls to infrastructure effects. They should also place synchronous policy gates in front of high-impact actions so a run can be suspended or its credentials revoked before effects become irreversible.The New Stack ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
CNCF: Isolation. Security. Scale.postThe CNCF blog post explains agent sandboxing and describes Agent Substrate, which runs agents as Actors inside Workers (Pods) managed by a control plane, using gVisor for software-level isolation and microVMs for hardware-level isolation. It walks through installing kagent and Agent Substrate with Helm, declaratively creating a Harness and AgentTemplate, and running a sandboxed assistant. The post says an Actor runs only while a session is active.platform teamsA platform team running kagent can provision agent sandboxes as declarative resources and keep agent sessions isolated from the host kernel, with the sandbox runtime chosen per workload. Teams should check the post's setup steps against current kagent and Agent Substrate releases before relying on them, since the post's own install steps are linked out rather than shown.CNCF Blog ↗kagentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Welcome to the MatrixpostThe CloudBees blog says a new matrix section is available in Declarative Pipeline from the Jenkins Experimental Update site. It lets users define a list once and run that list in parallel across multiple configurations. The source text is a truncated teaser, so details such as syntax and release status are not available here.platform teamsTeams running Jenkins can evaluate the matrix section to reduce duplicated pipeline definitions for parallel runs. Because it ships on the Experimental Update site, it should be tested before any production use.CloudBees Blog ↗CloudBeesJenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
CloudBees CI with HA Mode Enabled: Sample cost analysis on AWSpostCloudBees published a blog post titled 'CloudBees CI with HA Mode Enabled: Sample cost analysis on AWS'. The text available to us is a single general statement that infrastructure cost should be weighed against the value it delivers, and that higher performance and resilience increase complexity.platform teamsThe source text gives no figures, configuration details or methodology, so it does not show what an HA CloudBees CI deployment costs on AWS or what a platform team would change. Teams evaluating HA CI on AWS would need the full analysis.CloudBees Blog ↗CloudBeesJenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Pipeline Template Catalogs Enable Pipeline as Code in CloudBees CIpostCloudBees describes Pipeline Template Catalogs, used together with Shared Libraries, as a way to enable Pipeline as Code in CloudBees CI. The post says development teams often have very similar pipelines for common project types. The source excerpt is truncated and gives no further detail on how the feature works.platform teamsPlatform teams running CloudBees CI could use shared pipeline templates to standardize builds across teams, but the excerpt does not describe the mechanics, availability or limits.CloudBees Blog ↗CloudBeesJenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Disaster recovery for CloudBees CI with NetApp Astra ControlpostA CloudBees blog post argues that organizations depend heavily on CI platforms, so outages can cost significant developer productivity. It says an enterprise disaster recovery plan is needed for the CI platform and titles the post as covering CloudBees CI with NetApp Astra Control. The excerpt provided does not describe the specific steps or results.platform teamsPlatform teams running CloudBees CI can use this as a prompt to plan backup and recovery for their CI control plane. The source text here gives no concrete procedure or tooling details to act on.CloudBees Blog ↗CloudBeesJenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Troubleshooting Jenkins Performance: Kubernetes Edition - Part 2postThe CloudBees blog post describes steps for troubleshooting Jenkins performance issues in a Kubernetes setup where no production-ready APM tool is available. This is the second part of a series on the topic. The source text provided is only a short introduction, so the specific steps and findings are not described here.platform teamsPlatform teams running Jenkins on Kubernetes may find the troubleshooting approach useful when they lack APM tooling, but the source text does not specify concrete tools or changes.CloudBees Blog ↗CloudBeesJenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Configuration as Code for Cloudbees CI | CloudBees BlogpostThe CloudBees blog post describes configuration as code support for CloudBees CI. It states that enabling this support for plugins simplifies management and governance of those plugins. The source gives no specific features, steps, or versions.platform teamsPlatform teams running CloudBees CI may be able to manage plugin configuration through code instead of manual setup. The source does not say what changes in practice, so the scope of the change is unclear.CloudBees Blog ↗CloudBeeswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
How to deliver your first change with Cam: a walkthroughpostGearset published a walkthrough of Cam, its AI agent, delivering a sample Salesforce change: a VAT number field with a placeholder validation, a finance Flow, and access across 23 profiles. The steps are assigning a Jira or Azure DevOps ticket, answering Cam's questions, approving a nine-step build plan on a feature branch, reviewing the diff, and raising a pull request that Cam fixes if validation fails. The post also describes using Gearset Observability to hand production Apex and Flow errors to Cam.platform teamsPlatform teams running Salesforce on Gearset pipelines could route backlog and production error fixes to an agent whose output passes the same tests, approvals and security checks as human-written changes. The post does not give measured results, so the reliability of this workflow is untested by the source.Gearset Blog ↗GearsetSalesforce Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
From features to solutionspostThe Octopus Deploy blog post shows how to combine Slack integration, subscriptions, and webhook-triggered runbooks to notify responsible team members when a deployment reaches a manual intervention. The example uses a Terraform provider to create subscriptions across spaces, and a read-only service account with a Generic OIDC account to look up team members and their Slack IDs. The features referenced were added in Octopus 2026.3.platform teamsPlatform teams running Octopus can reduce overlooked manual intervention blocks by routing notifications to Slack and using runbooks and read-only service accounts, managed through Terraform. The approach requires configuring OIDC identities and a self-hosted server URI for CLI login to work.Octopus Deploy Blog ↗Octopus DeployTerraform MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
daily email

One short email each morning: what shipped, what breaks, and a link to each change. Unsubscribe in one click. Privacy.

statuslast 30 days for lines
tools tracked43releases in registry964released in the last 30 days108entries published335breaking change lines18security lines84
change typestwo-column gutter, like git status
  • +addedNew functionality.
  • ~changedExisting behavior changed.
  • -deprecatedStill works, scheduled for removal.
  • -removedDecommissioned, gone in this version.
  • *fixedA defect corrected.
  • !securityA vulnerability closed or a dependency patched for one.
  • !breakingFlag in the first column; the change needs action before upgrading.
filter
categoryallidp & portalsai agents on platformci/cdobservabilitysupply chaincost & governancereports & dx dataenterprise app platforms
showmajor onlyreleasescase studiespostmortemsinclude patches