Upgrade build-lib version in release pipeline to accomodate new changes #1659
Triggered via pull request
September 10, 2024 21:51
gaiksaya
Status
Success
Total duration
1m 27s
Artifacts
–
Annotations
4 warnings
|
test (18.x, 2.0, 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
test (18.x, 1.x, 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
test (18.x, 2.x, 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
test (18.x, main, 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|