platformchangelog.dev
43 tools

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

feedbefore 2026-07-28patches hidden unless security or breaking
newest entries
PlatformEngineering.org: New reference architectures for IDPs on AWS, GCP, and Azure: Version 2.0 now availablepostThe PlatformEngineering.org blog announces version 2.0 of cloud-agnostic reference architectures for internal developer platforms on AWS, GCP, and Azure. The source text describes multi-platform support, AI integration, and embedded security as features. It does not include the architecture contents or implementation details.platform teamsPlatform teams evaluating reference architectures for IDPs on the three major clouds may find the updated version relevant, but the source gives no specifics to verify what changed. Teams should review the published architecture directly before planning around it.PlatformEngineering.org Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: The platform scorecard: A practical way to prove value (and what to measure first)postThe article is a practical guide to building a platform scorecard to show the value of a platform engineering team. It proposes four areas to measure: a north star metric, adoption, platform health including DORA metrics and SLOs, and financials.platform teamsPlatform teams evaluating how to justify their work can use the four-area structure as a starting checklist for which metrics to collect first. The source text gives no specific figures or case data, so the guidance is a framework rather than evidence of outcomes.PlatformEngineering.org Blog ↗DORA State of DevOps / AI-assisted development reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: Platform engineering makes a difference. Here's how to prove itpostThe article outlines metrics that platform teams can use to show executives the value of an Internal Developer Platform. It names velocity, AI impact and developer sentiment as the core measures. The source text is a short summary and does not give specific figures or methods.platform teamsPlatform teams that need to justify IDP investment get a checklist of measures to consider. Nothing in the source changes tooling or platform behavior.PlatformEngineering.org Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: Self-service observability: Consistency, cost control, and scale with OpenTelemetrypostA platform team describes moving from having each team set up its own observability to offering self-service observability. They embedded OpenTelemetry into a NestJS Platform SDK and applied a four-pillar policy approach for consistency, cost guardrails and scale across more than 90 internal teams. The article, as published in the source abstract, reports a 4x TPS improvement, but the abstract gives no method or measurement details.platform teamsPlatform teams evaluating SDK-level instrumentation can see one approach to standardizing telemetry and enforcing cost limits without per-team setup. The source gives no detail on the policies or how the TPS figure was measured, so the result is hard to reproduce from this text alone.PlatformEngineering.org Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: Understanding platform engineering's role in staying compliant with the EU’s CRApostThe article discusses how platform engineering can help teams meet the EU Cyber Resilience Act's secure-by-design requirements. It proposes embedding secure-by-default standards, automated SBOM generation, and incident reporting into an internal developer platform. The source text is a short summary and does not cite specific tools, releases, or data.platform teamsPlatform teams evaluating CRA readiness could consider building SBOM generation and incident reporting into their golden paths. The source gives no concrete implementation details or requirements to act on.PlatformEngineering.org Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: The empathy gap: Why your platform needs UX, not just APIspostThe article argues that platform teams relying only on APIs and DORA metrics see low Internal Developer Platform adoption. It recommends treating the platform as a product with attention to user experience to reduce cognitive friction for developers. The source text is a short summary and does not include specific data or case examples.platform teamsPlatform teams evaluating adoption problems may consider investing in UX and product thinking alongside APIs. Nothing concrete changes in tooling or practice from the text itself.PlatformEngineering.org Blog ↗DORA State of DevOps / AI-assisted development reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: New reference architecture for an AI/ML Internal Developer Platform on GCPpostPlatformEngineering.org published a reference architecture for an AI/ML internal developer platform on Google Cloud. The architecture is organized into six planes and is aimed at data-intensive and complex ML workloads. The source text is a short teaser and does not list the planes or specific components.platform teamsPlatform teams evaluating ML platform layouts get a six-plane model to compare against their own design, but the source text does not give the plane definitions or tooling choices. Readers would need the full article to judge fit.PlatformEngineering.org Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: How to set up an Internal Developer Platform: An implementation guidepostThe article is a guide to building an Internal Developer Platform minimum viable product over eight weeks. It describes a four-phase framework for developer self-service, advice on choosing a first team, and tips for driving platform adoption. The source text provided is only a short summary, so the specific steps are not visible here.platform teamsPlatform teams planning a first IDP may find the phased approach and team selection advice useful as a planning reference. No new tooling or capability is introduced, so nothing concrete changes in existing platforms.PlatformEngineering.org Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PlatformEngineering.org: The biggest challenges platform engineering teams are facing in 2026postA PlatformEngineering.org blog post summarizes the State of Platform Engineering Vol 4 report. According to the post, the report finds that cultural and organizational barriers, rather than technical ones, are the biggest obstacle to platform initiatives. The post says developer adoption is the top challenge and covers building an MVP, securing executive buy-in, and measuring ROI.platform teamsPlatform teams planning an internal platform may need to prioritize developer adoption and organizational buy-in alongside technical work. The source text gives no figures or methodology, so the findings cannot be checked from this item alone.PlatformEngineering.org Blog ↗State of Platform Engineering reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-07-213 months ago
OpenTofuv1.12.5patchsecurity*!!
2026-07-144 months ago
Pulumiv3.253.0minor+++***
Kubernetes Dashboard to Headlamp: A Step-by-Step GuidepostThe Kubernetes Blog publishes a step-by-step guide for moving from Kubernetes Dashboard to Headlamp. It covers the differences between the two tools, a pre-migration checklist, desktop and in-cluster installs via Helm, and authentication through kubeconfig or OIDC with RBAC.platform teamsPlatform teams replacing Dashboard can use the guide to choose between desktop and in-cluster Headlamp, plan a parallel rollout, and confirm that Headlamp inherits the same RBAC rules and identities. Teams must also set up OIDC callbacks and ingress headers for shared in-cluster access.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-07-084 months ago
Pulumiv3.251.0minor++++++++++****
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