Releasesby IbisRetry jobs with narrower API token permissions
UpdatetodayUnverifiedAdded Oct 13, 2026
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 ).
Topics: Streaming, Security, Data integration, Developer tools
More Buildkite releases
Every Buildkite releaseShipped 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.
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.
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.
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.
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.
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.
Also shipped on Oct 13, 2026
Buildkite in October 2026What's included:
- Three training methods: Supervised fine-tuning (SFT) , direct preference optimization (DPO) , and reinforcement learning with group relative policy optimization (GRPO) . Each method trains a low-rank adapter (LoRA) or the full model weights. Custom loss functions : Train with any objective you compute in PyTorch from the model's log-probabilities.
LangSmith SDK 0.14.8
- fix(py): send session_id on RunTree.patch fix: keep punctuation out of freeze guard links chore(deps): bump source-map-js from 1.2.1 to 1.2.2 in /js fix(py): make the /runs/multipart 404 fallback to /runs/batch reachable feat(sandbox): accept any JOSE asymmetric algorithm chosen by the JWKS key (python) feat(sandbox): customer-managed KMS keys for S3...
Post-training
Post-training lets you write your own training loop and run it against Together AI GPUs. Your code builds each batch and chooses the loss function and learning rate, while the GPUs you provision run the forward and backward passes, optimizer steps, and sampling. It bills per GPU-minute.
2026-10-13 updates
See what changed in Sourcegraph.
truss 0.18.34
- Add include and exclude filters to BDN mount configuration feat: Forward egress_restrictions for BIS and warn about missing hosts Release 0.18.34
arize-phoenix-sqlean: v0.2.0
0.2.0 (2026-10-12) Features phoenix-sqlean: bundle SQLite 3.54.0 and support Python 3.15 (fff25bc)