From 2d384a77704c502a1fbc00748e503807fa5e0529 Mon Sep 17 00:00:00 2001 From: Kevin Green Date: Thu, 5 Nov 2026 14:46:05 -0500 Subject: [PATCH 1/2] docs: clarify release versioning guidance --- AGENTS.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 2315542..3631d02 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -134,13 +134,17 @@ GKE deletion protection must exist on the source pool before hardware replacemen - Do not describe PDBs as an unconditional zero-downtime guarantee. - Test role isolation, API compatibility, and cross-cloud behavior after PDB changes. -### Version Numbers +### Release Versioning -Chart version numbers are semantically meaningful for the upgrade path: -- Minor versions (e.g., 5.2.0) are additive, non-breaking chart features -- Major versions (e.g., 6.0.0) carry Data Plane image tag changes that affect runtime behavior +Choose the chart version bump based on changes to both the chart and the Braintrust release it deploys: -Do not bump `Chart.yaml` version without explicit coordination - version numbers determine customer upgrade sequencing. +- **Major:** Increment the major version for breaking changes in either the chart or the Braintrust release. +- **Minor:** Increment the minor version for non-breaking changes in either the chart or the Braintrust release, unless the release contains only documentation changes and backward-compatible bug fixes. +- **Patch:** Increment the patch version when the release contains only documentation changes and backward-compatible bug fixes. + +Use the highest applicable version bump across all changes in the release. Reset the minor and patch versions to zero when incrementing the major version, and reset the patch version to zero when incrementing the minor version. + +Do not bump the version in `braintrust/Chart.yaml` without explicit coordination; version numbers determine customer upgrade sequencing. ## Review guidelines From c2ede1dccbbead027d1f2d3d7e4cb48b6927da82 Mon Sep 17 00:00:00 2001 From: Kevin Green Date: Thu, 5 Nov 2026 16:00:41 -0500 Subject: [PATCH 2/2] docs: classify removal of top-level inputs as breaking --- AGENTS.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 3631d02..51906fa 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -142,6 +142,8 @@ Choose the chart version bump based on changes to both the chart and the Braintr - **Minor:** Increment the minor version for non-breaking changes in either the chart or the Braintrust release, unless the release contains only documentation changes and backward-compatible bug fixes. - **Patch:** Increment the patch version when the release contains only documentation changes and backward-compatible bug fixes. +Removing a top-level chart input (value) is a breaking change and requires a major version bump. + Use the highest applicable version bump across all changes in the release. Reset the minor and patch versions to zero when incrementing the major version, and reset the patch version to zero when incrementing the minor version. Do not bump the version in `braintrust/Chart.yaml` without explicit coordination; version numbers determine customer upgrade sequencing.