Skip to content

Fix packaging issues around subpath exports with node10 compatibility #1532

Fix packaging issues around subpath exports with node10 compatibility

Fix packaging issues around subpath exports with node10 compatibility #1532

Triggered via push December 28, 2023 15:35
Status Failure
Total duration 1m 5s
Artifacts

test.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
build (latest)
Process completed with exit code 1.
build (16.x)
Process completed with exit code 1.
build (20.x)
Process completed with exit code 1.
build (18.x)
The operation was canceled.
build (latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/