Diagnose npm 404 publish error in GitHub Actions release
Session from pi-web on Hugging Face by woxQAQ · MIT · condensed by Coders Talk
Click a segment to jump to that moment
29ssession
0interventions
by library · 1d
GOAL
Figure out why the release workflow's npm publish step fails with a 404 error for the @woxqaq/pi-web package.
- +0Prompt · +0What's causing this npm 404 error when publishing @woxqaq/[email protected] via PUT to the registry?
- +0mAgent did · +0mRead package.json to check the package name, version and scope configuration
- +0mAgent did · +0mDiagnosed the error as an npm auth/permissions issue in the CI environment (path shows /home/runner/), then checked for a .npmrc file and listed workflow files
- +0mAgent did · +0mReviewed release.yml and ci.yml workflows to see how npm publish is configured and where auth token should be set
- +0mOutcome · +0mRoot cause identified as missing npm auth token in the CI publish workflow; no fix applied yet in this session
VERDICT
Next time I'd paste the workflow files alongside the error so the agent doesn't have to go fetch them itself. The read of release.yml and ci.yml was the useful step here, it's what let the agent pin down that the publish job likely lacks an NPM_TOKEN, but we never got to actually applying or verifying a fix.