platformchangelog.dev
43 tools

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

feedbefore 2026-06-13patches hidden unless security or breaking
2026-06-095 months ago
Jenkins2.567minor*
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-045 months ago
Pulumiv3.245.0minor++++++***
2026-06-035 months ago
Salesforce CLI2.137.6minor*
From Kubernetes Dashboard to Headlamp: Understanding the TransitionpostThe Kubernetes Dashboard project has been archived. The Kubernetes blog presents Headlamp as its successor and maps common Dashboard workflows such as viewing, editing, scaling and deleting resources to Headlamp, which uses standard Kubernetes RBAC. Headlamp adds multi-cluster views, Projects that group related resources by application, plugins including a Flux plugin and an AI Assistant, and both in-cluster and desktop deployment. A step-by-step migration guide is said to be coming soon.platform teamsTeams still using Kubernetes Dashboard will need to plan a move to Headlamp, since the project is archived. Existing kubeconfig and service account access models are said to carry over, so the main work is evaluating the UI and choosing an in-cluster or desktop deployment.Kubernetes Blog ↗Fluxwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
Reconciling the Past: Correcting Records for Unfixed Kubernetes CVEsannouncementThe Kubernetes project says CVE records for three older vulnerabilities (CVE-2020-8561, CVE-2020-8562, CVE-2021-25740) incorrectly listed a fixed version. The Security Response Committee will correct the records on June 1, 2026, marking them as unfixed and affecting all versions. The project says the issues are architectural trade-offs it will not fix in code, and it lists configuration mitigations for each.platform teamsVulnerability scanners may start flagging these issues on clusters that were previously clean, so platform teams should expect new findings. Teams should apply the listed mitigations, including log verbosity and profiling settings, a caching DNS resolver on control plane nodes, and an RBAC audit to remove Endpoints write access from broad roles.Kubernetes Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-05-225 months ago
Crossplanev2.3.1patchsecurity*!
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
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 days104entries published336breaking change lines18security lines82
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