Skip to content

NPM Publish

NPM Publish #76

Triggered via workflow run March 15, 2026 00:24
@DavidArayanDavidArayan
completed 8aaf378
Status Failure
Total duration 28s
Artifacts

publish.yml

on: workflow_run
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
publish
NpmCallError: Call to "npm publish" exited with non-zero exit code 1 npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access npm error code E404 npm error 404 Not Found - PUT https://registry.npmjs.org/@astrumforge%2fbvx-kit - Not found npm error 404 npm error 404 '@astrumforge/bvx-kit@1.44.0' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-15T00_24_41_737Z-debug-0.log
publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, JS-DevTools/npm-publish@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
publish
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/