Users require a specific Node version when using Tanzu Node.js Buildpack to build applications in TAP.
If the specific Node version is not supported in the installed Tanzu Node.js Buildpack, then build errors similar to the following might be observed.
failed to satisfy "node" dependency version constraint "SOME-VERSION": no compatible versions on "io.buildpacks.stacks.jammy" stack. Supported versions are: [VERSION1, VERSION2, VERSION3, ...]
ERROR: failed to build: exit status 1
To successfully use a specific Node version to build applications in TAP, users might need to perform the following:
1. Confirm the specific Node version is supported in a Tanzu Node.js Buildpack by checking the release notes. For instance, if a user has a requirement to use Node v22.22.0, then they might need to use the Tanzu Node.js Buildpack v4.9, per the Tanzu Node.js Buildpack v4.9 release note.
2. Validate/generate a valid registry token. Refer to Registry Software Download functionality enhancements within the Broadcom Support Portal. Then log in to the tanzu-build.packages.broadcom.com using the token you saved.
$ docker login tanzu-build.packages.broadcom.com
Username: [email protected]
Password: <TOKEN-SAVED>
Login Succeeded
3. Log in to your registry.
$ docker login REGISTRY_HOST
Username <USER-NAME>
Password: <PASSWORD>
Login Succeeded
4. Refer to the Manual dependency updates to manually upgrade the clusterbuildpack for nodejs.
* If users want to use the Tanzu Node.js Buildpack v4.9.2, then they need to pull and relocate the "tanzu-build.packages.broadcom.com/tanzu-nodejs-buildpack/nodejs:4.9.2" to their registry.
5. Once the new ClusterBuildpack is deployed, the Tanzu Build Service will the latest available version to run builds. All images that were built with older versions of the buildpack will now be rebuilt.