platformchangelog.dev
43 tools

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

feedbefore 2026-10-05all releases, patches included
newest entries
2026-10-0229 days ago
Kargov1.12.1patch
Amazon ECS adds Amazon VPC Lattice support for blue/green, linear, and canary deploymentsannouncementAmazon ECS now offers built-in blue/green, linear, and canary deployment strategies for ECS services that use Amazon VPC Lattice for traffic routing. Teams can run test traffic before production shifts, attach lifecycle hooks such as Lambda and pause hooks, and use CloudWatch alarms and the ECS deployment circuit breaker to roll back automatically. The feature works for new and existing services in all Regions where VPC Lattice is available, and can be configured in the console, CLI, SDKs, or IaC tools.platform teamsPlatform teams running ECS with VPC Lattice can move progressive delivery into the ECS service configuration instead of building their own traffic shifting. Rollback depends on the CloudWatch alarms and circuit breaker that teams configure.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon EKS and Amazon EKS Distro now support Kubernetes version 1.37announcementAWS announced that Amazon EKS and Amazon EKS Distro now support Kubernetes version 1.37 in all EKS regions, including the GovCloud (US) Regions. Clusters can be created on 1.37 or upgraded through the EKS console, eksctl, or infrastructure-as-code tools. The source highlights Metrics API promotion to GA, DRA device taints and tolerations reaching GA, and Horizontal Pod Autoscaler scale-to-zero entering beta and enabled by default.platform teamsPlatform teams running EKS can plan upgrades to 1.37 and can use EKS cluster insights to check for issues before upgrading. Autoscalers with minReplicas: 0 using object or external metrics will scale idle workloads to zero by default, which teams should account for in their scaling policies.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
Actions Runner Controller0.15.0minor++++~----*********gha-runner-scale-set-0.15.0Actions Runner Controller released gha-runner-scale-set 0.15.0 with 79 changes, including removal of legacy e2e tests and several unused APIs and printer columns. New flags add default and per-controller max-concurrent-reconciles settings, and terminationGracePeriodSeconds is now configurable. The release also includes many fixes to listener pod patching, RBAC permissions, and scale-set drift detection.platform teamsPlatform teams running self-hosted GitHub Actions runners on Kubernetes should review the removed status-field printer columns and the new reconcile concurrency and termination grace period settings before upgrading. Runner status is now reported through metrics rather than status fields, so dashboards or scripts that read those fields will need updating.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Implementing feature flags in container environments with AWS AppConfigpostAWS Containers Blog published a walkthrough of using AWS AppConfig with its agent running as a sidecar in Amazon ECS tasks and Amazon EKS pods to serve feature flags. The application reads flags from a localhost HTTP endpoint, and the agent handles polling and caching. The post includes sample manifests, a task definition, and a discount flag example.platform teamsPlatform teams can change feature flag values at runtime without rebuilding or redeploying containers, using the same sidecar pattern on both ECS and EKS. Teams should still plan for service-level API throttling at high agent counts, which the post notes.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon EKS Auto Mode now supports advanced compute configurationannouncementAmazon EKS Auto Mode now lets users set kubelet settings, Linux kernel sysctls, and hugepages through a new advancedCompute field in the NodeClass resource. The settings are applied declaratively via the Kubernetes API, validated, applied at node boot, and kept through scaling and upgrades. The feature is available in all AWS Regions where EKS Auto Mode is offered.platform teamsPlatform teams can run workloads that need node tuning, such as user namespaces for rootless builds, eviction thresholds, and hugepages, without maintaining EC2 launch templates, custom AMIs, or privileged DaemonSets. Teams running EKS Auto Mode should evaluate whether this replaces their existing node customization.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
The Future of Platform Engineering reportreportOctopus Deploy published the 2026 Future of Platform Engineering report, based on primary survey data from 379 technical platform practitioners and a review of current literature. The report finds that automation and efficiency are the main reasons organizations adopt platforms, and that lack of clear strategy is a more common obstacle than technical complexity. It also reports that teams with mandatory adoption achieved most of their goals more often (62.2%) than teams with optional adoption (about 27.5%).platform teamsPlatform teams evaluating adoption models may weigh the reported link between mandatory adoption, leadership direction and goal delivery when deciding how to position a platform. The source gives no methodology detail beyond the sample size, so the figures are best treated as directional.Octopus Deploy Blog ↗Octopus DeployState of Platform Engineering reportDORA State of DevOps / AI-assisted development reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-301 month ago
Kargov1.12.0minorbreaking++++++++++~~~~****Kargo v1.12.0 removes the Connect-based gRPC API, the createTargetBranch option on git-open-pr, and the author block on git-commit. It changes the git-push default integration policy to RebaseOrMerge and removes the legacy Secret namespace chart values, so upgrades that still set them will fail. The release also adds a tar step, an oci-push srcPath option, cross-account ECR pulls, and per-request actor attribution in API logs.platform teamsPlatform teams upgrading Kargo must check integrations for the removed gRPC API, remove deprecated step fields from promotion tasks, and confirm required Secrets exist in the system and shared resources namespaces before upgrading. Teams relying on rebase-only pushes should set pushIntegrationPolicy to AlwaysRebase in Helm values to keep the old behavior.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Salesforce CLI2.152.14minorsecurity+~***!Salesforce CLI 2.152.14 adds --debug-level and --category-level flags to the apex run command for controlling anonymous Apex debug logs, and the two flags are mutually exclusive. It removes a Hyperforce/JWT gate that blocked sf org create user on Hyperforce orgs when the Dev Hub used JWT authentication. The release also fixes sf org open exiting before the browser launched, a broken sf-trust bin path in @salesforce/plugin-trust, and adds support for the ReferralIntakeConfiguration metadata type in DX projects. A security fix bumps the npm version pinned in npm-shrinkwrap.json to pull in a patched tar.platform teamsTeams running anonymous Apex from the CLI can set debug log levels per predefined level or per category. Teams that run user creation on Hyperforce orgs with JWT Dev Hubs can now use that command, and the npm install failure from the broken bin path is resolved.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Running production experiments with AWS AppConfig experimentationpostAWS describes AWS AppConfig experimentation, which adds A/B testing on top of AWS AppConfig feature flags so a change can be exposed to a controlled slice of production traffic. The AWS AppConfig Agent assigns each participant to a control or treatment, logs each assignment to stderr for shipping to CloudWatch Logs and Amazon S3, and leaves metric analysis to the customer's existing data warehouse. The post walks through a frontend Add to cart button experiment and a backend cache TTL experiment on Amazon ECS.platform teamsPlatform teams can run production A/B tests through existing AppConfig and Agent setups, but they must provision assignment logging, a warehouse for analysis, and CloudWatch alarms that stop runs. Entity IDs are logged verbatim, so PII must be hashed or pseudonymized.AWS DevOps Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
How athenahealth modernized healthcare workloads with Amazon EKS Hybrid Nodescase studyathenahealth moved its Clinicals Macro Service from AWS Outposts to Amazon EKS Hybrid Nodes, keeping on-premises worker nodes in one EKS cluster with a control plane in an AWS Region. The post reports about 50 percent lower HTTP response times, about 50 percent projected hardware cost savings, and CPU use below 10 percent across an eight-node fleet, and says the company passed a HITRUST audit. These figures are the authors' own account of the migration and were not independently verified.platform teamsA platform team that must keep latency-sensitive or data-resident workloads on premises can run them under the same EKS control plane, APIs and tooling as cloud nodes, instead of operating a second control plane. The team still owns the hardware, network, node OS and storage, and needs Direct Connect or VPN connectivity and a separate nodeadm upgrade path for hybrid nodes.AWS Containers Blog ↗Amazon EKSCrossplaneFluxKarpenterwritten 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
Terraform Provider for SAP BTP1.27.0minor+****SAP released version 1.27.0 of the Terraform Provider for SAP BTP. The release notes list one added action, action_update_global_account, and four fixes covering function label extraction for legacy labels, failing early when an amount is set on non-quota entitlement plans, drift resolution for role collection assignments with custom IAS origins, and an auto_create_shadow_users option in the globalaccount trust configuration.platform teamsPlatform teams managing SAP BTP through Terraform get a new action for updating global accounts and fixes that reduce configuration drift for role collections and trust settings. Teams using entitlement plans should note that amount on non-quota plans now fails at plan time instead of being silently accepted.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
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