platformchangelog.dev
43 tools

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

feedbefore 2026-09-29all releases, patches included
newest entries
2026-09-281 month ago
What's new in Git 2.56.0?postGit 2.56.0 adds a drop subcommand to git-history that removes a commit and rebases its descendants onto its parent, and new --forked and --delete-merged options to git-branch for finding and deleting branches merged into an upstream. It also lets git-refs create, delete, update and rename refs, and adds a remote-object-info command to git-cat-file and a --drop-filtered option to git-repack for partial clones. The post also outlines a plan where Git 2.98 follows 2.56, with 2.99 and 3.0 shipping together in spring 2027 and 3.0 making SHA-256 the default object format, reftable the default ref storage, and Rust mandatory.platform teamsPlatform teams running Git-based pipelines get new commands for cleaning up merged branches and reclaiming disk space in partial clones, but nothing in this release changes existing CI behavior. The Git 3.0 plan (SHA-256 default, reftable default, Rust required) is a future breaking change that teams should check their forges, tooling and build toolchains against, and the 2.99 LTS release is aimed at platforms without a Rust toolchain.GitLab Blog ↗GitLabeditorCorrection 2026-10-20: this was listed as a GitLab 2.56.0 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
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 ↗Terraform MCP ServerAmazon EKSAWS DevOps Agentwritten 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 ↗Amazon EKSAWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Fix pod distribution drift in Amazon EKS with the Kubernetes deschedulerpostThe AWS Containers Blog describes how pods spread across three Availability Zones with soft topology spread constraints can drift into two zones after a node-availability gap and stay skewed. In a measured run on Amazon EKS with a 1,000-pod fleet, the post reports the skew persisted for over 16 hours after capacity returned. It then shows the Kubernetes descheduler's RemovePodsViolatingTopologySpreadConstraint plugin, configured to act on ScheduleAnyway constraints, restoring balance in about 183 evictions with PDB limits applied.platform teamsPlatform teams running soft topology spread on EKS should expect silent zone drift after node disruptions and can use the descheduler with ScheduleAnyway enabled, topologyBalanceNodeFit, and PDBs to correct it. Teams needing strict zone balance should consider DoNotSchedule and alert on pending pods instead.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Pulumiv3.265.0minor++****************Pulumi v3.265.0 adds a pulumi logout --all --delete-credentials-key option, Authenticode signing for Windows CLI and language host binaries, and a PCL error for literals that do not match a schema constant or enum. It also fixes 21 items, mostly in the PCL type checker and interpreter, code generation for Python, Node.js and Go SDKs, and engine handling of unknown outputs when a dependency fails during a --continue-on-error update.platform teamsTeams using Pulumi with --continue-on-error can now rely on Unknown=true being reported for skipped Read and Import steps, so SDK consumers no longer treat empty outputs as real values. Windows CLI binaries are now signed, which may matter for install policies.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
One Amazon EKS, many edges: How to choose your edge container strategy on AWSpostAWS published a guide on running Amazon EKS as one standard across many edge locations, with the deployment model chosen per site. The post proposes a two-step method: first check whether a site has a reliable connection to an AWS Region, then choose between EKS Hybrid Nodes, EKS on Outposts, or EKS Anywhere based on existing infrastructure. It also lists pricing for each model and notes that Windows workloads are supported only on Outposts.platform teamsPlatform teams running many edge sites can use the connectivity-gated decision flow to standardize on one Kubernetes API and pipeline while varying the deployment model per site. Teams should check the pricing table and the Windows and Linux-only constraints before choosing a model.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
How to deploy data kits in Salesforce Data 360postGearset's blog explains that Salesforce Data 360 data kits can deploy without their contained components, because retrieving a DataPackageKitDefinition returns only the list of contents. It describes a Gearset workflow that builds the package with dependencies, validates the kit, and adds a post-deployment activation step that runs Salesforce's separate publish process. The post also notes that Direct Deploy is available for some Data 360 components outside of kits, but not in automated CI jobs.platform teamsPlatform teams deploying Data 360 config through pipelines need a publish or activation step per environment, since a deployment can report success while data streams stay inert. Teams using a different tool would need to handle component retrieval, dependency ordering and activation themselves.Gearset Blog ↗Salesforce PlatformGearsetwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Salesforce CLI2.151.7minor++****Salesforce CLI 2.151.7 shows deploy notifications in both JSON and human-readable table output, and adds Refresh Token Rotation support so simultaneous commands no longer fail with a token-processing error. It also fixes plugin install, uninstall and update failures on Windows paths with spaces, false-positive diffs for Aura CSS edits, handling of AiAgentDefinitionVersion names containing #, and ENOENT errors on standalone Unix tarball installs.platform teamsPipelines that run project deploy start now see deploy-level notifications such as ApexApiVersionRetirement in the table output, and connected apps with RTR enabled work without extra flags. Teams using AI agent metadata can deploy and retrieve versioned agent definitions without the earlier delimiter errors.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Building a single-pane NOC dashboard for Amazon EKS with Amazon CloudWatchpostAWS Containers Blog describes a sample NOC dashboard for Amazon EKS built on Amazon CloudWatch, combining PromQL chart widgets with CloudWatch metric widgets. The sample comprises a 35-widget NOC and three drilldown dashboards for the retail store sample application, with a probe that validates each query against live telemetry before deployment. The post was validated with the Amazon CloudWatch Observability EKS add-on v6.4.0-eksbuild.1.platform teamsPlatform teams running EKS can reuse the pattern and the validation probe to check that dashboard queries resolve, and can add freshness alarms to separate missing telemetry from healthy zero counts. Auto Mode scale-in can produce blank widgets, so teams need the freshness alarms to tell expected scale-in from pipeline failure.AWS Containers Blog ↗Amazon EKSwritten 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 days105entries 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