I have a private repository and I was able to publish a private package successfully. But when I try to install the package, It gives a 404 error. I cannot download the package from the package landing page and the assets links to https://notfound.pkg.github.com/.
I changed the visibility to public and the installation and assets' link worked fine.
Solved! Solved! Go to Solution.
Here are the steps to reproduce:
$ npm login --scope @repo-owner --registry https://npm.pkg.github.com
$ npm view @repo-owner/repo-name
@firstname.lastname@example.org | ISC | deps: 0 | versions: 1
Now, try to install the package:
$ npm install -g @repo-owner/repo-name npm ERR! code E404 npm ERR! 404 Not Found - GET https://npm.pkg.github.com/download/@repo-owner/repo-name/0.0.1/8d84896fe3f54d8ce56962cf1f7fc760e56efe52f2d471cf703103c476d3c9a9
Check that though the GitHub UI is showing the new version, its tarball links to https://notfound.pkg.github.com/:
Same isssue here, which is a shame as when github packages was released it looked like a perfect solution for consolidating a lot of disparate repository guff I've had to deal with.
I can confirm that the problem has been fixed and might have been related to some "data transfer" billing issues at github. Support eventually cameback to me after 2 weeks and gave me the following response.
Hey there *NAME RETRACTED*,
Thanks for your patience here, we believe there may have been some issues with rounding the data.
Can I ask you to:
Usage should be more accurately reflected, and you should be able to start using the package registry once more.
We've also been getting charged for data transfer out when using personal access tokens to get a docker image hosted on the GitHub Package Registry from GitHub Actions. This is supposed to be free.