v6.58.4 (2026-03-18)
Tip
🎉 ✨ Streaming job dispatch (Public Preview): Buildkite Agent version 3.120.0 adds opt-in support for a new streaming connection between agents and Buildkite, significantly reducing job acceptance latency for self-hosted agents. To try it, set AgentEndpoint parameter in CloudFormation to https://agent-edge.buildkite.com/v3.
This capability is in public preview and will become the default in a future release. If you have any feedback or run into issues, please reach out to support@buildkite.com.
Changed
- Update buildkite-agent to v3.120.1 #1739 (renovate[bot])
Internal
Agent Changelog
v3.120.1 (2026-03-17)
[!TIP]
🎉 ✨ Streaming job dispatch (Public Preview): Version 3.120.0 adds opt-in support for a new streaming connection between agents and Buildkite, significantly reducing job acceptance latency for self-hosted agents. To try it, start your agent with--endpoint https://agent-edge.buildkite.com/v3, for example:buildkite-agent start --endpoint https://agent-edge.buildkite.com/v3You may alternatively use the environment variable
BUILDKITE_AGENT_ENDPOINTor edit yourbuildkite-agent.cfgto containendpoint=https://agent-edge.buildkite.com/v3.This capability is in public preview and will become the default in a future release. If you have any feedback or run into issues, please reach out to support@buildkite.com.
Fixed
- Adds
API_KEYvalues to the redacted list #3761 (@mcncl) - fix: Support []string fields in ReadFromEnvironment #3767 (@DrJosh9000)
Internal
Dependency updates
- build(deps): bump the container-images group across 1 directory with 2 updates #3764 (@dependabot[bot])
- build(deps): bump the container-images group across 5 directories with 2 updates #3766 (@dependabot[bot])
- build(deps): bump the golang-x group with 3 updates #3762 (@dependabot[bot])
- build(deps): bump the cloud-providers group with 8 updates #3765 (@dependabot[bot])
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.58.4/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):