Data and AI releases

2,002 this month · 180 companies

Monitor billable active-user usage with the Buildkite API

UpdateNot yet verified

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.

SQLGovernancePricingObservabilityDeveloper tools

Read on buildkite.com

Also shipped Oct 5, 2026Buildkite in October 2026 →

Scheduled Search and Reporting is now generally available

New Relic is excited to share that Scheduled Search and Reporting is now generally available. Instead of manually re-running the same NRQL query to check on your data, Scheduled Search runs it for you, on whatever cadence you choose, and delivers the results straight to your inbox. What is Scheduled Search and Reporting?

GA
Source ↗

Lyria 3 music models for your app's AI features

Your app's AI features can now generate music with two Google models, from a text prompt or an image, with vocals or as an instrumental: Lyria 3 Clip Preview , for clips of about 30 seconds. Lyria 3 Pro Preview , for full tracks up to 184 seconds. Ask Lovable to use either model in your app, or describe what you want and let Lovable pick.

Preview
Source ↗

More from BuildkiteEvery Buildkite release →

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.

Update
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗

Retry jobs with narrower API token permissions

Retry automation no longer needs the broader write_builds REST API scope. The new retry_builds scope allows a token to retry failed jobs in existing builds or individual eligible jobs, without granting access to the create-build or rebuild endpoints. When creating or editing an API access token, select Build Retries ( retry_builds ).

Update
Source ↗