I believe that yarn was used prior to NodeJS having a package-lock.json available. Now that it does, should we just use that instead of requiring yarn?
How This PR Solves The Issue
Removes the yarn.lock file
Adds the package-lock.json file and all the changes to the node_modules directory
Enforces minimum NodeJS version of 18+ (current LTS)
Bumps the version of @types/node to match the same NodeJS version (same change as #1)
Manual Testing Instructions
Clone the repo, run npm install do you get the same dependencies?
Automated Testing Overview
Should only need regression tests, so no need to add new ones.
The Issue
I believe that yarn was used prior to NodeJS having a package-lock.json available. Now that it does, should we just use that instead of requiring yarn?
How This PR Solves The Issue
yarn.lockfilepackage-lock.jsonfile and all the changes to thenode_modulesdirectoryManual Testing Instructions
Clone the repo, run
npm installdo you get the same dependencies?Automated Testing Overview
Should only need regression tests, so no need to add new ones.
Related Issue Link(s)
None
Release/Deployment Notes
None, only affects the action internals.