Releasesby GlyphTrace propagation across triggered builds
Agent spans across your multi-pipeline workflows can now share a single OpenTelemetry trace without contacting Support to enable propagation. Buildkite automatically passes trace context from a parent build to builds it triggers. This also works for internal trigger chains without externally supplied trace context.
Also shipped Nov 2, 2026Buildkite in November 2026 →
Managed warehouse for MLflow (Beta)
Managed warehouse for MLflow is available in Beta, enabling users to view Unity Catalog traces in the MLflow UI without manually choosing a SQL warehouse.
Serving tuned Gemini 3.x models on global endpoints
Serving tuned Gemini 3.x models on global endpoints is available in General Availability (GA) . You can copy fine-tuned Gemini 3.x models to the global region using the Model Registry models:copy API, deploy them to global serving endpoints, and send inference requests directly to aiplatform.googleapis.com .
[Launched] Generally Available: Change from virtual network integration to a private endpoint capable network configuration in Azure Database for PostgreSQL flexible server
You now have greater flexibility in network design for Azure Database for PostgreSQL Flexible Server workloads. Now you can change existing VNet-integrated servers from delegated-subnet networking to a private endpoint-capable configuration, enabling secu
[Launched] Generally Available: Restart databases in Azure SQL DB via the Azure portal
You can now restart or fail over databases directly from the Azure portal, including single databases, Hyperscale databases, and databases in elastic pools, without writing scripts against the Rest API or contacting support. Learn more.
Lakehouse caching for cross-cloud data access is generally available (GA)
Lakehouse caching for cross-cloud data access is generally available (GA). Cross-cloud caching is disabled by default. You can opt in to caching on a Lakehouse federated catalog or a BigQuery cross-cloud connection to cache remote files in your Google Cloud region. This helps reduce cross-cloud egress costs and accelerate subsequent queries.
You can now monitor the performance, adoption, latency, and costs of your data agents and their conversations...
You can now monitor the performance, adoption, latency, and costs of your data agents and their conversations by using Google Cloud Observability in BigQuery. This feature is generally available (GA).
More from BuildkiteEvery Buildkite release →
Check out GitHub code without long-lived credentials on self-hosted agents
Self-hosted agents can now use temporary, read-only GitHub App tokens for repository checkout. This eliminates the need to distribute and rotate long-lived SSH keys or personal access tokens across your agent fleet.
A changelog post about the changelog menu
We’ve added a changelog menu to Buildkite. This changelog post is to let you know about the changelog menu, and is available in the changelog menu for that purpose. If you arrived at this changelog post through the changelog menu, you already know about the changelog menu.
See what's happening across your agents and queues
Buildkite has updated its queue pages to provide better visibility into agent capacity and job status. New charts allow teams to track agent and job activity over time to identify bottlenecks and manage capacity more effectively.
Manage Test Engine workflows with Terraform and the REST API
Users can now manage Test Engine workflows using the buildkite_test_suite_workflow Terraform resource or the REST API, enabling code-based configuration of monitors and actions.
Buildkite Cache is generally available
Buildkite Cache is now generally available, allowing jobs to reuse work such as dependency downloads or build commands. It is integrated into the Buildkite agent and supports custom cache keys and fallback limits.
Filter webhook job events by queue
Buildkite added cluster queue filtering to webhooks in Notification Services and the REST API, allowing job events (scheduled, started, finished, activated, exit status) to be restricted to selected queues.
Configure OpenTelemetry at the cluster level
You can now turn on OpenTelemetry tracing for every agent in a cluster with one setting. Choose an OpenTelemetry notification service in the cluster's settings. Each agent that registers in the cluster then exports traces to that service's endpoint, using its headers, with no OTLP configuration on the agent.
Inspect matrix jobs directly on the build canvas
Matrix steps previously appeared as a single node on the build canvas, with individual jobs shown in a separate panel. Now you can expand them in place to see each job's status and duration, and navigate directly to the job. Similar to group steps , failed matrix steps now start expanded and focus on failed jobs.