Add a regular check whether Charlie is using the most recent Node LTS
mgwalker opened this issue · comments
We have a nightly action that restages Charlie on cloud.gov, so it should always be using the latest version of its intended LTS (currently 16) that is in the most recent buildpack on cloud.gov, but we don't have any automations to let us know when a new LTS is available. They usually release in October of each year. We should have an automation that checks our package.json engines property and compares that to the current LTS major version periodically, so it can let us know if we're behind.