You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Build WG will keep build configuration required for a release line for 6 months after the release goes End-of-Life, in case further build or test runs are required. After that the configuration will be removed.
Node.js 12 went End-of-Life in April so we're approaching the end of the 6 month period and in all likelihood we're not going to be building Node.js 12 again. I plan to start cleaning up really old CI infrastructure that we kept around for Node.js 12 that is no longer used.
Disable https://ci.nodejs.org/job/node-daily-v12.x-staging/. This has been running daily to give some indication that the builds still work. Replace this with a daily job for v14.x so we're testing the earliest infrastructure we need to keep running.
Identify and remove platforms from the CI that are no longer required for Node.js 14 onwards. This will help with things like Jenkins agents need newer Java (11+) #3030 where End-of-Life operating systems do not provide later versions of Java in their package repositories.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.
According to
README.md
in this repository:Node.js 12 went End-of-Life in April so we're approaching the end of the 6 month period and in all likelihood we're not going to be building Node.js 12 again. I plan to start cleaning up really old CI infrastructure that we kept around for Node.js 12 that is no longer used.
The text was updated successfully, but these errors were encountered: