platformchangelog.dev
43 tools

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

feedbefore 2026-05-17all releases, patches included
newest entries
2026-05-146 months ago
Kubernetes v1.36: Deprecation and removal of Service ExternalIPsannouncementKubernetes 1.36 formally deprecates the .spec.externalIPs field on Service, which the project says enables security exploits when users are not fully trusted (CVE-2020-8554). Kubernetes now emits warnings when the field is used. The project plans to disable support in kube-proxy at v1.40 at the earliest, with an opt-back-in, and fully at v1.43 at the earliest.platform teamsPlatform teams should check whether any Services set externalIPs and migrate to a LoadBalancer controller such as MetalLB, or to Gateway API, where administrators control IP assignment. Enabling the DenyServiceExternalIPs admission controller is recommended as a precaution against new uses.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-05-016 months ago
Kubernetes v1.36: Pod-Level Resource Managers (Alpha)postKubernetes v1.36 adds Pod-Level Resource Managers as an alpha feature, extending the kubelet's Topology, CPU, and Memory Managers to use pod-level resource specifications. Exclusive NUMA-aligned resources can be granted to specific containers while sidecars share a pod-level pool, under feature gates PodLevelResourceManagers and PodLevelResources. New kubelet metrics track allocations, errors, and container assignment types.platform teamsPlatform teams running latency-sensitive workloads can keep sidecars in the Guaranteed QoS class without dedicating exclusive cores to them, but must enable two feature gates and configure the static CPU and Memory Managers with a non-none Topology Manager policy. Since the feature is alpha, teams should review the documented limitations and downgrade instructions before relying on it.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-04-296 months ago
Salesforce CLI2.132.14minor*
Agentforce Vibes: governing AI-generated code in your Salesforce orgpostGearset published a blog post on Agentforce Vibes, Salesforce's AI coding assistant that generates Apex, Lightning Web Components and Flows from prompts. The post argues that AI-generated Salesforce code needs automated testing, static analysis, code review and observability in the delivery pipeline before it reaches production. It promotes Gearset's CI/CD, code review, monitoring and backup tooling as the way to provide that governance.platform teamsNo new product capability or change to Agentforce Vibes is described. Platform teams using Salesforce may use the post's list of controls (quality gates on Apex deployments, UI test runs, runtime error monitoring) as a checklist, but the post itself states no new behavior.Gearset Blog ↗Salesforce PlatformAgentforceGearsetwritten 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