fix: update dry-run and publish conflict logic for npm>=10 #414
Triggered via pull request
September 13, 2025 19:21
mcous
Status
Failure
Total duration
1m 24s
Artifacts
–
ci-cd.yaml
on: pull_request
Matrix: test
Build and lint
17s
Code Coverage
5s
Matrix: e2e
Publish
0s
Annotations
1 error and 5 notices
|
Build and lint
Process completed with exit code 1.
|
|
Unit tests / Node.js 20 / windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Unit tests / Node.js 18 / windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Unit tests / Node.js 22 / windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Unit tests / Node.js 16 / windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Unit tests / Node.js 24 / windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|