Skip to content
CI-CD

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

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 #417

Triggered via pull request September 14, 2025 00:33
@mcousmcous
synchronize #232
fix/npm-10-11
Status Success
Total duration 2m 7s
Artifacts 1

ci-cd.yaml

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

Annotations

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

Artifacts

Produced during runtime
Name Size Digest
publish-artifact
66.1 KB
sha256:d8294b81f9d8fb9dfd7ab79ef6047f3cb338e5ca75e2bdd98baa455f260e7810