platformchangelog.dev
43 tools

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

feedbefore 2026-07-04all releases, patches included
2026-07-014 months ago
Salesforce CLI2.141.6minor*
See your serverless: introducing the Headlamp plugin for KnativeannouncementThe Headlamp project announced a Knative plugin for its Kubernetes UI, released as version 0.3.0-beta. The plugin shows Knative KServices, Revisions and DomainMappings in a map view, and lets operators edit traffic splits and tags, with validation that traffic sums to 100%. It also displays effective autoscaling settings against cluster ConfigMaps and surfaces Prometheus metrics when the Prometheus plugin is installed.platform teamsPlatform teams running Knative can inspect routing, revisions, autoscaling and networking from Headlamp instead of switching between kn, kubectl and the Kubernetes UI. Actions such as editing traffic and restarting pods are gated by existing RBAC permissions, but the release is beta and the source gives no details on its maturity.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-06-244 months ago
Salesforce CLI2.140.6minor*
Spotlight on WG Device ManagementpostThe Kubernetes Blog published an interview with the chairs of the Device Management Working Group about Dynamic Resource Allocation (DRA), which the source says recently graduated to GA. The chairs describe DRA as replacing the legacy Device Plugin model with a declarative API that uses ResourceSlice and ResourceClaim objects across modeling, requesting, scheduling and actuation. They list ongoing work on device health monitoring, multi-node support and interconnect-aware device selection.platform teamsPlatform teams running GPU, TPU or other accelerator workloads can plan around DRA as the successor to the device plugin model, with drivers publishing device attributes the scheduler can act on. The source's KEP status table for Kubernetes 1.36 shows several features still in alpha or beta, so teams should check feature maturity before depending on them.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-06-175 months ago
Salesforce CLI2.139.6minor*
2026-06-165 months ago
ServiceNow SDK4.8.0minorSDK 4.8.0
2026-06-105 months ago
Salesforce CLI2.138.6minor+*
Governing change in an AI development erapostGearset argues that AI-generated code increases the volume of changes flowing through Salesforce delivery pipelines, so review and validation need to be automated to keep up. The post cites its State of Salesforce DevOps 2026 report, which says 82% of Salesforce teams trust AI to write code in the build stage and that security and compliance are the largest barriers to wider AI adoption. It recommends org visibility, automated quality gates and post-deployment monitoring, and describes Gearset's product in those terms.platform teamsPlatform teams running Salesforce delivery should expect more changes per sprint from AI tooling, so manual review and approval steps may need to be automated in the pipeline. The post gives no new product capability or concrete change beyond the vendor's own positioning.Gearset Blog ↗Salesforce PlatformAgentforceGearsetwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-06-035 months ago
Salesforce CLI2.137.6minor*
2026-05-275 months ago
Salesforce CLI2.136.8minor++
2026-05-225 months ago
Salesforce change sets and their hidden limitspostThe Gearset blog post explains how Salesforce change sets move metadata from a sandbox to a production org through a deployment connection, using the Metadata API. It describes limits including no org-to-org moves across unrelated orgs, manual component selection, a dependency tool that misses indirect links, locked uploads that must be cloned and re-uploaded, and profile deployments that overwrite target permissions.platform teamsPlatform teams running Salesforce release pipelines should expect change sets to need manual dependency review, full rebuilds after any fix, and careful handling of profile metadata. The post is a vendor article promoting an alternative deployment tool, so its framing is not independent evidence.Gearset Blog ↗Salesforce PlatformGearsetwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Enterprise Salesforce governance: how to enforce compliance without slowing downpostGearset, a Salesforce DevOps vendor, argues that automated release policy enforcement can replace manual approval workflows in Salesforce delivery without slowing teams down. The post describes its Continuous Delivery Rules, role-based access controls, change monitoring, and backup and sandbox seeding features, and lists SOX, ISO 27001, HIPAA and GDPR/CCPA support. It cites Ninety One, an asset manager, as a customer using the tool for deployment governance.platform teamsPlatform teams running Salesforce delivery can see the vendor's approach to pipeline gating, separation of duties and audit trails. The post provides no independent data, and the compliance and speed claims are the vendor's own and are not verified in the text.Gearset Blog ↗Salesforce PlatformAgentforceGearsetwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-05-205 months ago
Salesforce CLI2.135.7minor++++**
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