Review summary: #4217

Change reviewed

This PR advances the embedded agent version in version/VERSION from 4.0.0-beta.13 to 4.0.0-beta.14. On main, that value is read into the Go version package, propagated into build metadata by .buildkite/steps/extract-agent-version-metadata.sh, and recognized as a prerelease by .buildkite/steps/upload-release-steps.sh, which selects the agent-release-beta pipeline after the normal build and test dependencies complete.

The branch contains exactly this one-line version change and is based directly on the current main commit (5d0452f96fb66b69cbc878b930834cca638a1d27). No linked Linear issue was present in the branch name, PR title, or PR description.

Evidence examined

• Read the complete PR diff and the full changed file.
• Inspected version/version.go and version/version_test.go to verify how the file is embedded and the accepted version syntax.
• Traced the value through .buildkite/steps/extract-agent-version-metadata.sh, .buildkite/pipeline.yml, and .buildkite/steps/upload-release-steps.sh to confirm that a beta version is marked as a prerelease and dispatches the beta release pipeline.
• Compared the change with the prior 4.0.0-beta.13 bump and its release PR.
• Checked recent GitHub releases and remote tags: v4.0.0-beta.13 is the current v4 beta release, while no v4.0.0-beta.14 tag exists yet.
• Confirmed the PR has the release label. The category-label check initially failed before the label was present, then reran successfully.
• Ran git diff --check successfully and independently validated that 4.0.0-beta.14 matches the format enforced by TestVersionIsValid.

The Go toolchain is not installed in this review environment, so go test ./version could not be run locally. The Buildkite Agent build was still pending through GitHub status when the review was submitted. Socket Security checks had passed. Direct Buildkite CLI inspection was unavailable because the supplied token could not access the organization, so no Buildkite job logs were examined.

Findings and verdict

No correctness, release-routing, compatibility, or formatting issues were found. The increment is sequential, valid, unique among existing tags, and follows the established beta-release path. No inline comments were posted.

The review was submitted as APPROVE: #4217 (review)

Trigger source: automatic.