Buildpack Versioning Decoupled from BOSH Release Versions

Products

• VMware Tanzu Application Service
• VMware Tanzu Application Service
• VMware Tanzu Application Service for VMs

Issue/Introduction

Buildpack versions listed in Tanzu Application Service (TAS) release notes may not match the versions displayed by the cf buildpacks CLI command

For example, in TAS v10.2.11 release notes, the version of go-offline-buildpack is 1.10.108

Bump go-offline-buildpack to version 1.10.108

but the output "cf buildpacks"  shows

position   name                     stack        enabled   locked   state   filename                                              lifecycle
.
.
.
6          go_buildpack             cflinuxfs4   true      false    READY   go_buildpack-cached-cflinuxfs4-v1.10.82.zip           buildpack

 

TAS release notes list the bosh release version, whereas "cf buildpacks" list the buildpack version.

Environment

TAS / ERT

Cause

BOSH releases and buildpacks were tightly coupled, meaning their versions were always identical but now have independent lifecycles. A BOSH release serves as a "wrapper" or distribution vehicle for the buildpacks. 

Resolution

At the beginning of each component list in every version's release notes, you will find a link to the component details, which specifies which buildpacks versions are included in that BOSH release version. E.g

10.2.11

Release Date: 05/19/2026

For component details, see the Component Release Notes for this patch.

Once you click in the Component Release Notes it will show the buildpacks included in the bosh release. E.g 

go-offline-buildpack

1.10.108

v1.10.108 Buildpacks provided by this bosh release: - go_buildpack-cached-cflinuxfs3-v1.10.82.zip - go_buildpack-cached-cflinuxfs4-v1.10.82.zip