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.
Thanks for creating a dedicated issue for this, @waqasibrahim (the previous issue wasn’t getting any attention since it’s marked fixed for an unrelated reason).
Here are the steps to reproduce:
Create a new private repository. Per npm package naming requirements, make sure the repo owner and name (i.e. @repo-owner/repo-name) are both lowercase.
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.
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.
I started also receiving today errors for installing packages (private) via circle ci…any ideas if there is anything wrong happenig? I feel like if it was a token problem I would not be getting a 404 but rather a permission denied…locally I can install the packages no problem…
Anyone else experiencing some issues recently on this?