platformchangelog.dev
43 tools

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

feedbefore 2026-09-02all releases, patches included
newest entries
2026-09-012 months ago
Flaggerv1.45.0minor+++**
2026-08-312 months ago
Fluxv2.9.5patch+++++~~~~~~~~~~
Optimize EKS operations with agents: Reduce MTTR with AWS DevOps Agent and a Kubernetes OperatorpostAWS describes a Kubernetes Operator that watches EKS pods, collects logs, events, node-level data and manifests when a failure occurs, and sends that context to AWS DevOps Agent through a generic webhook. The post says the Operator stores evidence in S3 or CloudWatch Logs before pods are rescheduled or deleted. Setup requires an Agent Space, an IAM role with Pod Identity, and building the Operator image from source because no prebuilt image is provided.platform teamsPlatform teams running EKS can evaluate automated incident evidence capture and agent-driven investigation, but must set up IAM, Systems Manager registration on nodes, and build and host their own image. Node-level collection is unavailable on Fargate.AWS DevOps Blog ↗K8sGPTAmazon EKSAWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-282 months ago
Build your own continuous modernization pipeline with AWS Transform custompostAWS describes a do-it-yourself continuous modernization pipeline that runs AWS Transform custom as a step in GitHub Actions. The walkthrough uses a sample Spring Boot application and covers Dependabot alert remediation and auto-documentation on pull requests. The post provides shell scripts that call the atx CLI in headless mode with up to three retries.platform teamsPlatform teams could wire AI code transformations into existing CI/CD pipelines, but the example runs with the --trust-all-tools flag, which removes interactive confirmation and needs review against security policy before production use. The source text is cut off before the remaining practices are covered.AWS DevOps Blog ↗GitHub ActionsAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Two views, one org: mapping business processes to Salesforce metadatapostThe post argues that Salesforce teams need a map linking business processes to the metadata that implements them, because org documentation goes stale and changes carry risk. It describes three traditional discovery methods (talking to the business, reviewing regression tests, and reviewing historical tickets) and notes that dependency tooling is limited by API restrictions. It then presents Gearset's Agent and Org Intelligence as a way to generate a live, dependency-aware map of org metadata.platform teamsPlatform teams running Salesforce may find dependency mapping before changes useful, but the post gives no measured results and the claimed benefits are the vendor's own. The post also notes that AI reads implementation rather than intent, so changes still need review against business requirements.Gearset Blog ↗Salesforce PlatformGearsetwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-272 months ago
Argo CDv3.4.8patchsecurity****!!!
Debunking the hotfix pipeline mythpostThe Octopus Deploy blog argues that hotfix pipelines, which skip lower environments to deploy straight from Staging to Production, are a symptom of a suboptimal main deployment pipeline. The author describes a former team that rebuilt its pipeline with Octopus Deploy, Azure DevOps and Redgate tooling, moving production deployments from quarterly to weekly and dropping the need for a hotfix path. The post then lists modern delivery principles and open questions about versioning and merging hotfix pipelines.platform teamsPlatform teams evaluating hotfix pipelines are advised to invest first in a single, identical promotion path with build-once artifacts, rather than a separate fast lane. The post offers no benchmark data, so the claimed benefits rest on one team's anecdote.Octopus Deploy Blog ↗Octopus Deploywritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-262 months ago
AI-driven software delivery with Kiro, AWS DevOps Agent and Bluebox by DynatracepostAWS and Dynatrace describe a workflow in which Kiro retrieves runtime topology and traffic data from Bluebox via CLI before generating a pull request, and AWS DevOps Agent investigates a simulated traffic-spike incident. The agent's findings and mitigation plan are filed as a GitHub issue, and Kiro then opens a remediation pull request that a human reviews and merges. The post uses a travel-booking example, and the reported results come from that example rather than measured data.platform teamsPlatform teams evaluating AI incident agents can see a pattern where investigation output is written to GitHub issues and fixes flow through normal PR review and CI/CD. The post does not give benchmarks, adoption figures, or availability details for the release management capability, which is in Preview.AWS DevOps Blog ↗AWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-252 months ago
Jenkins2.579minor+~*******
A virtual teammate vs a copilot: what’s the difference?postGearset argues that AI coding tools differ between copilots, which assist a developer step by step, and virtual teammates, which take a ticket and return a review-ready pull request. The post lists questions for evaluating tools, including whether they hold org context, are shared across a team, adapt to feedback, and work within existing governance. It closes by promoting the Gearset Agent.platform teamsPlatform teams evaluating agents for Salesforce delivery should check whether an agent runs through the same tests, security checks and review gates as human changes, and whether it has org context. The post itself gives no measured results and no concrete product change.Gearset Blog ↗Salesforce PlatformGearsetwritten 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