platformchangelog.dev
43 tools

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

feedbefore 2026-06-22patches hidden unless security or breaking
newest entries
2026-06-185 months ago
GitLab19.1minor
2026-06-165 months ago
Jenkins2.569minor+++~*****
2026-06-095 months ago
Jenkins2.567minor*
2026-06-055 months ago
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-05-275 months ago
Jenkins Security Advisory 2026-05-27announcementJenkins published a security advisory dated 2026-05-27 listing 11 plugins as affected, including Active Directory, Credentials Binding, GitHub Integration, LDAP and Pipeline: Groovy Libraries. The source text gives no vulnerability descriptions, severity ratings, CVE identifiers or fixed versions.platform teamsTeams running Jenkins should check whether any of the listed plugins are installed and follow the advisory for fixed versions and remediation. The source text does not say what the fixes are.Jenkins security advisories ↗Jenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-05-265 months ago
Jenkins2.566minor+*
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
2026-05-215 months ago
GitLab19.0major
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-146 months ago
Helmv4.2.0minor+~~~~~~~~*********
2026-05-136 months ago
Kubernetes v1.36: Advancing Workload-Aware SchedulingpostKubernetes v1.36 introduces the Workload and PodGroup APIs under scheduling.k8s.io/v1alpha2, separating the static Workload template from runtime PodGroup state. It adds a PodGroup scheduling cycle that evaluates a group atomically, along with first iterations of topology-aware scheduling and workload-aware preemption. The release also adds ResourceClaim support for PodGroups and a first phase of Job controller integration with the new API.platform teamsTeams running batch or AI/ML training workloads on Kubernetes will see the v1alpha2 API replace v1alpha1, and the Pod workloadRef field is replaced by schedulingGroup, so manifests and controllers need updating. Gang scheduling and topology placement are alpha, and the source notes limits on heterogeneous groups and inter-Pod dependencies, so plan for partial guarantees.Kubernetes Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-05-126 months ago
Fluxv2.8.7patchsecurity++~~~~~~!
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