Skip to content
.github/workflows/publish.yml

ci: fix npm publish #3

Sign in to view logs

ci: fix npm publish

ci: fix npm publish #3

Triggered via push November 9, 2023 11:34
@DiscreteTomDiscreteTom
pushed 0836b23
main
Status Failure
Total duration 42s
Artifacts –

publish.yml

on: push
publish
34s
publish
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
publish
Error: Unable to publish @discretetom/r-compose v0.1.0 to NPM. npm publish --access restricted 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:96: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 --access restricted 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:513:28) at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)
publish
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/