Platform Changelog

feedbefore 2026-10-14patches hidden unless security or breaking

2026-10-1318 days ago

InfoQ: Backstage 1.55 Adds Scaffolder Task Recovery and Removes Deprecated Catalog APIspostBackstage 1.55 adds opt-in recovery for Software Template tasks, allowing crashed or timed-out runs to resume from the last completed step. The release also includes breaking changes to the catalog, search and TechDocs. The source points readers to the current 1.55.3 patch.platform teamsPlatform teams running Backstage scaffolder templates can opt into resuming failed runs instead of restarting them. They should review catalog, search and TechDocs configuration before upgrading because of the breaking changes.InfoQ ↗BackstageeditorCorrection 2026-10-20: this was listed as a Backstage 1.55 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

ServiceNow SDK4.13.xminor++**SDK 4.13.x Patch NotesServiceNow released SDK 4.13.x patch changes. The release adds table support for db_object_id in bootstrap and for configuration_access, and adds a protectionPolicy option for sys_security_acl_role. It fixes an OAuth CSRF issue by restoring cookie replay and binding CSRF lookup to the exact session, and it also fixes a now-ux-globals Array.from polyfill requirement and a TypeScript error during UI type-checking.platform teamsPlatform teams that use the ServiceNow SDK should pick up the OAuth CSRF fix, which is a security fix in the SDK itself. Teams managing ACL rules can use the new protectionPolicy option on sys_security_acl_role, and telemetry events no longer have person profile processing applied.written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

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

Amazon ECS adds LiveTaskCount and removes the charge for RunningTaskCount metricannouncementAmazon ECS added a LiveTaskCount service metric that reports tasks in ACTIVATING, RUNNING, and DEACTIVATING states, including tasks draining during scale-in. The metric is available at no charge and does not require CloudWatch Container Insights. The existing RunningTaskCount metric in Container Insights also no longer incurs a charge, effective October 1, 2026.platform teamsPlatform teams running ECS can use LiveTaskCount for autoscaling and capacity planning without paying for Container Insights, and can drop charges previously paid for RunningTaskCount. RunningTaskCount still only counts tasks whose current and desired state are both RUNNING, so it is not a substitute for LiveTaskCount in scale-in logic.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Amazon Bedrock AgentCore Memory now supports configurable time-to-live for long-term memoryannouncementAmazon Bedrock AgentCore Memory now supports a configurable time-to-live on long-term memory records, so records are deleted automatically after a retention period the user sets. Previously long-term memory records did not expire by default. TTL can be set on the resource or on specific records, and changing it requires the new bedrock-agentcore:UpdateMemoryRecordExpirySpecification permission. The feature is available in all AWS Regions where AgentCore Memory is supported.platform teamsPlatform teams can set retention rules to meet data-retention requirements and limit storage growth from agent memory. Because changing TTL needs its own IAM permission, access to retention settings can be granted separately from general memory access.What's New with AWS ↗written 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

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

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

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

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

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

Announcing consumption-based pricing for short-term memory in Amazon Bedrock AgentCoreannouncementAmazon Bedrock AgentCore now bills short-term memory by data ingested, retrieved, and stored, replacing the previous flat rate per event. Ingestion is priced at $1.00 per GB, retrieval at $0.20 per GB, and storage at $0.10 per GB-month, with a 12 KB minimum and 64 KB maximum billable size per event for ingestion and retrieval. AWS says most workloads see lower costs, and long-term memory pricing is unchanged.platform teamsTeams running agents on AgentCore memory need to re-estimate costs, since the billing unit changed from events to data volume and small-payload workloads are the ones AWS says benefit most. Setting a shorter TTL on memory resources is the stated lever for controlling storage spend.What's New with AWS ↗written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

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

CNCF: From zero to agent builder: Running kagent on your laptoppostThe author walks through running kagent, a CNCF Sandbox project, on a local kind cluster with a local Ollama model. An agent-builder agent is defined as a Kubernetes Agent resource that can only apply Agent manifests, with a three-tool allowlist and human approval before each apply. The post notes that security settings such as default unsecure auth and a built-in PostgreSQL password are deliberately left out of this laptop setup.platform teamsA platform team evaluating agents-as-resources can see how RBAC limited to agents.kagent.dev, a tool allowlist and requireApproval gate constrain what a generated agent can do. The post states the laptop setup is not suitable for a shared cluster without the security settings it omits.CNCF Blog ↗Kubernetes MCP Server kagentwritten 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

InfoQ: Foresight AI Brings Gremlin Agents to Reliability EngineeringpostGremlin has announced general availability of Foresight AI, an agentic product. According to the source, it analyzes services for potential failures, recommends changes, and reruns tests to check whether a fix works.platform teamsPlatform teams evaluating AI-driven reliability tooling can now consider Foresight AI as a GA option, but the source gives no details on integrations, pricing, or how it connects to existing pipelines or clusters.InfoQ ↗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