platformchangelog.dev
43 tools

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

feedbefore 2026-09-14patches hidden unless security or breaking
2026-09-041 month ago
Kubernetes v1.37: KubeletInUserNamespace (aka Rootless mode) Graduates to BetapostKubernetes v1.37 promotes the KubeletInUserNamespace feature gate to beta, allowing kubelet, container runtimes, CNI plugins and kube-proxy to run as a non-root user inside a Linux user namespace. The feature gate is now enabled by default, but nodes only run rootless if they are set up that way outside Kubernetes. Kubelet now reports a runningInUserNamespace property on nodes.platform teamsPlatform teams can run node components without host root to limit container-breakout impact, but some CNI and CSI drivers may break, so test them first. Administrators can use the new runningInUserNamespace node property to keep root-dependent workloads off rootless nodes.Kubernetes Blog ↗editorCorrection 2026-10-20: this was listed as a Kubernetes MCP Server v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-021 month ago
Jenkins Security Advisory 2026-09-02incidentJenkins published a security advisory dated 2026-09-02 that lists affected components: Jenkins core, update-center2, and about 18 plugins including GitLab, LDAP, SAML, Microsoft Entra ID, Script Security, and Pipeline: Groovy Libraries. The source text lists only the affected components and does not describe the vulnerabilities, severity, or fixed versions.platform teamsPlatform teams running Jenkins controllers should check the advisory for fixed Jenkins core and plugin versions and review which installed plugins are affected. The source text does not give the fixed versions, so the advisory itself must be consulted before deciding on upgrades.Jenkins security advisories ↗Jenkinswritten 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
2026-08-173 months ago
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-053 months ago
Jenkins Security Advisory 2026-08-05announcementJenkins published a security advisory dated 2026-08-05 listing affected components. Jenkins Core is among them, along with 16 plugins, including AWS CodeBuild, CodeSonar, Google Chat Notification, Qualys Container Scanning Connector and SCM-Manager. The source text does not describe the vulnerabilities, their severity, or the fixed versions.platform teamsTeams running Jenkins core or any listed plugin should check their installed versions against the advisory and apply the fixes it describes. The source text gives no versions, CVE identifiers or severity, so those details must be taken from the full advisory.Jenkins security advisories ↗Jenkinswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-07-233 months ago
PlatformEngineering.org: Understanding platform engineering's role in staying compliant with the EU’s CRApostThe article discusses how platform engineering can help teams meet the EU Cyber Resilience Act's secure-by-design requirements. It proposes embedding secure-by-default standards, automated SBOM generation, and incident reporting into an internal developer platform. The source text is a short summary and does not cite specific tools, releases, or data.platform teamsPlatform teams evaluating CRA readiness could consider building SBOM generation and incident reporting into their golden paths. The source gives no concrete implementation details or requirements to act on.PlatformEngineering.org Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-06-244 months ago
Jenkins Security Advisory 2026-06-24reportJenkins published a security advisory dated 2026-06-24 listing 18 plugins as affected, including Git client, Pipeline: Groovy, Script Security, GitHub Branch Source and MCP Server. The source text gives no vulnerability descriptions, severities, CVE identifiers or fixed versions.platform teamsTeams running Jenkins should check whether any of the listed plugins are installed and apply the fixed versions from the official advisory. This feed item does not state what the fixes are or how severe they are.Jenkins security advisories ↗Jenkinswritten 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