actions
404 when trying to publish to npm.
Description: Same github action triggered by tag creation worked 2 weeks ago, now it fails when trying to publish a new version to npm.
Action version: using v4.
Platform:
- [x] Ubuntu
- [ ] macOS
- [ ] Windows
Runner type:
- [x] Hosted
- [ ] Self-hosted
Tools version: node version 21.x
Repro steps:
Here is the github action: https://github.com/baobabsoluciones/mango-ui/blob/master/.github/workflows/mango-ui-deploy-npm.yml
Here is the run that worked 2 weeks ago: https://github.com/baobabsoluciones/mango-ui/actions/runs/9052522117
And here are the two failing runs from yesterday and today: https://github.com/baobabsoluciones/mango-ui/actions/runs/9250954159 and https://github.com/baobabsoluciones/mango-ui/actions/runs/9267599146
Expected behavior: For the workflow to work correctly and a new version to get published
Actual behavior: A 404 error gets raised.
Hello @ggsdc Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback
Hello @HarithaVattikuti and @KathiravanKrish
I may have missed your initial reply and I was checking back on this as I had to do a new upload manually of the library in said repository.
Is there any news on this issue or how to fix it? Is there any class of log that I may be able to download that could give you back more information?
Thank you in advance for your help
Hello @ggsdc , Thank you once again for bringing this issue to our attention. We tried to reproduce the issue from our end but unable to reproduce with the same workflow that you ran, we were able to publish the package successfully without encountering the 404 error. Please find the screenshot for reference.
We have reviewed the package.json file & the GitHub Actions workflow configuration for the baobabsoluciones/mango-ui repository and confirmed that the package name mango-vue is correctly mapped and should not be causing the issue.
Here are a few things we wanted to verify on your side to further investigate:
NPM Token: Make sure the NODE_AUTH_TOKEN used in the workflow is valid and has the appropriate permissions to publish packages. Registry URL: Confirm that the registry URL is set correctly to https://registry.npmjs.org. Please double-check the npm configuration and the availability of the package name on the npm registry.
Thank you @KathiravanKrish I would double check the token, as the package is currently registered under our name and we can upoload manually.
Hello @ggsdc, a gentle reminder to please check and confirm the npm configuration and verify the availability of the package name on the npm registry. Thank you.
Hello @ggsdc, We are proceeding to close this ticket as we didn't hear anything from a long time. Please feel free to reach us in case of any issues to reopen the issue.
Hey, sorry to bother! May I ask you about how do you fix this issue? I am currently experiencing similar issue and having no clue. Thank you!
OK, I see. Just secret key is messed up.
