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
What happened:
Node.js 12 runtime has hit its End-Of-Life. This means it is no longer being maintained and does not receive critical bug fixes and security updates. The Active LTS is Node.js 16, so we should update our packages that specify the engine
What should have happened:
We should make sure our microservices runs as expected with Node.js 16. Most of our Dockerfiles already use node:16 or node:lts as its base so I don't think we need to make any changes there
Our CI tests also do not rely on Node.js 12 so we're good on that front as well.
How to reproduce it (as precise as possible):
Anything else we need to know?:
Environment:
OS:
Browser:
The text was updated successfully, but these errors were encountered:
What happened:
Node.js 12 runtime has hit its End-Of-Life. This means it is no longer being maintained and does not receive critical bug fixes and security updates. The Active LTS is Node.js 16, so we should update our packages that specify the engine
Node.js 14 is in Maintenance, so we could update the following package.json as well:
telescope/package.json
Line 89 in 06100a7
telescope/src/api/parser/package.json
Line 40 in 06100a7
telescope/src/web/docusaurus/package.json
Line 63 in 06100a7
What should have happened:
We should make sure our microservices runs as expected with Node.js 16. Most of our Dockerfiles already use
node:16
ornode:lts
as its base so I don't think we need to make any changes thereOur CI tests also do not rely on Node.js 12 so we're good on that front as well.
How to reproduce it (as precise as possible):
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: