What is the lifecycle for binaries distributed with the Node.js Buildpack
Article ID: 298053
Updated On:
Products
Issue/Introduction
Environment
Resolution
VMware only bundles supported versions of Node.js with its buildpack. If an upstream version of Node.js becomes unsupported, we can no longer include that version of Node.js with the buildpack. This is because it will not be receiving security updates or updates of any kind and thus it should no longer be used.
The following information comes from the Node.js site. Refer to the site for the most up-to-date information.
"Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases."
VMware Tanzu Support recommends that you monitor the lifecycle of Node.js versions being used by your applications so that you have adequate time to upgrade applications.
If you need additional time to migrate, you may run cf create-buildpack and create a new buildpack using the latest version of the Node.js buildpack that includes the version of Node.js that you require. You can see which versions of Node.js are shipped with a buildpack on this site or by looking at the release notes on GitHub. You can then have application developers that require the old version use the specific buildpack that you created for their needs.
VMware Support recommends that you do not lock or downgrade the system buildpacks that ship with Tanzu Application Service for VMs. This will impact all applications that run using the system buildpack, including system applications, and will prevent them from receiving security updates.
Checklist:
VMware only bundles supported versions of Node.js with its buildpack. If an upstream version of Node.js becomes unsupported, we can no longer include that version of Node.js with the buildpack. This is because it will not be receiving security updates or updates of any kind and thus it should no longer be used.
The following information comes from the Node.js site. Refer to the site for the most up-to-date information.
"Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases."
If you need additional time to migrate, you may run cf create-buildpack and create a new buildpack using the latest version of the Node.js buildpack that includes the version of Node.js that you require. You can see which versions of Node.js are shipped with a buildpack on this site or by looking at the release notes on Github. You can then have application developers that require the old version use the specific buildpack that you created for their needs.
VMware Support recommends that you do not lock or downgrade the system buildpacks that ship with Tanzu Application Service for VMs. This will impact all applications that run using the system buildpack, including system applications, and will prevent them from receiving security updates.
Feedback
