platformchangelog.dev
43 tools

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

feedbefore 2026-08-21patches hidden unless security or breaking
newest entries
2026-08-202 months ago
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-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 ↗GitHub ActionsAmazon EKSAWS DevOps Agentwritten 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
2026-08-143 months ago
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-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 ↗Amazon EKSAWS DevOps Agentwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-08-043 months ago
Terraform MCP Serverv1.2.0minor
2026-07-144 months ago
Terraform MCP Serverv1.1.0minor
2026-06-194 months ago
K8sGPTv0.4.34patchsecurity+**!!
2026-06-095 months ago
Terraform MCP Serverv1.0.0major
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