platformchangelog.dev
43 tools

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

feedsince 2026-10-20patches hidden unless security or breaking
2026-10-292 days ago
Tektonv1.18.0minor+****Pipeline release v1.18.0 "Ukrainian Levkoy Ultron LTS"Tekton Pipelines v1.18.0 was released. The release adds a continueAndFail option on step.onError. Fixes include making controller-managed labels immutable via a webhook, fixing truncation of large Tekton bundles resolved from OCI images, fixing early PVC cleanup for pipelines-in-pipelines child pipelines, and bumping the plumbing ko image to Go 1.27.3.platform teamsTeams running Tekton can use continueAndFail to let a pipeline keep going after a step error, which changes failure handling in existing pipelines. The label immutability webhook and PVC cleanup fix affect controller behavior, so teams should review those when upgrading.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
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
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
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
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
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
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
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
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
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
2026-10-247 days ago
The New Stack: Building an agentic software factory? Start with the sensor.postThe article argues that agentic software factories are limited by their verification step, which it calls the sensor, rather than by coding agents. It defines three sensor properties (latency, fidelity, bandwidth) and suggests tracking time to signal, escape rate and concurrent verification capacity. The article is written by a team that sells a product for per-change realistic environments and presents that approach as the solution.platform teamsPlatform teams evaluating agent-driven pipelines can use the proposed metrics to find which verification property is weakest before raising agent autonomy. The article does not describe a specific tool change, and its recommended per-change environment approach comes from the vendor's own view.The New Stack ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PHP2Shell: GitLab helps find and remediate critical PHP flawspostPHP fixed two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619 (PHP2Shell), on October 21, 2026, in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The flaws are in the PHP engine, so framework or application changes do not mitigate them, and any web server running PHP is affected. GitLab says its own products are not affected and describes how to use container scanning and code search to find PHP runtimes in projects.platform teamsPlatform teams need to upgrade PHP runtimes in hosts and container images, rebuild images with docker build --pull, and check for PHP installed from source, which container scanning cannot detect. Runtime inventory is needed alongside repository scans to find PHP workloads outside GitLab projects.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Meta API endpoints updated for Actions blob storageannouncementGitHub added new blob storage endpoints for GitHub Actions on github.com to its meta API, as part of work to improve capacity and reliability. Organizations that restrict outbound traffic with a network allowlist are asked to permit two new host ranges: productionresultssa30 through productionresultssa49, and productionresultssa100 through productionresultssa199, under blob.core.windows.net. Wildcard allowlists for productionresultssa*.blob.core.windows.net need no change.platform teamsPlatform teams whose runners sit behind individual-host egress allowlists must add the new hosts or risk interruptions to job summaries and logs. The current endpoint list can be retrieved from the REST meta API.GitHub Changelog ↗GitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
AWS CloudFormation now simplifies stack update rollback operationsannouncementAWS CloudFormation added a force rollback option to continue a stalled update rollback in a single operation. The option works across the AWS CLI, SDKs, AWS CDK and AI agents. Resources that still need attention, such as those changed outside CloudFormation, are recorded for review before the next deployment.platform teamsPlatform teams running CloudFormation can recover failed stack updates without listing and retrying each affected resource one by one. They should review drift-aware change sets and recorded resources before the next deployment, since force rollback does not resolve out-of-band changes.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-2110 days ago
CNCF: Distributed tracing for CI pipelines without touching a single workflow filepostThe post describes using the OpenTelemetry Collector's githubreceiver, behind a single org-level GitHub webhook, to turn workflow_run and workflow_job events into OTLP traces. A workflow becomes a parent span, with jobs and steps as nested child spans, so no workflow files need changing. The receiver is a contrib component at alpha stability, and the author advises pinning the collector version.platform teamsA platform team can get org-wide CI traces by pointing one org webhook at a collector, and new repos are covered automatically. The team must provide a publicly reachable endpoint, restrict it to GitHub's webhook ranges, have org admin access, and pin an alpha-stage collector version.CNCF Blog ↗GitHub ActionsActions Runner Controllerwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Limit agent permissions and spend in AWS Transform custompostThe AWS DevOps Blog describes three configuration controls for running the AWS Transform custom agent on fleets of repositories: a trust settings file that auto-approves some tool calls and shell commands, an IAM execution identity scoped to approved transformations, and an agent-minute cap plus an AWS Budgets alert on spend. The post walks through a sample Java 8 to Java 17 upgrade run using AWS Transform CLI 3.10.0, reporting 43 tool calls and that the trust allowlist reduced approval prompts from 23 to zero on a clean clone.platform teamsPlatform teams running agent-driven upgrades from pipelines can manage tool trust, identity scope and spend as configuration rather than new infrastructure. The post's own measurements are from one sample repository and one CLI version, so counts will differ on other estates.AWS DevOps Blog ↗AWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Bulk migrate branch protections to rulesets for a repositorypostGitHub now lets repository admins convert all classic branch protection rules in a repository to rulesets in one action, extending the earlier single-rule conversion. The Review import dialog previews the rulesets to be created, flags rules already covered by an existing ruleset, and shows where one rule expands into multiple rulesets. After creation, the user chooses whether to keep or delete the original branch protection rules.platform teamsPlatform teams that manage branch protection on many repositories can migrate in bulk instead of one rule at a time, choosing enforcement status (Active, Evaluate, or Disabled) before committing. Teams should review the generated rulesets before deleting the originals, since one classic rule can map to several rulesets.GitHub Changelog ↗GitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
InfoQ: GitHub Actions Runner Controller 0.15.0 Targets Reliability at ScalepostGitHub released Actions Runner Controller 0.15.0, which the source describes as adding reliability, scalability and observability improvements for organisations running self-hosted GitHub Actions runners on Kubernetes. The source text is a short excerpt and does not list specific changes.platform teamsPlatform teams running self-hosted GitHub Actions runners on Kubernetes may get better reliability and visibility at scale, but the excerpt gives no specifics on what changed, so the changelog should be checked before upgrading.InfoQ ↗GitHub ActionseditorCorrection 2026-10-20: this was listed as a GitHub Actions 0.15.0 release by mistake. It is InfoQ coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Salesforce teams succeeding with AI have strong DevOps fundamentalsreportGearset's blog summarizes The State of Salesforce DevOps 2026 survey, which reports that 84% of surveyed teams use AI to build Salesforce changes but only 40% are confident in the accuracy and security of AI-generated code. The post says teams with every DevOps lifecycle stage covered report higher confidence and fewer production bugs than teams with gaps. The article then promotes Gearset's agent and pipeline product as a way to combine trusted AI changes with a DevOps pipeline.platform teamsPlatform teams running Salesforce delivery can use the survey's stage-by-stage findings to prioritize version control, automated validation, backups and post-release observability before expanding AI-generated changes or Agentforce agents. The survey methodology and sample size are not given in the source text, and the report is vendor-commissioned.Gearset Blog ↗GearsetSalesforce PlatformAgentforceGitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Redesign how your team ships software with AI agentsannouncementGitLab announced the AI-Native Engineering Playbook, a guide to redesigning software delivery so people and AI agents each handle the work they suit best. The playbook proposes a four-stage autonomy ladder in which each step up must be backed by evidence, and a layered verification approach for code review at agent volume. GitLab's AI Accountability Report, based on an April 2026 survey of 1,528 DevSecOps professionals, is cited, with 79% saying individual productivity improved but overall delivery did not accelerate at the same pace.platform teamsPlatform teams can use the playbook's layered checks as a model: move formatting, type and dependency policy checks closer to authoring, keep change sets small, and record agentic review decisions so they can be inspected later. The post does not describe any new platform feature or tooling change.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
AI Governance: One view of agent activityannouncementGitLab has released the AI Governance Dashboard in beta, which shows activity from GitLab Duo Agent Platform agents and externally connected agents such as Claude Code, Cursor, and Codex in one view for a top-level group. Each agent action is recorded as an audit event with the prompt, model, tools, MCP servers, and project, and sessions can be downloaded as immutable evidence or streamed to a SIEM. Setup requires enabling AI audit event storage, which is off by default, and running glab govern setup on developer machines.platform teamsPlatform and security teams on GitLab Premium or Ultimate can get audit trails of agent tool calls and MCP server use, but must turn on AI audit event storage and hold the Owner role or a custom role with read_agent_artifacts. External agent capture depends on glab 1.122.0 or later on macOS or Linux.GitLab Blog ↗GitLabwritten 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