Verify Tanzu Build Service Automatic dependency update is updating patch releases

Products

• VMware Tanzu Application Platform
• VMware Tanzu Build Service

Issue/Introduction

After following the documentation to enable automatic updates you may wonder if it is working as expected.  This KB will describe how to verify automatic updates are working.

 

 

Resolution

The first thing to check is you set "VERSION-CONSTRAINT" in step 4 when you added the PackageRepository  tbs-dependencies-package-repository.  it should be something like "1.12.x" if you have tap version 1.12 installed. This will limit the patch updates associated to the 1.12 release line. 

  spec:
    fetch:
      imgpkgBundle:
        image: tanzu-build.packages.broadcom.com/build-service-dependency-updater/package-repo
        tagSelection:
          semver:
            constraints: "VERSION-CONSTRAINT"

To check what you have set for your package repository you can get the yaml using this command

 kubelet get PackageRepository tbs-dependencies-package-repository -n tap-install -o yaml

apiVersion: packaging.carvel.dev/v1alpha1
kind: PackageRepository
metadata:
  finalizers:
  - finalizers.packagerepository.packaging.carvel.dev/delete
  name: tbs-dependencies-package-repository
  namespace: tap-install
spec:
  fetch:
    imgpkgBundle:
      image: tanzu-build.packages.broadcom.com/build-service-dependency-updater/package-repo
      tagSelection:
        semver:
          constraints: 1.12.x. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

 

Given you have the spec.fetch.imgpkgBundle.tagSeclection.semver.constraints version set correctly you can check if packages are being updated with this command.  As an example we will check the base Jammy Stack using the release notes https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-buildpacks/services/buildpacks/base-stack-ubuntu-2204-release-notes.html as reference.  If our base stack version is 0.1.x then we should expect to see the latest patch release referenced in the release notes in the output below.  As per below we can see the initial package installed was version 0.1.141.  Version 0.1.148 was released on June 10Th 2025 and was automatically updated. 

 kubectl get packages -n tap-install   | egrep "base-jammy-stack|AGE"


NAME                                                                  PACKAGEMETADATA NAME                                  VERSION                     AGE
base-jammy-stack-lite.buildpacks.tanzu.vmware.com.0.1.141             base-jammy-stack-lite.buildpacks.tanzu.vmware.com     0.1.141                     525h59m44s
base-jammy-stack-lite.buildpacks.tanzu.vmware.com.0.1.148             base-jammy-stack-lite.buildpacks.tanzu.vmware.com     0.1.148                     1h33m33s
base-jammy-stack.buildpacks.tanzu.vmware.com.0.1.141                  base-jammy-stack.buildpacks.tanzu.vmware.com          0.1.141                     357h36m27s
base-jammy-stack.buildpacks.tanzu.vmware.com.0.1.148                  base-jammy-stack.buildpacks.tanzu.vmware.com          0.1.148                     1h33m33s

 

 

If for some reason automatic dependency updater is not patching releases then please open a ticket with support and reference this KB.