Give agents only the access they need
Buildkite has released two opt-in security controls for agent tokens: token permissions and queue scopes. Agents connecting with restricted tokens can only use the capabilities those tokens allow, such as uploading steps or reading secrets. Scoped agent tokens let your platform team give different parts of your infrastructure only the permissions they need.
Also shipped Nov 13, 2026Buildkite in November 2026 →
AI Function task support in Declarative Automation Bundles (Beta)
Support for AI Function tasks in Declarative Automation Bundles is now in Beta . See AI Function task .
Many-to-many relationships in semantic views (Preview)
Many-to-many relationships are now in preview for semantic views. You can model a many-to-many relationship between two logical tables in either of the following ways:
Metabase 65.4
Upgrading > Before you upgrade, back up your Metabase application database! Check out our upgrading instructions. Get the most out of Metabase. Learn more about advanced features, managed cloud, and first-class support.
Metabase 64.6
Upgrading > Before you upgrade, back up your Metabase application database! Check out our upgrading instructions. Get the most out of Metabase. Learn more about advanced features, managed cloud, and first-class support.
Metabase 58.40
Upgrading > Before you upgrade, back up your Metabase application database! Check out our upgrading instructions. Get the most out of Metabase. Learn more about advanced features, managed cloud, and first-class support.
Metabase 58.39
Upgrading > Before you upgrade, back up your Metabase application database! Check out our upgrading instructions. Get the most out of Metabase. Learn more about advanced features, managed cloud, and first-class support.
More from BuildkiteEvery Buildkite release →
Set agent token expiry on the dashboard
Buildkite added support for configuring agent token expiry durations and custom target dates directly within the Buildkite dashboard.
Choose read-only access when connecting Buildkite MCP
Users can now select between Read-only and Full access when connecting an AI agent to Buildkite via MCP. Read-only access allows agents to inspect builds and logs without the ability to trigger changes.
Hosted agents are now available on Windows and Linux ARM64
Buildkite now offers hosted agents for Windows and Linux ARM64. Windows support is in public preview, while Linux ARM64 is generally available, allowing users to run builds without managing their own infrastructure.
Cancel in-progress jobs with concurrency groups
For finer control over concurrency group queues, cancel_in_progress: true lets a job waiting for a concurrency slot cancel blocking jobs in the same group: steps: command: "./real-device-tests.sh" concurrency: limit: 1 group: "my-pipeline/real-device-tests/${BUILDKITE_BRANCH}" cancel_in_progress: true The new concurrency map syntax keeps your limit, group...
More control and visibility for artifacts
Organization admins can now configure shorter retention periods for Buildkite-hosted artifacts. The usage page has been updated to provide clearer tracking of storage and download limits.
Revoke OAuth access for your organization
Organization administrators can now revoke all existing OAuth access and refresh tokens directly from the security settings page.
Require SSO sign-in again for your organization
Organization administrators can now revoke all active SSO sessions for their organization directly from the security settings during a suspected incident.
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.