Weekly wrap: September 27 – October 3, 2026
What shipped this week Between September 27 and October 3, 2026, we published 4 changelog entries and 35 releases across 13 public repos. Three things run through them: more control and predictability for platform teams, fewer gaps for teams moving off GitHub Actions, and more of the platform agents can drive directly. Tightened how secrets are handled.
Also shipped Oct 2, 2026Buildkite in October 2026 →
PagerDuty Advance team-level permissions now Generally Available
Building on team-level permissions, Account Admins can now choose which AI agents are enabled for each team. This further empowers teams to roll out AI adoption with confidence. Learn more.
AI Gateway, Web Search API - Introducing Web Search API
Web Search API is now available in beta. Web Search API lets your AI agents and applications search the Internet and ground their responses in live information, instead of guessing URLs or relying on a model's training cutoff. At launch, you can choose between three search providers: Ceramic.ai, Exa, and Linkup .
KV - Workers KV namespace jurisdictions are now generally available
Jurisdictions for Workers KV namespaces are now generally available. When you create a namespace, you can set a jurisdiction to make sure the namespace's data is only durably stored within that region. Jurisdictions can help you comply with data localization regulations such as GDPR or FedRAMP. Supported jurisdictions are eu , us , and fedramp .
Repository security advisory comments API in public preview
You can now read, add, and edit comments on repository security advisories using the REST API, including advisories created from private vulnerability reports. Until now, the discussion on an advisory was only reachable in the web UI, even though it often holds the most useful triage context on a vulnerability report.
Note : Your clusters might not have these versions available
Note : Your clusters might not have these versions available. Rollouts are already in progress when we publish the release notes, and can take multiple days to complete across all Google Cloud zones. Version 1.36.4-gke.1495000 is now the default version for cluster creation in the Rapid channel.
You can use Vertical Pod Autoscaler (VPA) with Horizontal Pod Autoscaler (HPA) to automatically optimize...
You can use Vertical Pod Autoscaler (VPA) with Horizontal Pod Autoscaler (HPA) to automatically optimize container CPU requests for workloads that scale replicas based on CPU utilization. This feature is available in Public Preview on clusters running GKE version 1.36.3-gke.1630000 or later. For more information, see Rightsize HPA workloads with VPA .
More from BuildkiteEvery Buildkite release →
Get notified about new macOS base image releases
You can now subscribe to RSS feeds for macOS base image releases on Buildkite hosted agents, making it easier to keep up with changes to your build environments. For updates to stable base images used in production, add the stable RSS feed to your preferred RSS reader.
Choose the organization for each Remote MCP Server connection
If you belong to more than one Buildkite organization, you can now choose which one each Remote MCP Server connection uses. Add the organization's slug to the server URL: https://mcp.buildkite.com/mcp?organization=your-organization When your MCP client asks you to authorize, that organization is already selected.
Buildkite agent version support policy
From 1 January 2027 , each minor release line of the Buildkite agent will be supported for one year from its first stable release . The final three months are a deprecation period: agents remain supported, with warnings encouraging you to upgrade. Installing an agent or updating to a newer patch doesn't restart that window.
Monitor billable active-user usage with the Buildkite API
You can now monitor your organization's billable active-user usage programmatically and compare it with your contracted allowance. Send the count to observability tools such as Datadog to track usage over time, or include it in internal license, billing, and compliance reporting.
Manage secrets from pipeline settings
If you can edit a pipeline and manage its associated cluster, you can now create and manage secrets directly from Pipeline settings → Secrets . Pipeline secrets are cluster secrets with access restricted to the current pipeline.
Buildkite MCP Server updates
Your agent can now do more of the work between a failed build and a green one. Here are the latest tool updates for the Buildkite MCP Server . See what changed since the last green build When a build fails, one of the first questions is what's different from the last one that passed. compare_builds answers it in a single call.
Shipped this week
Buildkite shipped 40 releases. Three themes. Diagnosis. Agents put blocking failures first and retry infrastructure failures. Desktop alerts and log summaries are more reliable. Compatibility. GitHub Actions workflows get hashFiles() in composite actions, Windows checkout fixes, and retries for temporary token failures. Control.
See the important parts of job logs first
Job logs on the new build page are easier to scan now that Buildkite folds de-emphasized system groups into compact rows by default. Command output and the groups you usually need remain visible, while setup and other supporting output take up less space. Select a folded row to reveal just that section in place.