Understanding Terraform Template Versions vs Data Plane Versions

Issue

Users deploying Braintrust via Terraform may see configuration references such as:

ref = "v4.0.1"

At the same time, Braintrust documentation or support may reference versions such as:

1.1.29

This can cause confusion about which version controls the actual runtime behavior.

Cause

These version numbers refer to different components:

The Terraform template version determines which service versions get deployed.

Each Terraform release contains a VERSIONS.json file that pins the internal service versions used during deployment.

For example:

terraform template v4.0.1
→ references services version 1.1.27

Because of this mapping, upgrading Terraform templates is how the underlying Braintrust services are upgraded.

As an example, here you can see the current version of the VERSIONS.json file for Brainstore.

This version is then passed to the template through the brainstore_release_version variable

Notes

• Terraform template versions and service versions will not match numerically.

• Release notes for service updates can be found in the Braintrust changelog

  • Data plane changelog

  • Product changelog