You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're having issues with access and GitHub's NPM registry. Our situation is as follows:
A member has the Member role in our organization
The member is part of the Core team
The Core team has access to a private repository within our organization using the All-repository maintain Organization access
The member has a classic personal access token with the package:read permission
The token has been set correctly inside the .npmrc file
When the member tries to install the package, they receive a 403 error saying permission_denied: read_package
What's weird is that when a member with the Owner organization role tries the above, it works. All is the same, except for the member roles. Furthermore, when we give the Core team Direct access, everything also works.
Are we missing something in our settings, or is this a bug?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone,
We're having issues with access and GitHub's NPM registry. Our situation is as follows:
Member
role in our organizationCore
teamCore
team has access to a private repository within our organization using theAll-repository maintain
Organization accesspackage:read
permission.npmrc
filepermission_denied: read_package
What's weird is that when a member with the
Owner
organization role tries the above, it works. All is the same, except for the member roles. Furthermore, when we give theCore
team Direct access, everything also works.Are we missing something in our settings, or is this a bug?
Appreciate any help we can get!
Beta Was this translation helpful? Give feedback.
All reactions