Skip to content
CI-CD

fix: update dry-run and publish conflict logic for npm>=10 #413

Sign in to view logs

fix: update dry-run and publish conflict logic for npm>=10

fix: update dry-run and publish conflict logic for npm>=10 #413

Triggered via pull request September 13, 2025 19:14
@mcousmcous
opened #232
fix/npm-10-11
Status Success
Total duration 1m 37s
Artifacts 1

ci-cd.yaml

on: pull_request
Matrix: test
Build and lint
24s
Build and lint
Code Coverage
6s
Code Coverage
Matrix: e2e
Publish
0s
Publish
Fit to window
Zoom out
Zoom in

Annotations

5 notices
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 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 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
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

Artifacts

Produced during runtime
Name Size Digest
publish-artifact
66 KB
sha256:770f29fc2375ea8f0b01d0947c22f5e057378f284fe21a1a5383b1f2dfbf09f6