Skip to content

fix vscode-extension bundle step adding correct jspi subfolder #725

fix vscode-extension bundle step adding correct jspi subfolder

fix vscode-extension bundle step adding correct jspi subfolder #725

Triggered via pull request October 17, 2024 06:20
Status Success
Total duration 1m 42s
Artifacts

ci.yml

on: pull_request
Lint and typecheck
43s
Lint and typecheck
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Lint and typecheck
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Lint and typecheck
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/