platformchangelog.dev
43 tools

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

feedbefore 2026-09-02patches hidden unless security or breaking
newest entries
2026-09-012 months ago
Flaggerv1.45.0minor+++**
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 ↗Amazon EKSAWS DevOps AgentK8sGPTwritten 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 ↗GearsetSalesforce Platformwritten 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 ↗GearsetSalesforce Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-202 months ago
GitLab19.3minor
CloudBees Smart Tests Helps Leading Software Company Double Release Velocity by Saving 40K Testing Hours in One Yearcase studyCloudBees published a case study about an unnamed leading software company that adopted its AI-powered Smart Tests. The vendor reports a doubling of annual release velocity, 40,000 saved test execution hours, and an 80% cut in cloud costs. The source gives no methodology or baseline for these figures.platform teamsPlatform teams evaluating test selection in CI pipelines may find this relevant, but the figures are vendor-reported and unverified. The source does not describe how the tool works or how the results were measured.CloudBees Blog ↗CloudBeeswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Building an AI-Powered Incident Bot with Octopus DeploypostThe Octopus Deploy blog describes a proof-of-concept incident bot called Octopus Healer. It receives Prometheus alerts, sends pod logs and metrics to an AI model for a structured remediation suggestion, and maps that suggestion to a predefined Octopus Deploy runbook. An operator selects the environment and approves the runbook in Slack before execution.platform teamsPlatform teams can see a pattern for routing AI-suggested Kubernetes remediations through an existing deployment tool with its approvals, permissions and audit history, instead of letting the model generate kubectl commands. The author states it is a PoC with hardcoded remediation templates and a 30-minute in-memory approval TTL, so it is not a shipped product.Octopus Deploy Blog ↗Octopus Deploywritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-192 months ago
Let The Buzz Begin…Introducing CloudBees UnifyannouncementCloudBees has introduced CloudBees Unify, a DevOps solution it describes as AI-driven. The company says it integrates with existing tools such as GitHub and Jenkins and provides unified visibility and security without requiring migration. The source text gives no technical details, features, or availability.platform teamsPlatform teams already running Jenkins or GitHub may be able to evaluate it without migrating pipelines, but the source does not describe what changes in practice. No concrete capabilities can be confirmed from this text.CloudBees Blog ↗CloudBeesJenkinsGitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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
2026-08-182 months ago
Jenkins2.578minor
2026-08-173 months ago
Streamline your GitHub journey with AWS CodePipeline and AWS DevOps AgentpostAWS published a walkthrough for connecting AWS DevOps Agent to GitHub repositories, AWS CodePipeline, CloudWatch alarms and a Lambda webhook. When a pipeline stage fails, a CloudWatch alarm or EventBridge rule triggers the agent, which investigates logs and recent commits. The post shows two sample failures, a bad DynamoDB table name and a misspelled npm dependency, where the agent identified the offending change.platform teamsPlatform teams running CodePipeline with GitHub sources can evaluate an agent that starts investigations from pipeline alarms and proposes remediation. The setup requires IAM roles, a webhook stored in Secrets Manager, and a Lambda bridge, and the post reports no measured results beyond the sample app.AWS DevOps Blog ↗AWS DevOps AgentGitHub ActionsAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Sandboxing local AI AgentspostOctopus Deploy published a how-to for running local AI agents inside a Vagrant virtual machine sandbox. The sandbox runs Claude Code as a restricted user, mounts only the ~/Code directory over NFS, and stores the Anthropic API key in a root-owned file the agent can read. The post says the design prioritizes convenience over security, and its stated non-goals include guaranteeing that malicious prompts cause no harm.platform teamsPlatform teams evaluating local agent use can reuse the pattern of a restricted OS user, limited directory mounts, and denied git push, but the post says credentials can still be exfiltrated by the agent. Teams should treat this as a starting point and not as a hard security boundary.Octopus Deploy Blog ↗Octopus Deploywritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Octopus Easy Mode - Self SupportpostThe Octopus Deploy blog post walks through a demo in which a deployment is set up to fail on a missing Kubernetes secret, then a Platform Hub process template is added. The template runs a Claude Agent step on failed deployments that uses Octopus and GitHub MCP servers to pull deployment logs, step configuration, git changes, and matching GitHub issues. The demo uses a mock Kubernetes target and a mock git repository that resets periodically.platform teamsA platform team could publish a shared AI self-support step as a Platform Hub process template and attach it to projects, with the prompt and MCP servers managed centrally. It requires Claude, GitHub and Octopus Agent API credentials, and the post states that the hosted demo setup is not a production pattern.Octopus Deploy Blog ↗Octopus Deploywritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-133 months ago
Act faster with our new Slack integrationannouncementOctopus Deploy has added a Slack integration that sends subscription event notifications to Slack channels, alongside existing webhook and email options. It also adds a Send a Slack Message step that uses OAuth so a deployment or runbook can post a message to a chosen channel, such as just before a manual intervention step. Event filters can scope notifications by project, tag, and environment.platform teamsPlatform teams using Octopus can route deployment failures, variable changes, API expiries and MCP token issuance to Slack channels, and can notify approvers at manual intervention points. Teams on other CI/CD tools will not be affected.Octopus Deploy Blog ↗Octopus Deploywritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-123 months ago
Argo CDv3.3.14patchsecurity****!!
2026-08-113 months ago
Argo Workflows4.1.0minor+
2026-08-103 months ago
Automate SageMaker HyperPod incident triage and root-cause-analysis with AWS DevOps AgentpostAWS describes a solution that connects a SageMaker HyperPod cluster to AWS DevOps Agent. EventBridge events and a periodic Kubernetes-state audit feed the agent, which triages and root-causes conditions that still need a human decision and sends a verdict email. The agent is configured read-only, with no SSM, SSH, or action-taking permissions, and the solution deploys as one CloudFormation stack per cluster.platform teamsPlatform teams running HyperPod on EKS or Slurm can deploy an observe-and-report incident agent alongside existing self-healing, with custom skills that can be edited for their own conditions. Teams should check the read-only boundary and the cost of polling and investigations against their own operating model.AWS DevOps Blog ↗AWS DevOps AgentAmazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
How to deploy Salesforce Agent Script metadatapostGearset describes how to deploy Salesforce Agent Script metadata (AiAuthoringBundle) between orgs. Salesforce's draft and commit lifecycle means only the bundle should be deployed, since Bot, BotVersion and GenAiPlannerBundle are generated when a draft is committed in the target. The post says Gearset deploys the script as a draft when the target is already committed and offers an option to commit automatically after deployment, currently for org-to-org deployments only.platform teamsPlatform teams deploying Agentforce agents need to package only the AiAuthoringBundle and account for the draft-versus-committed state of the target org, or the deployment is rejected or the agent stays inert until someone commits it manually. Automatic commit is available in Gearset for org-to-org deployments, with pipeline support stated as upcoming.Gearset Blog ↗GearsetSalesforce PlatformAgentforcewritten 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