platformchangelog.dev
43 tools

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

feedsince 2026-09-14all releases, patches included
2026-10-292 days ago
CNCF: The boundary problem in agentic AI is a platform problempostThe post argues that the risk of autonomous agents comes from tools and credentials that accumulate beyond what anyone decided, and that instructions alone cannot hold an agent to its scope. It proposes a Safe Operating Model with concentric rings: verified workload identity, declared service-mesh reach, admission-controlled and per-call capability checks, and data-plane authorization keyed to that identity. The agent's own identity is denied rights to modify the objects that define its authority, and changes go through reviewed version-controlled configuration. The source text is cut off before the concrete integration work it refers to.platform teamsPlatform teams would enforce agent boundaries through workload identity, mesh authorization, admission policy on tool bindings, and per-invocation gateway checks, with agent authority changes made only through reviewed config. The article is a conceptual model and names no specific tools or releases in the text provided.CNCF Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
GitLab Orbit: Find vulnerability blast radius without the manual huntannouncementGitLab has made Orbit generally available for Premium and Ultimate customers, starting on GitLab.com with Self-Managed and GitLab Dedicated to follow. Orbit builds a graph from merge requests, pipelines, deployments, security findings and ownership data so users can ask which projects contain a vulnerable component and who owns them. GitLab's Security Analyst Agent and external agents such as Claude Code and Codex can query the same graph over MCP, subject to existing roles.platform teamsPlatform teams on GitLab can use the graph to map which services, base images and pipelines depend on a shared component, instead of assembling that list from scanners and spreadsheets. Teams should still check the graph against runtime inventory, since it only covers what repositories declare on the default branch.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-265 days ago
InfoQ: OpenTofu 1.13 Lets Module Authors Reduce Unknown Values at Plan TimepostOpenTofu released version 1.13, adding functions such as convert and assumenotnull that let module authors resolve count and for_each values at plan time when input is unknown. The release adds experimental linting with four built-in warning rules, an opt-in Symbol Libraries experiment, and removes WinRM support from the remote-exec and file provisioners. It also changes base64gzip output bytes, requires macOS 13 or later, and is the last series with official 32-bit builds.platform teamsPlatform teams maintaining OpenTofu modules can plan conditional resources with unknown YAML inputs, but must ensure generated values always match the declared object type or apply will fail. Teams using WinRM provisioners or base64gzip need migration work, and base64gzip changes may trigger unexpected resource updates.InfoQ ↗OpenTofuwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Amazon ECR now supports replication backfill for existing container imagesannouncementAmazon ECR now supports replication backfill, which replicates existing images in a private registry to configured replication destinations. Previously, replication only applied to images pushed after replication was enabled, so teams had to retag images manually. Backfill jobs can be started with a single API call, up to ten can run concurrently, and per-image progress is visible through new APIs.platform teamsPlatform teams can seed new or existing Regions and disaster recovery destinations with an full image catalog without retagging images. Jobs can be stopped at any time without deleting already replicated images, and the feature is available in all Regions where ECR is offered.What's New with AWS ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-229 days ago
Crossplanev2.4.3patchsecurity++++*!!!!!Crossplane v2.4.3 updates the Go toolchain to 1.26.10, which rejects certificates from compromised eMudhra intermediate CAs (CVE-2026-111943), and removes the AAA Certificate Services and emSign ECC Root CA - G3 roots from the image CA bundle. The release also bundles dependency security updates and fixes a bug where a failed, partial package download could be cached as a valid package. Users with crossplane-edit or crossplane-admin access can now kubectl scale XRs and claims whose XRD serves the scale subresource.platform teamsPlatform teams running Crossplane should upgrade to pick up the Go toolchain and dependency CVE fixes and the discarded-truncated-download fix, which could otherwise leave providers in a crash loop. Teams relying on the scale subresource need to note that edit and admin roles can now scale XRs and claims.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
PHP2Shell: GitLab helps find and remediate critical PHP flawspostPHP fixed two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619 (PHP2Shell), on October 21, 2026, in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The flaws are in the PHP engine, so framework or application changes do not mitigate them, and any web server running PHP is affected. GitLab says its own products are not affected and describes how to use container scanning and code search to find PHP runtimes in projects.platform teamsPlatform teams need to upgrade PHP runtimes in hosts and container images, rebuild images with docker build --pull, and check for PHP installed from source, which container scanning cannot detect. Runtime inventory is needed alongside repository scans to find PHP workloads outside GitLab projects.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-1615 days ago
Automating secure container registry management for air-gapped AWS workloadspostAWS describes an approach for migrating Helm charts and container images into private Amazon ECR repositories inside air-gapped VPCs. It uses ECR repository creation templates, applied through Terraform, to set customer-managed KMS encryption, immutable tags and lifecycle rules on repositories created on first push. A migration tool called ecr-artifact-manager, included in the sample repository, preserves multi-architecture manifests, rewrites Helm chart references, and pulls private source credentials from AWS Secrets Manager.platform teamsPlatform teams in regulated air-gapped AWS environments can define repository security settings once in Terraform and have new repositories inherit them, rather than configuring each repository by hand. Teams should note that the encryption configuration cannot be changed after repository creation, and that enhanced scanning is configured at the registry level, not in the template.AWS Containers Blog ↗HelmAmazon EKSTerraform MCP Serverwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
InfoQ: Chainguard Launches Secure Workspaces and Checks for AI Coding AgentsannouncementChainguard announced two beta products at its Assemble London event. Chainguard Workspaces provides remote development environments based on hardened microVMs. Chainguard Checks runs continuous integration inside the development loop, for code written by developers and AI agents.platform teamsPlatform teams evaluating hosted or agent-facing dev environments and in-loop CI can consider these betas, but the source gives no technical detail, pricing, or availability beyond beta status. Nothing here changes existing pipelines or platforms yet.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-10-1516 days ago
GitLab19.5minorGitLab 19.5 was released on October 15, 2026. The GitLab MCP server and GitLab Secrets Manager are now generally available, and the MCP server gives external agents such as Claude Code and Cursor access to a wider set of GitLab tools. The release also adds beta support for connecting externally connected agents to AI Governance, plus non-default branch vulnerability tracking and several GitLab Duo CLI features.platform teamsPlatform teams can scope CI secrets per job by environment and branch and get audit logs for each secret operation, using existing GitLab permissions. Security teams can see sessions from agents running outside GitLab, with audit events sent to a SIEM, though this ECA capability is in beta.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
CNCF: Extending Kubernetes policy enforcement to runtime security for AI workloadspostNirmata published an open source project, Nirmata Runtime for Kyverno, that uses eBPF and Linux Security Modules to enforce policy on process execution, file access, network egress, and application protocol inside running pods. Policies use the same CEL-based syntax as Kyverno admission policies and start in monitor mode, with denials attributed to the responsible policy and reported as OpenReports objects. The post describes example policies for AI agent pods, such as limiting egress to an LLM gateway, restricting launchable binaries, and detecting agent CLIs in images.platform teamsPlatform teams running agent pods could use per-pod runtime policies to restrict egress, executables, and credential file access beyond what admission control checks. The post provides no benchmarks, adoption data, or independent validation, so the enforcement claims are unverified.CNCF Blog ↗Kyvernowritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
GitLab Secrets Manager: Govern secrets like your codepostGitLab says Secrets Manager is now generally available in GitLab 19.5 for Premium and Ultimate on GitLab.com and Self-Managed, with GitLab Dedicated coming soon. It is built on OpenBao and stores build-time and runtime credentials under GitLab's project and group permissions and audit trail. Jobs receive only the secrets they declare and that match branch and environment scope conditions.platform teamsPlatform teams can replace raw CI/CD variables with scoped secret references and serve Kubernetes via External Secrets Operator, Terraform and OpenTofu data sources, and the Vault-compatible API from one store. Pricing is a paid add-on billed in GitLab Credits, and the source notes a CI/CD variable migration workflow is still in development.GitLab Blog ↗GitLabOpenTofueditorCorrection 2026-10-20: this was listed as a OpenTofu, Helm, GitLab 19.5 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-0823 days ago
CNCF: Don’t give AI agents root. Make them propose the next system state.postThe author argues that autonomous agents should not be given root access to production machines, since agent behavior is nondeterministic and root access offers no reproducibility. He proposes that agents run in short-lived isolated workloads, observe immutable hosts, and submit pull requests for the next system image, which then passes review, build, signing and release before the host consumes it. He states that the agent identity should be able to propose changes without approving, merging, altering pipelines, or signing images. The post is written by a Kairos maintainer and describes a go-ukify alignment fix found by an agent during QA.platform teamsPlatform teams evaluating agents on infrastructure can treat agent write access as a separation-of-authority question: agents propose changes through the same review and build pipeline as humans, with no direct host mutation. The post describes an architectural pattern rather than a shipped product feature.CNCF Blog ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
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-0625 days ago
Argo CDv3.4.10patchbreakingsecurity+~~****!!!!!!!!Argo CD v3.4.10 ships fixes for 11 security issues, including several rated critical: command execution via Kustomize remote refs and Helm config home in the repo-server, a Jsonnet import that reads repo-server files, and an AppProject restriction bypass through PreDelete/PostDelete hooks. It also includes two breaking changes: Kustomize no longer honors helmGlobals.configHome for Helm plugins registered from that directory, and OCI manifests larger than 4 MiB are rejected. The release also adds username logging on login attempts and four bug fixes.platform teamsPlatform teams running Argo CD 3.4 should upgrade to pick up the critical repo-server and AppProject fixes. Teams using Kustomize with Helm plugins from configHome or OCI manifests above 4 MiB need to check their builds before upgrading because those will now fail.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Argo CDv3.3.15patchbreakingsecurity~~*********!!!!!!!Argo CD v3.3.15 ships fixes for 12 security issues and 11 other fixes, with 2 changes marked breaking. Breaking changes: Kustomize builds that render Helm charts no longer honor helmGlobals.configHome, so builds relying on a Helm plugin registered from that directory will fail, and OCI manifests larger than 4 MiB are now rejected. Critical advisories cover command execution via Kustomize remote refs and Helm config home, Jsonnet file reads from the repo-server, and AppProject restriction bypass via PreDelete/PostDelete hooks.platform teamsPlatform teams running Argo CD 3.3 should plan to upgrade, and check any Kustomize-with-Helm pipelines that use a plugin from configHome or OCI manifests over 4 MiB before rolling out. Repo-server exposure from the listed critical issues makes the update a priority.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
GitLab Transcend: Speed you can trust, all the way to productionannouncementGitLab announced more than a dozen features at its Transcend event, including goal-driven agent flows, custom flows, an MCP Server, Artifact Central in beta, Dependency Firewall in early access, and Secrets Manager set to reach GA this month. The vendor says GitLab Orbit context graph reduces agent retries by up to 45x and token use by up to 4.5x during its beta. Credit and usage controls add spend caps and alerts at the subscription, group, and user level.platform teamsPlatform teams evaluating GitLab can plan to govern agent actions and MCP access under existing policy, set AI spend caps, and route packages through Artifact Central and Dependency Firewall. Many capabilities are GA later or in beta or early access, so rollout timing matters.GitLab Blog ↗GitLabJenkinsGitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
Dependency Firewall: Block risky packages before the buildpostGitLab announced Dependency Firewall, now in early access for GitLab.com and GitLab Self-Managed Premium and Ultimate customers. It blocks or warns on packages that match a policy covering malware status, vulnerability severity, license type, and minimum package age, before they are installed in a build. The source also cites five malicious PyPI packages GitLab researchers found in June 2026, four of them typosquats of Flask, Requests, and NumPy.platform teamsPlatform teams can set policy once at the top-level group, with project-level overrides where the strictest rule applies, and run warn mode before switching to block mode with logged bypasses. Teams using Sonatype Nexus or JFrog Artifactory can apply it at the registry, and the GitLab CLI can check a package before it is added.GitLab Blog ↗GitLabeditorCorrection 2026-10-20: this was listed as a GitLab 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
Every artifact your teams ship, assembled right the first timeannouncementGitLab announced Artifact Central, an organization-level registry in beta that replaces project-level package and container registries. Retention rules, storage quotas and publish or pull access are set once at the organization level, with four artifact-specific roles (Admin, Manager, Contributor, Viewer). The beta supports Maven, npm, Docker and OCI, and is available on GitLab.com with Self-Managed availability planned, at no charge during the beta.platform teamsPlatform teams could set artifact storage, quota and access policy in one place instead of per project, and use one hosted, remote or virtual URL for internal and external packages. Existing registries can be added as remotes and converted to hosted repos gradually, so no bulk migration is required.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-301 month ago
Kargov1.12.0minorbreaking++++++++++~~~~****Kargo v1.12.0 removes the Connect-based gRPC API, the createTargetBranch option on git-open-pr, and the author block on git-commit. It changes the git-push default integration policy to RebaseOrMerge and removes the legacy Secret namespace chart values, so upgrades that still set them will fail. The release also adds a tar step, an oci-push srcPath option, cross-account ECR pulls, and per-request actor attribution in API logs.platform teamsPlatform teams upgrading Kargo must check integrations for the removed gRPC API, remove deprecated step fields from promotion tasks, and confirm required Secrets exist in the system and shared resources namespaces before upgrading. Teams relying on rebase-only pushes should set pushIntegrationPolicy to AlwaysRebase in Helm values to keep the old behavior.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-221 month ago
Implement per-pod image pull permissions with ECR repository policies on Amazon EKSpostAWS describes a walkthrough for scoping Amazon ECR image pull permissions to individual Kubernetes pods on Amazon EKS. The approach uses KEP 4412 per-pod credential support in kubelet, with the ecr-credential-provider assuming a team IAM role through a service account annotation and ECR repository policies enforcing access. The post states the feature needs Kubernetes 1.34 or later, with full support on EKS v1.35 or later.platform teamsPlatform teams on multi-tenant EKS can give each namespace its own ECR pull role instead of relying on the shared node role, but they must create a ClusterRole and ClusterRoleBinding for the sts.amazonaws.com audience before nodes join, and must update node credential provider configuration. Pods without the annotation fall back to the node role.AWS Containers Blog ↗Amazon EKSwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules
2026-09-161 month ago
Jenkins Security Advisory 2026-09-16announcementJenkins published a security advisory dated 2026-09-16 listing 13 affected plugins, including Bitbucket Push and Pull Request, Bitbucket Server Integration, Coverage, Gitee, GitLab, Gradle, Keycloak Authentication, OWASP Dependency-Check, Pipeline: Groovy Libraries, Pipeline: Multibranch, Robot Framework, Script Security, and Warnings. The source text does not describe the vulnerabilities, their severity, or the fixed versions.platform teamsTeams running Jenkins with any of the listed plugins should check whether they have them installed and consult the full advisory for affected and fixed versions. The source text gives no details to confirm the scope of exposure.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
categoryallidp & portalsai agents on platformci/cdobservabilitysupply chaincost & governancereports & dx dataenterprise app platforms
showmajor onlyreleasescase studiespostmortemsinclude patches