Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Copilot Lvl 2
Message 1 of 7

Github package registry - Private package not found

Solved! Go to Solution.

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.

6 Replies
Ground Controller Lvl 1
Message 2 of 7

Re: Github package registry - Private package not found

I'm having this exact same problem.

Ground Controller Lvl 2
Message 3 of 7

Re: Github package registry - Private package not found

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:

 

  1. 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.
  2. Create a personal access token with the following scopes:
    • write:packages
    • read:packages
    • repo
  3. Authenticate against the GitHub NPM registry using your GitHub username and personal access token:
    $ npm login --scope @repo-owner --registry https://npm.pkg.github.com
  4. Use npm init to create a new npm package called @repo-owner/repo-name.
  5. Publish a new (and only) version of the NPM package with npm publish.
  6. Check that the package is visible with npm view:
    $ npm view @repo-owner/repo-name
    @repo-owner/repo-name@0.0.1 | 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/:


github-package-npm.png

Copilot Lvl 2
Message 4 of 7

Re: Github package registry - Private package not found

I am also getting this.

Copilot Lvl 2
Message 5 of 7

Re: Github package registry - Private package not found

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.

Ground Controller Lvl 1
Message 6 of 7

Re: Github package registry - Private package not found

I am having the same issue.

Solution
Copilot Lvl 3
Message 7 of 7

Re: Github package registry - Private package not found

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.

 

Thanks
*NAME RETRACTED*

-----