platformchangelog.dev
43 tools

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

feedbefore 2026-10-08patches hidden unless security or breaking
newest entries
2026-10-0724 days ago
CNCF: Meshery becomes a CNCF Incubating projectannouncementThe CNCF TOC voted to accept Meshery as a CNCF incubating project. The announcement cites a 350% increase in code commits over the year to July 2026, about 7,000 contributors, and general availability of Meshery v1.0. A new Meshery MCP Server gives AI assistants read-only access to the Meshery Registry and cluster state.platform teamsPlatform teams evaluating Meshery gain a CNCF incubation signal and a read-only MCP server for agent access to cluster state. Terraform support for the single model is described as coming soon, so it is not yet available. The growth figures are self-reported by the project and the CNCF blog, not independently verified.CNCF Blog ↗BackstageHelmTektonCortexOpenTofuwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-0625 days ago
GitLab Transcend: Speed you can trust, all the way to productionannouncementGitLab announced more than a dozen features at its Transcend event, including goal-driven agent flows, custom flows, an MCP Server, Artifact Central in beta, Dependency Firewall in early access, and Secrets Manager set to reach GA this month. The vendor says GitLab Orbit context graph reduces agent retries by up to 45x and token use by up to 4.5x during its beta. Credit and usage controls add spend caps and alerts at the subscription, group, and user level.platform teamsPlatform teams evaluating GitLab can plan to govern agent actions and MCP access under existing policy, set AI spend caps, and route packages through Artifact Central and Dependency Firewall. Many capabilities are GA later or in beta or early access, so rollout timing matters.GitLab Blog ↗GitLabJenkinsGitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-0229 days ago
Integrate AWS DevOps Agent with third-party tools using Amazon EventBridgepostAWS published a walkthrough that uses AWS CDK, Amazon EventBridge, AWS Lambda, and DynamoDB to send AWS DevOps Agent investigation events to Jira Cloud. The Lambda function creates a Jira issue on Investigation Created, stores the mapping from task_id to issue key, and appends comments for later state changes. Credentials are kept in AWS Secrets Manager, and the post says the same pattern applies to ServiceNow and PagerDuty.platform teamsA platform team that runs AWS DevOps Agent can follow investigations in its existing ticketing tool by adding an EventBridge rule and a Lambda target, without changing the agent. The destination-specific logic lives in the Lambda code, so swapping tools mainly means rewriting that function.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Closed-loop incident response: connect AWS DevOps Agent to OpenSearchpostThe AWS DevOps Blog describes connecting AWS DevOps Agent to Amazon OpenSearch Service data through an MCP server, so that OpenSearch alerts trigger the agent to query logs and traces and correlate them with CloudTrail and CloudWatch. The post presents three hosting options: self-managed on ECS Fargate behind an NLB with VPC Lattice, Amazon Bedrock AgentCore, and the built-in MCP endpoint on OpenSearch 3.3+. The source text is cut off before the registration and verification steps are complete.platform teamsPlatform teams running OpenSearch alerting could route alerts to an agent that investigates automatically, but they would need to set up a hosted MCP server, a private network connection, and FGAC role mappings that control what the agent can read. The source describes this as a walkthrough and does not report measured results.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
AgentCore Gateway supports private TLS certificates for VPC endpointsannouncementAmazon Bedrock AgentCore Gateway now accepts TLS certificates signed by private certificate authorities on MCP, OpenAPI and HTTP proxy targets. The gateway fetches a PEM-encoded CA certificate from Amazon S3 or AWS Secrets Manager and uses it as the trust anchor for outbound TLS. The feature is available in all Regions where AgentCore Gateway and Amazon VPC Lattice are both available.platform teamsTeams can connect agents through AgentCore Gateway to private endpoints in their VPC without placing an Application Load Balancer in front of them solely for TLS. Teams with internal CAs will need to store the CA certificate in S3 or Secrets Manager and make the targets reachable through VPC Lattice.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-301 month ago
AI-powered EKS migration assessment with Amazon Bedrock AgentCorepostAWS published a walkthrough for building a migration assessment agent with Amazon Bedrock AgentCore and the Strands Agents SDK. The agent reads application source code and container artifacts from platforms such as OpenShift, Azure and on-premises Kubernetes, then produces a readiness score, ranked blockers and a migration plan for Amazon EKS. The source text was cut off before the deployment steps.platform teamsPlatform teams assessing many applications for EKS migration could automate the first-pass readiness review, with the output still needing engineer review. The post describes a reference implementation rather than a shipped product feature.AWS Containers Blog ↗Amazon EKSAWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
What is the Agentic Development Lifecycle and do you need it?postThe author argues that the Agentic Development Lifecycle (ADLC) maps almost stage for stage onto the existing software development lifecycle (SDLC). He says Agentforce agents are deployed as metadata, so existing release and version control practices apply, and that metadata types have changed over the past year, such as Agent Planner bundles becoming Agent Script. He recommends limiting agents to analysis and building while deterministic CI/CD, testing, review and backups handle the rest.platform teamsPlatform teams running Salesforce should keep applying existing release governance, change failure rate and DORA measurement to AI-produced changes, and track Agentforce metadata format changes in release notes. Nothing new is shipped that changes tooling.Gearset Blog ↗GearsetSalesforce PlatformAgentforceDORA State of DevOps / AI-assisted development reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-291 month ago
Accelerating development workflows with Kiro CLI as a Pre-Commit and Git Hook AgentpostAWS DevOps Blog describes using Kiro CLI in non-interactive mode with a KIRO_API_KEY environment variable so it can run inside local Git hooks. The post gives example pre-commit, commit-msg and pre-push hook scripts that send staged diffs or commit messages to the Kiro API for analysis. The source notes that hooks send code diffs to an external API and that the hook is skipped when the key is unset.platform teamsPlatform teams can use this pattern to add AI review to local Git hooks before CI runs, but it sends source diffs to an external API, so data-handling policy review is needed first. The source text is cut off before the pre-push hook and post-merge hook are complete.AWS DevOps Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
GitLab and Claude Code: Fast, compliant AIannouncementGitLab describes running Anthropic's Claude Code as the coding interface inside GitLab Duo Agent Platform, so that generated changes pass through GitLab's merge request gate, scans, approvals and audit trail. The post says that as of August 2026, GitLab Dedicated for Government customers can deploy the AI Gateway in their own single-tenant environment and connect a model provider such as Amazon Bedrock. The post cites LinearB's 2026 benchmark for the finding that agentic AI merge requests take 5.3 times longer for a reviewer to pick up.platform teamsPlatform teams evaluating GitLab for agent-written code can use the merge request gate as a single review and audit point regardless of which coding tool wrote the change. Self-hosted and single-tenant AI Gateway options are the relevant deployment choices for data residency or air-gapped requirements, but the post gives no pricing, availability details beyond the stated date, or independent verification.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-281 month ago
How Property Finder automated incident management with AWS DevOps Agentcase studyProperty Finder describes a pipeline built on AWS DevOps Agent that takes a CloudWatch ECS CPU alarm through root cause analysis, Slack posting, Jira ticket creation, phone escalation via Grafana IRM, and a Draft GitHub PR with a Terraform fix. The post reports a 14-minute end-to-end time for one incident, with investigation taking about 10 minutes. The post is written by AWS and the figures come from a single incident and the company's own account.platform teamsPlatform teams running ECS and Terraform can see a pattern for wiring an AI investigation agent to alerting, ticketing and paging, with a remediation agent restricted to a GitHub MCP server and always opening Draft PRs for human review. The source gives no independent measurements beyond the one incident and a vendor-attributed quote.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSTerraform MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Audit trails for autonomous agents with AWS DevOps AgentpostAWS describes an audit pipeline for AWS DevOps Agent built on Amazon EventBridge, AWS Lambda, Amazon S3, Glue and Athena. The pipeline archives the agent's investigation journals, polls recommendations on a schedule, and correlates recommended fixes with resource changes recorded in AWS Config and CloudTrail. The post says the journal is immutable, and it points to sample code in a repository.platform teamsPlatform teams running DevOps Agent can capture per-investigation journals, recommendation versions, and lifecycle events into their own archive, and scope IAM access to that archive. Recommendations have no event, so they must be polled, and CloudTrail does not capture the agent's read queries.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-221 month ago
How GitLab reduced code-per-agentic-flow ratio by 45%postGitLab describes Flow Registry, a declarative YAML framework that compiles into LangGraph flows for its Duo Agent Platform, built from reusable components, routers and a shared state structure. GitLab says using it cut its own code-per-agentic-flow by 45%. The article is partial in the feed and does not include independent measurements.platform teamsPlatform teams building or evaluating agent workflows on GitLab could define agents and routing in YAML instead of hand-written graphs, which may reduce maintenance work. The 45% figure is GitLab's own internal metric and is not independently verified.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-171 month ago
See who spent your AI credits and set fair caps per teamannouncementGitLab 19.4 adds per-user management of GitLab Credits, letting admins set a flat per-user cap, add overrides for individuals, and see spend. Admins can also export per-event usage data covering up to 31 days, delivered by email as a summary, per-event file and manifest. Usage syncs periodically, so spend already in flight can cross a cap before enforcement catches up.platform teamsPlatform teams can allocate AI agent budgets per team and per developer, map namespace IDs to cost centers for showback, and pull session-level records for investigating spikes. Teams should account for the periodic sync delay when setting caps.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
New MCP tools help platform teams scale automationpostGitLab 19.4 substantially expands the GitLab MCP server tool set with CI/CD, merge request, work item, vulnerability and project tools, currently in beta. Read-only actions run without a human in the loop by default, while writing, merging or deleting actions wait for a reviewer the team chose. A new Merge request created trigger lets a flow or external agent run when an MR is opened once the diff is generated.platform teamsPlatform teams can let agents retry pipelines, read job logs, open and update MRs, and merge when checks pass, with approval gates set per action. Vulnerability tools require the Ultimate tier, and the MR created trigger requires Premium or Ultimate with GitLab Duo Agent Platform enabled.GitLab Blog ↗GitLabeditorCorrection 2026-10-20: this was listed as a GitLab 19.4 release by mistake. It is GitLab Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Investigate DMS migration issues with AWS DevOps AgentpostAWS published a guide on extending AWS DevOps Agent with a sample MCP server that provides read-only, DMS-specific tools and 46 runbooks for investigating database migration issues. The server is deployed on AWS Lambda behind an IAM-authenticated function URL and registered with a DevOps Agent Space. The post describes five investigation scenarios run against a test migration from RDS MySQL to Aurora PostgreSQL.platform teamsPlatform teams running DMS migrations can evaluate a read-only MCP pattern for giving an agent migration-specific context, with tools restricted to Describe, Get, List, Lookup and TestConnection calls. Timing claims in the post come from the authors' own test runs and are not benchmarked.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-031 month ago
Automating the Experimentation Lifecycle with Kiro, AWS DevOps Agent, and LaunchDarklypostAWS describes a reference architecture where AWS DevOps Agent runs a scheduled custom agent that plans feature-flagged experiments, uses Kiro CLI in a custom MCP server to write code and open pull requests, and deploys through GitHub Actions and AWS Amplify. LaunchDarkly runs the experiments and Guarded Releases, which roll back flag state when error or latency guardrails are breached. The post says the architecture is a reference implementation and that a more turnkey version is planned.platform teamsA platform team evaluating agent-driven delivery would need to scope MCP tools, restrict repos, branches and allowed tools, and manage credentials and state outside the container. The post notes that the scoping lives in server code rather than prompts, and that MCP tool allowlists are recommended for production.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSGitHub ActionsKubernetes MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-021 month ago
Automate planned lifecycle upgrades with AWS DevOps Agent and KiropostAWS describes a pattern in which AWS Health Planned Lifecycle Events for Amazon EKS trigger EventBridge and a Lambda function that starts AWS DevOps Agent to investigate the upgrade and produce a CDK change spec. The spec is validated in a GitHub Actions workflow, then Kiro CLI in headless mode edits a single stack file and a pull request is opened for human review. The post also describes an automated failure path that investigates failed deployments and opens a fix pull request, with one retry attempt.platform teamsPlatform teams running EKS on AWS could adapt this event-driven pattern to handle managed service end-of-support deadlines, with human review kept at the pull request. The source is a vendor blog post with sample code and does not report measured results.AWS DevOps Blog ↗Amazon EKSAWS DevOps AgentGitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-312 months ago
Optimize EKS operations with agents: Reduce MTTR with AWS DevOps Agent and a Kubernetes OperatorpostAWS describes a Kubernetes Operator that watches EKS pods, collects logs, events, node-level data and manifests when a failure occurs, and sends that context to AWS DevOps Agent through a generic webhook. The post says the Operator stores evidence in S3 or CloudWatch Logs before pods are rescheduled or deleted. Setup requires an Agent Space, an IAM role with Pod Identity, and building the Operator image from source because no prebuilt image is provided.platform teamsPlatform teams running EKS can evaluate automated incident evidence capture and agent-driven investigation, but must set up IAM, Systems Manager registration on nodes, and build and host their own image. Node-level collection is unavailable on Fargate.AWS DevOps Blog ↗Amazon EKSAWS DevOps AgentK8sGPTwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-282 months ago
Build your own continuous modernization pipeline with AWS Transform custompostAWS describes a do-it-yourself continuous modernization pipeline that runs AWS Transform custom as a step in GitHub Actions. The walkthrough uses a sample Spring Boot application and covers Dependabot alert remediation and auto-documentation on pull requests. The post provides shell scripts that call the atx CLI in headless mode with up to three retries.platform teamsPlatform teams could wire AI code transformations into existing CI/CD pipelines, but the example runs with the --trust-all-tools flag, which removes interactive confirmation and needs review against security policy before production use. The source text is cut off before the remaining practices are covered.AWS DevOps Blog ↗GitHub ActionsAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-262 months ago
Terraform MCP Serverv1.3.0minor
AI-driven software delivery with Kiro, AWS DevOps Agent and Bluebox by DynatracepostAWS and Dynatrace describe a workflow in which Kiro retrieves runtime topology and traffic data from Bluebox via CLI before generating a pull request, and AWS DevOps Agent investigates a simulated traffic-spike incident. The agent's findings and mitigation plan are filed as a GitHub issue, and Kiro then opens a remediation pull request that a human reviews and merges. The post uses a travel-booking example, and the reported results come from that example rather than measured data.platform teamsPlatform teams evaluating AI incident agents can see a pattern where investigation output is written to GitHub issues and fixes flow through normal PR review and CI/CD. The post does not give benchmarks, adoption figures, or availability details for the release management capability, which is in Preview.AWS DevOps Blog ↗AWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-212 months ago
A virtual teammate vs a copilot: what’s the difference?postGearset argues that AI coding tools differ between copilots, which assist a developer step by step, and virtual teammates, which take a ticket and return a review-ready pull request. The post lists questions for evaluating tools, including whether they hold org context, are shared across a team, adapt to feedback, and work within existing governance. It closes by promoting the Gearset Agent.platform teamsPlatform teams evaluating agents for Salesforce delivery should check whether an agent runs through the same tests, security checks and review gates as human changes, and whether it has org context. The post itself gives no measured results and no concrete product change.Gearset Blog ↗GearsetSalesforce Platformwritten 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 days106entries published336breaking 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