New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Npm public login require but new bug #974
Comments
Hello @plsgivemeachane |
Hi @plsgivemeachane, we've conducted a test on our end using an auth token to publish the registry, and it completed without any errors. Here's a screenshot for your reference. Could you please verify if you're using the correct auth token with the necessary publishing permissions? |
I thought that the github token are created in runtime, isn't it? |
To publish npm in our GitHub registry, we may follow one of two methods:
|
Hello @plsgivemeachane |
Hello @plsgivemeachane, |
npm notice === Tarball Details ===
npm notice name: @quanvndev/waterx
npm notice version: 1.0.5
npm notice filename: @quanvndev/waterx-1.0.5.tgz
npm notice package size: 129.4 kB
npm notice unpacked size: 525.8 kB
npm notice shasum: 8edca9b93551a8d8806cace4fdeea3734f9683a5
npm notice integrity: sha512-8a4WKePggCg3l[...]zvROWUZgv8gpg==
npm notice total files: 32
npm notice
npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in to https://registry.npmjs.org/
npm ERR! need auth You need to authorize this machine using
npm adduser
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/logs/2024-02-27T01_2058_187Z-debug-0.log
Error: Process completed with exit code 1.
Description:
Github actions bug need login when already pass through the GITHUB_ACTION token
already read other duppilcate closed issue
The text was updated successfully, but these errors were encountered: