Buildpack versions in TAS release note decoupling from OSS

Products

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

Issue/Introduction

Customer is confusing that Buildpack versions in TAS release notes don't line up with cf buildpacks.

For example, refer to TAS v6.0.13 release note, the version of go-offline-buildpack is 1.10.43.

 

Actually, the version num 1.10.43 here is the go_buildpack BOSH release version. As you can see in the screenshot below, two buildpacks go_buildpack-cached-cflinuxfs3-v1.10.29.zip and go_buildpack-cached-cflinuxfs4-v1.10.29.zip are included in this bosh release.

Note: This screen-shot is the go-offline-buildpack-release Release page within Broadcom github. External won't have access to this repo.

 

Meanwhile, from "cf buildpacks" output, we can see the cflinuxfs4 stack of go_buildpack is using go_buildpack-cached-cflinuxfs4-v1.10.29.zip.

7          go_buildpack             cflinuxfs4   true      false    READY   go_buildpack-cached-cflinuxfs4-v1.10.29.zip

The version num 1.10.29 here is the OSS go-buildpack version, you can find the info in the OSS release note.

Resolution

The release notes will be incorporated into TAS release notes starting with the upcoming releases. We won't rely on OSS at all. 

Our Product team plan to tackle the official docs to clarify this decoupling from OSS. And we expect that the next TAS patch releases will contain notes for all buildpack BOSH releases from the TAS releases. These BOSH release notes include the corresponding release notes for the buildpacks. 

Attached TAS Buildpacks release notes PDF file for reference. The file contains the release notes for the buildpack BOSH releases from the last 4 TAS patch releases. 

Until our Product Team publish notes for all buildpacks shipped outside of BOSH releases, please ask Support for the release notes and we can provide them.