Platform Changelog

feedbefore 2026-10-20all releases, patches included

2026-10-1912 days ago

InfoQ: Buildkite Adds Scoped Secrets and New Agentic CI ToolspostBuildkite has introduced pipeline-scoped secrets and new Model Context Protocol tools for validating pipelines, diagnosing failed builds and repairing webhooks. It also added Linux arm64 support to its GitHub Actions compatibility layer and expanded OpenTelemetry data in Buildkite Agent v4.1.0.platform teamsPlatform teams running Buildkite can scope secrets to individual pipelines and let MCP-connected agents validate pipelines and diagnose failures. Teams relying on the GitHub Actions compatibility layer on arm64 runners and on Buildkite Agent telemetry can now evaluate those changes.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1615 days ago

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

Xcode 27 runner image generally availablepostGitHub has made the Xcode 27 runner image generally available for building and testing Apple applications in GitHub Actions. The image runs on macOS 27 and includes the Xcode 27 toolchain and Apple SDKs. It is available on Apple Silicon (arm64) runners only, selected with the xcode-27 and xcode-27-xlarge labels.platform teamsTeams building Apple apps on GitHub-hosted runners can target the xcode-27 or xcode-27-xlarge labels, and existing workflows using those labels need no change. Intel runners are not supported, so pipelines that depend on them will need a different runner.GitHub Changelog ↗GitHub Actionswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Using Claude Code for Salesforce? Don’t miss these security and governance gapspostGearset's blog post lists governance and security gaps for teams using Claude Code, Cursor or Codex to build on Salesforce. The gaps include over-broad local permissions, prompt injection, changes that bypass testing and review, inconsistent team standards, and unplanned maintenance. The post recommends running agents in a container, using least-privilege integration users, restricting MCP toolsets, and routing all AI-generated changes through a CI/CD pipeline.platform teamsPlatform teams that let agents reach Salesforce orgs through MCP should scope credentials to least privilege, restrict enabled MCP toolsets, and require AI-generated changes to pass the same pipeline checks as human changes. The post's recommendations are general, and it promotes Gearset's own product as the solution.Gearset Blog ↗Gearset Salesforce Platform Salesforce DX MCP Server Agentforcewritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1516 days ago

OpenFeaturev0.18.0minorbreaking+++++~~~flagd: v0.18.0

Helmv3.22.1patchsecurity~~~!Helm v3.22.1 was released with a security item that bumps dependencies to remove Go package vulnerabilities. Other changes update the k8s.io Go packages to v0.37.1 and the OpenTelemetry OTLP trace exporters to v1.45.0. The notes also state that the next patch releases for Helm 4.3.2 and 3.22.2 are scheduled for November 11, 2026, and that Helm 4.4.0 is scheduled for January 13, 2027.platform teamsPlatform teams running Helm 3 get dependency-level CVE fixes in this release, but the source does not name the affected packages or the tool's own code. The notes say there will be no further Helm 3 minor releases after this line, so teams should plan migration to Helm 4.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

OpenFeaturev0.17.1patchsecurity!flagd: v0.17.1

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

Helmv4.3.1patch*****

Connect your agents to your software lifecycle with the GitLab MCP serverpostGitLab announced general availability of its MCP server with GitLab 19.5, letting MCP-compatible agents work with code, merge requests, work items and pipelines. The release adds tools for branches, file reads, semantic code search, pipeline inspection and artifact reads, and consolidates related tools into fewer calls. Agents can also start and follow GitLab Duo Agent Platform flows, with actions running under existing GitLab permissions.platform teamsPlatform teams evaluating agent access to GitLab can connect external agents with permissions inherited from GitLab, and can limit the tool surface with toolsets. The source gives no measured figures for the claimed reduction in calls or context.GitLab Blog ↗GitLabeditorCorrection 2026-10-20: this was listed as a GitHub Actions, 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

Get every merge request in front of the right reviewer, fasterpostGitLab 19.5 makes Recommend Reviewers Flow generally available on GitLab.com, Self-Managed and Dedicated. When a merge request is created, the flow suggests one reviewer based on workload, time zone, availability and expertise defined by approval rules and CODEOWNERS, and shows its reasoning. Authors can assign the suggested reviewer with one click. The vendor also states that Code Review Flow costs a flat 0.25 GitLab Credits per review and cuts per-review cost by 99% against a manual review estimate.platform teamsPlatform teams using GitLab can enable the flow as a project trigger and rely on CODEOWNERS and approval rules as the input for reviewer routing. The benefit to review load and time to first review is the vendor's claim and no independent data is given.GitLab Blog ↗GitLabeditorCorrection 2026-10-20: this was listed as a 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

Unblock agentic software delivery with governed code reviewannouncementGitLab says Code Review Flow, part of GitLab Duo Agent Platform, is now generally available and runs as a CI/CD job on GitLab-hosted or self-hosted runners. Teams can set custom review instructions at the project, group or instance level, and choose GitLab-managed or self-hosted models. The post lists roadmap items including extended analysis, approve or request-changes decisions, risk assessment and local review in Duo CLI.platform teamsPlatform teams can run automated agentic review inside existing merge request, pipeline and approval controls, and can select self-hosted models for air-gapped or regulated setups. The $0.25 per review price and 100x ROI figure are vendor claims, and the source gives no methodology for them.GitLab Blog ↗GitLab GitHub Actionswritten 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 ↗GitLab OpenTofueditorCorrection 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-1318 days ago

Jenkins2.586minor+++++****Jenkins 2.586 was released with nine changes: five additions and four fixes. Added items include standardised shadows and focus rings for controls, removal of the Manage Jenkins breadcrumb menu, updated User settings pages, and a warning about unsafe authorization strategy. Fixes cover readOnlyMode propagation in dropdown fragments, locale handling in the search index, log recorder level updates, and dialog width limits.platform teamsPlatform teams running Jenkins controllers get UI changes and a warning when the authorization strategy is unsafe, which may prompt a review of their security configuration. The release notes list no breaking changes to pipelines or APIs.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Make every AI credit count: See, cap, and reduce agent spendannouncementGitLab describes new controls in its Duo Agent Platform for managing agent spend. These include per-user and per-group credit caps with alerts at 50%, 80% and 100% and an automatic pause at the cap, plus Impact Analytics for breaking spend down by team, task and model. GitLab also says three open-weight models are now hosted, with internal benchmark claims of matching frontier models at lower cost, and that its Orbit context graph reduces agent retries.platform teamsPlatform teams using GitLab can pin models per feature and set per-user credit caps today, with Impact Analytics in early access. Orbit is in free beta on GitLab.com and is slated for general availability next month, and its cost benefits rest on GitLab's own testing.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Scaling Git for the agentic software factoryannouncementGitLab describes next-gen SCM, a redesigned Git backend built to serve thousands of concurrent agents while keeping the Git protocol, and says it is in private beta. The post cites Anthropic's monorepo growth from about 2,500 daily merges in May to more than 30,000 in September, and Anthropic's own Scion system built for that monorepo. GitLab says early internal tests showed up to 50x faster workloads, up to 2x fewer tokens and up to 1,000x less network traffic, described as peak results under specific conditions.platform teamsPlatform teams evaluating GitLab for agent-heavy workloads can request private beta access to test next-gen SCM against their own repositories. The performance figures are vendor test results and have not been validated under sustained concurrent load, so they should not be used for capacity planning yet.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

GitLab's agent orchestration eliminates the wait between development stagesannouncementGitLab announced agent orchestration capabilities in GitLab Duo Agent Platform, including goal-driven flows that run review, tests, security scans and approvals as one sequence. It also announced GitLab for Slack, which starts flows from Slack threads, and Custom Flows, which can be triggered by mentions, assignments or pipelines. The source says Custom Flows are generally available, while the MCP server and GitLab for Slack are slated for general availability later this month.platform teamsPlatform teams running GitLab can evaluate agents that act on pipeline failures and merge workflows, with the stated requirement of GitLab 19.3 or later and Duo CLI 9.17.0 or later on Premium or Ultimate. The source gives no metrics for the claimed delivery speedups, so teams would need their own measurements before relying on them.GitLab Blog ↗GitLabwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Introducing remote MCP for Octopus DeploypostOctopus Deploy now includes a built-in remote MCP server, so agents can connect over HTTP to an instance's /mcp endpoint without a local install. The server initially exposes a selected set of core features covering spaces, projects, tenants, deployments, runbooks, task logs, audit events and tenant variables, with access depending on the authentication method and granted permissions. Octopus Cloud customers can use it now and Octopus Server customers will get it in the 2026.3 release. The company says scoped API keys, OAuth for the MCP server, agent-aware policies and an improved audit log are planned for the coming months.platform teamsPlatform teams running Octopus can connect agents without distributing and updating a local MCP server on every machine. Governance controls such as scoped API keys, agent-aware policies and agent audit filtering are not yet available, so teams should plan access controls before letting agents trigger deployments.Octopus Deploy Blog ↗Octopus DeployeditorCorrection 2026-10-20: this was listed as a Octopus Deploy release by mistake. It is Octopus Deploy Blog coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1219 days ago

Argo Rolloutsv1.10.1patchbreaking**Argo Rollouts v1.10.1 ships two fixes cherry-picked to the 1.10 line. The Rollouts dashboard now binds only to the local interface by default, which is marked as a breaking change. The release also allows Bidirectional mountPropagation on privileged containers, fixing issue #3130.platform teamsTeams that reached the Rollouts dashboard over a non-local address will need to expose it explicitly or port-forward after upgrading. Teams running privileged workloads that need bidirectional mount propagation can now use that setting on this version.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo Rollouts1.9.2patchbreakingsecurity*!Argo Rollouts v1.9.2 changes the Rollouts dashboard to bind only to the local interface by default. The release notes mark this as a breaking change for users who expose the dashboard through a custom Helm chart or another method. The release also lists a security fix, but the notes do not describe its details.platform teamsTeams that reach the Rollouts dashboard through a custom Helm chart or ingress must now explicitly configure exposure, or the dashboard will be unreachable from outside the local interface. Teams should review their dashboard access setup before upgrading.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo Rolloutsv1.8.5patchbreaking**Argo Rollouts v1.8.5 ships two fixes. The Rollouts dashboard now binds only to the local interface by default, which is marked as a breaking change. A yarn.lock file was also updated with correct dependencies.platform teamsTeams that reach the Rollouts dashboard over the network by default will need to expose it explicitly or port-forward to it after upgrading. The yarn.lock fix is a build-level correction with no stated effect on runtime behavior.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo CDv3.5.5patch**********

Argo CDv3.4.11patch********

Argo CDv3.3.16patch****

Kargov1.12.4patchKargo released v1.12.4 on 2026-10-12. The release notes list five changes, one of which is a security item bumping the step-security/harden-runner GitHub Action from 2.21.1 to 2.22.0. The other four are maintenance changes such as dependency bumps, CI, tests and docs.platform teamsThe only security-related change is a CI action dependency bump, not a fix in Kargo's own code, so teams running Kargo see no concrete behavior change from the notes provided. Teams may still want to confirm the full changelog before upgrading.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Kargov1.11.8patchKargo v1.11.8 was released with 7 changes, including one security item bumping the step-security/harden-runner GitHub Action from 2.21.1 to 2.22.1. The other six changes are maintenance items such as dependency bumps, CI, tests and docs, which the source condenses and omits.platform teamsPlatform teams running Kargo in their delivery pipelines get a patch release with a CI hardening action bump; the source does not describe any change to runtime behavior, configuration, or APIs. The security change is to a build-pipeline action, not a vulnerability fix in Kargo's own code.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Kargov1.10.15patch

Kargov1.9.15patch

Kargov1.8.19patch

InfoQ: Spotify More Than Doubled Monthly Code Changes as AI Accelerated Developmentcase studySpotify reports that AI-assisted development more than doubled its monthly merged changes. The company says it is reviewing quality and reliability controls across its engineering organization in response. Described changes include testing, observability, rollback capacity, workload prioritization and automated maintenance.platform teamsPlatform teams facing a similar rise in change volume can compare their testing, observability and rollback practices against the areas Spotify names. The source gives no specific tooling, metrics or figures beyond the merged-change increase.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

InfoQ: GitLab 19.4 Adds Goal-Driven Agents and Tighter Cost ControlspostGitLab released version 19.4 of its DevSecOps platform. The release adds a goal-driven mode to GitLab Duo CLI, three hosted open-weight models, a larger set of Model Context Protocol tools, and more detailed controls for AI spending.platform teamsPlatform teams running GitLab can now set AI spending controls and use a broader MCP tool set when agents consume GitLab APIs. The source text does not give details on the controls or tool permissions, so the specifics need checking in the release notes.InfoQ ↗GitLabeditorCorrection 2026-10-20: this was listed as a GitLab 19.4 release by mistake. It is InfoQ coverage, not release notes from the project.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1120 days ago

Agentic AI in DevOps: Exploring Use Cases for the CloudBees MCPpostCloudBees published a blog post describing use cases for its Unify platform combined with an MCP server, focused on pipeline diagnostics and security remediation. The source text is a short teaser and does not describe specific features, releases, or results. The vendor says the combination reduces DevOps tool sprawl and keeps developers in flow without context switching, but these are unverified claims.platform teamsA platform team evaluating CloudBees could look at whether an MCP server for pipeline diagnostics fits its tooling, but the source gives no concrete capabilities, permission model, or governance details to assess. No concrete change can be confirmed from this text.CloudBees Blog ↗CloudBeeswritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-1021 days ago

InfoQ: Cloudflare Traces Turns the Proxy Layer into OpenTelemetry Spans, with New Volume-Based PricingpostCloudflare put Traces into open beta, extending its automatic tracing from Workers to security rules, transformations, cache, routing and origin handling, emitted as OpenTelemetry spans. Traces accept and forward W3C traceparent headers, and Trace Rules allow targeted sampling. Pricing moves to ingestion and retention volume starting December 1.platform teamsPlatform teams that use Cloudflare in front of services can get proxy-layer spans in their existing OpenTelemetry backends, with sampling controls to limit volume. Teams should estimate ingestion and retention costs before December 1, since billing changes from the current model to volume-based.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Salesforce Deployments with OctopuspostThe Octopus Deploy blog describes a walkthrough for deploying a Salesforce sample application with Octopus Deploy and the Salesforce CLI (sf). It covers storing an SFDX auth URL as a sensitive variable, running a script step in a container built from a Dockerfile that installs the CLI, and running sf project deploy start against a target org.platform teamsA platform team that runs Salesforce deployments can use a pattern of a containerized execution step with the sf CLI and an auth URL secret in Octopus. The post is a tutorial on one approach and does not announce any change to Salesforce or Octopus tooling.Octopus Deploy Blog ↗Octopus Deploy Salesforce CLI Salesforce Platformwritten by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

2026-10-0922 days ago

InfoQ: HashiCorp Relased Terraform Google Cloud Provider 8.0 in General AvailabilitypostHashiCorp has announced general availability of version 8.0 of the Terraform provider for Google Cloud. The major release changes the default load balancing for two Compute Engine resources and removes resources tied to retired Google Cloud services.platform teamsPlatform teams using this provider should review configurations for the two Compute Engine resources whose default load balancing changed, and remove or migrate any usage of resources for retired Google Cloud services before upgrading. The source does not name the specific resources or new defaults.InfoQ ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo Workflowsv4.1.5patchsecurity**************!!Argo Workflows v4.1.5 was published with two changes, one added and one other, and one of them is marked as breaking. The release notes in the source are condensed and do not name the specific changes, pointing readers to the upgrading guide and the project's changelog.platform teamsPlatform teams running Argo Workflows should read the upgrading guide before rolling out v4.1.5, since a breaking change is flagged. The source text does not say what the breaking change is.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Argo Workflowsv4.0.13patchsecurity*******!Argo Workflows v4.0.13 was released with two changes, one marked as breaking and one added feature. The release notes in the source do not describe the specific changes and point to the upgrading guide and GitHub issues for details.platform teamsPlatform teams running Argo Workflows should read the upgrading guide for the breaking change before upgrading. The source text does not name the affected behavior.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Power Platform Build Tools2.0.158patch

2026-10-0823 days ago

Power Platform Build Tools2.0.156patch

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

older entries

daily email

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

categoryall idp & portals ai agents on platform ci/cd observability supply chain cost & governance reports & dx data enterprise app platforms

showmajor only releases case studies postmortems include patches

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