-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate dev environment and workflows to node16 #1278
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -219,6 +219,13 @@ export class DownloadHttpClient { | |||
fileDownloadPath: string | |||
): Promise<void> => { | |||
destinationStream.close() | |||
// await until file is created at downloadpath; node15 and up fs.createWriteStream had not created a file yet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Node16 regression:
The single code change we need in node16: awaiting destinationStream.on('close',
ensures that the file has been created so we can rmFile
delete it on line 229.
@@ -24,10 +24,10 @@ jobs: | |||
- name: Checkout | |||
uses: actions/checkout@v2 | |||
|
|||
- name: Set Node.js 12.x | |||
- name: Set Node.js 16.x | |||
uses: actions/setup-node@v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setup-node can also be updated to v3?
…rl/node-v16-and-toolkit-fixes
Releases can be made or PRs can be merged even if the workflow is failing
To fix critical audit vulnerabilities, we needed to upgrade (dev) dependencies to versions that are no longer compatible with our current workflows using node12.
Node12 and node16 are the versions used by the runner. With Node12 being deprecated, we've targeted node16 for this project as well. It makes sense to keep in sync with the runner, as most eventual applications of
actions/tookit
's packages end up being executed by the runner.Also contains numerous fixes to satisfy
audit-all