Skip to content

mol_compare_deep

mol_compare_deep #1977

Triggered via schedule November 6, 2024 07:20
Status Failure
Total duration 2m 14s
Artifacts

mol_compare_deep.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
build
Error: Unable to publish mol_compare_deep v0.0.1 to NPM. npm publish exited with a status of 1. at Object.publish (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/npm.ts:112:13) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Object.npmPublish (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/npm-publish.ts:23:5) at main (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/action/index.ts:28:19) ProcessError: npm publish exited with a status of 1. at normalizeResult (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/node_modules/@jsdevtools/ez-spawn/lib/normalize-result.js:31:1) at ChildProcess.<anonymous> (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/node_modules/@jsdevtools/ez-spawn/lib/async.js:79:1) at ChildProcess.emit (node:events:519:28) at Process.ChildProcess._handle.onexit (node:internal/child_process:294:12)
build
The following actions uses node12 which is deprecated and will be forced to run on node16: hyoo-ru/mam_build@master2, JS-DevTools/npm-publish@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: hyoo-ru/mam_build@master2, JS-DevTools/npm-publish@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/