Skip to content

fix: correctly identify pnp if it Vitest was already resolved #213

fix: correctly identify pnp if it Vitest was already resolved

fix: correctly identify pnp if it Vitest was already resolved #213

Triggered via push October 21, 2024 13:29
Status Success
Total duration 2m 21s
Artifacts 1

ci.yml

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

Annotations

3 warnings
ci (macos-14, 20.x)
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/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (windows-latest, 20.x)
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/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "artifact". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
artifact
9.31 MB