platformchangelog.dev
43 tools

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

feedsince 2026-07-28all releases, patches included
2026-10-2110 days ago
InfoQ: Presentation: AI is an Amplifier: Scale High Performance, Not DysfunctionreportDORA's Nathen Harvey presents findings from the 2025 DORA survey, which had nearly 5,000 respondents and ran June 13 to July 21, 2025. He reports that about 90% of respondents use AI at work and that the survey frames AI as an amplifier of existing organizational systems. The source text is cut off before the detailed relationship findings.platform teamsPlatform teams evaluating AI-assisted development should note that the talk argues gains in code generation do not reach production without work on the wider delivery system, such as review and release steps. The source gives no concrete tooling change.InfoQ ↗DORA State of DevOps / AI-assisted development reportwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-0823 days ago
Track organization-wide security risk in one dashboardpostGitLab 19.4 adds an organization-level security dashboard in beta for GitLab.com Ultimate users. It shows a risk score calculated from severity and age of open vulnerabilities, KEV status, and EPSS scores, with trend, age, severity and CWE charts across all top-level groups. Third-party scanners that output SARIF can also feed findings into the same view.platform teamsPlatform and security teams running GitLab across multiple top-level groups can get a single rolled-up vulnerability view without manual reporting, provided they have an Organization with Owner access and at least one scanner with a completed default-branch scan. The feature is beta and limited to GitLab.com.GitLab Blog ↗GitLabeditorCorrection 2026-10-20: this was listed as a GitLab 19.4 release by mistake. It is GitLab Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-011 month ago
The Future of Platform Engineering reportreportOctopus Deploy published the 2026 Future of Platform Engineering report, based on primary survey data from 379 technical platform practitioners and a review of current literature. The report finds that automation and efficiency are the main reasons organizations adopt platforms, and that lack of clear strategy is a more common obstacle than technical complexity. It also reports that teams with mandatory adoption achieved most of their goals more often (62.2%) than teams with optional adoption (about 27.5%).platform teamsPlatform teams evaluating adoption models may weigh the reported link between mandatory adoption, leadership direction and goal delivery when deciding how to position a platform. The source gives no methodology detail beyond the sample size, so the figures are best treated as directional.Octopus Deploy Blog ↗DORA State of DevOps / AI-assisted development reportState of Platform Engineering reportOctopus Deploywritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-221 month ago
Salesforce DevOps tools: why the highest-performing teams don’t stop at deploymentreportGearset publishes an analysis based on its State of Salesforce DevOps 2026 report, arguing that teams covering more of the six DevOps lifecycle stages report fewer bugs, less rework and less downtime. The post says high adopters are nearly twice as likely to keep error rates below 5%, spend 56% fewer hours on rework and lose 62% less time to downtime. It also reports that observe and operate are the least covered stages, and that 43% of teams apply no extra review to AI-generated changes.platform teamsPlatform teams running Salesforce can use the stage-by-stage coverage model to audit their own toolchain, particularly the observe and operate stages. The post is written by a vendor selling a competing DevOps product and the survey methodology is not described in the source text.Gearset Blog ↗Salesforce PlatformGearsetwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-192 months ago
The 2026 State of Code Abundance Report: Exposing the Enterprise AI Readiness GapreportCloudBees published the 2026 State of Code Abundance Report. It cites a self-assessment called the CARE Score, in which organizations rated themselves an average of 83.6 out of 100 across categories including governance, cost visibility, productivity measurement and pipeline visibility. The source text gives no sample size, methodology or further results.platform teamsThe excerpt gives no concrete change for platform teams. The only figure is a self-reported average score, so it cannot be used to benchmark readiness until the full methodology is published.CloudBees Blog ↗CloudBeeswritten 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 published335breaking 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