platformchangelog.dev
43 tools

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

feedbefore 2026-09-29patches hidden unless security or breaking
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 ↗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
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 ↗GearsetSalesforce Platformwritten 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
The operations gap between deploying an application and running it foreverannouncementAWS announced Elastic Beanstalk Cluster Mode, which accepts an application as source code, a Dockerfile, or a pre-built container image from Amazon ECR and runs it on Amazon EKS. The source says AWS handles deployment, scaling, patching, monitoring and upgrades for the life of the application, with automatic rollback when health checks fail. The service is available in all commercial AWS Regions where Elastic Beanstalk is offered, with no additional Elastic Beanstalk service fee beyond underlying resources.platform teamsPlatform teams evaluating managed hosting for a mixed portfolio could consolidate containerized and legacy apps under one operational model with AWS-run environments. The post is vendor-written and gives no performance or cost figures, so the cost and reliability benefits it describes are unverified.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Implement per-pod image pull permissions with ECR repository policies on Amazon EKSpostAWS describes a walkthrough for scoping Amazon ECR image pull permissions to individual Kubernetes pods on Amazon EKS. The approach uses KEP 4412 per-pod credential support in kubelet, with the ecr-credential-provider assuming a team IAM role through a service account annotation and ECR repository policies enforcing access. The post states the feature needs Kubernetes 1.34 or later, with full support on EKS v1.35 or later.platform teamsPlatform teams on multi-tenant EKS can give each namespace its own ECR pull role instead of relying on the shared node role, but they must create a ClusterRole and ClusterRoleBinding for the sts.amazonaws.com audience before nodes join, and must update node credential provider configuration. Pods without the annotation fall back to the node role.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Salesforce DevOps tools: why the highest-performing teams don’t stop at deploymentreportGearset publishes an analysis based on its State of Salesforce DevOps 2026 report, arguing that teams covering more of the six DevOps lifecycle stages report fewer bugs, less rework and less downtime. The post says high adopters are nearly twice as likely to keep error rates below 5%, spend 56% fewer hours on rework and lose 62% less time to downtime. It also reports that observe and operate are the least covered stages, and that 43% of teams apply no extra review to AI-generated changes.platform teamsPlatform teams running Salesforce can use the stage-by-stage coverage model to audit their own toolchain, particularly the observe and operate stages. The post is written by a vendor selling a competing DevOps product and the survey methodology is not described in the source text.Gearset Blog ↗GearsetSalesforce Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
How to design GitLab for enterprise scalepostGitLab's blog publishes a guide on designing GitLab for enterprise scale, covering choosing between GitLab.com, GitLab Dedicated and Self-Managed, runner scope and executor choice, and availability targets. It also covers measuring queued duration, job duration and runner utilization to find pipeline bottlenecks. The excerpt provided is cut off before the Kubernetes and checklist sections.platform teamsPlatform teams evaluating GitLab at scale get a checklist of sizing inputs, including runner scope, executor choice and RTO/RPO targets to define before rollout. Nothing in the excerpt changes GitLab product behavior.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-211 month ago
Kubernetes v1.37: Tracking When a PersistentVolumeClaim Was Last Used (Beta)postKubernetes v1.37 promotes the PersistentVolumeClaimUnusedSinceTime feature gate to Beta and enables it by default. The PVC protection controller now sets an Unused condition on each PVC, with status True and reason NoPodsUsingPVC when no non-terminated pod references it. The condition's lastTransitionTime records when the PVC became idle.platform teamsPlatform teams can list idle PVCs with kubectl and jq instead of cross-referencing pods and volumes with custom scripts, which helps find orphaned storage that drives cloud costs. The feature is on by default in v1.37, and the project intends to reach GA in a later release.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Amazon EKS v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Extend Server Logic with Power Automate Cloud Flows in Power PagesannouncementMicrosoft announced support for invoking Power Automate cloud flows from Server Logic in Power Pages. The feature lets website server-side logic call existing cloud flows. Microsoft says this gives access to more than 1,400 connectors in Power Automate.platform teamsPlatform teams that govern Power Pages can reuse existing cloud flows and their connector governance instead of building separate integrations. The post gives no details on permissions, deployment, or limits, so teams should check the documentation before relying on it.Microsoft Power Platform Blog ↗Microsoft Power Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-171 month ago
Rate limits on GitLab.com are changingannouncementGitLab.com is changing its API rate limits so they depend on subscription tier. Free accounts and unauthenticated requests are limited starting October 19, 2026, with preview windows on October 7 and October 14, and Premium and Ultimate limits change in January 2027. Unauthenticated requests are capped at 60 per hour per IP address, and exceeding a limit returns HTTP 429 with a Retry-After header.platform teamsPlatform teams whose pipelines, bots, or agents call the GitLab.com API without credentials will hit the 60 requests per hour anonymous cap and should move calls to personal access, OAuth, or job tokens. Teams should check RateLimit-Remaining headers against their plan's published limits before the October 19 change, and self-managed and Dedicated instances are not affected.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
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