Replies: 10 comments 7 replies
-
|
Agree! Further, it's very unexpected (to me) that this even applies to someone with admin permissions on the repo (as an owner, I think I can still see the package regardless), and it even applies to being able to see the package's existence via the web UI. |
Beta Was this translation helpful? Give feedback.
-
|
This is a very recent change, and applies only to packages created after some date. This is VERY frustrating, as there seems no way to change the default, or to programmatically turn it on. |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
@watson13j |
Beta Was this translation helpful? Give feedback.
-
|
@sanjeevh93 only newly created packages. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
We just had a newly created package that by default inherited permissions and was truly public ... so perhaps they've resolved/changed the default behavior? 🤞 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Godsfavoritelosangeles@gmail |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Is there a way we can set "Inherit access from source repository" by default either organization-wide or as a flag on the creation of a new package? This setting is buried and appears to be unchecked by default even though it's labeled "Recommended".
It also seems to be a recent change, as the dozens of NPM packages in my org are just now starting to run into permissions problems because inheritance isn't enabled. The only remedy appears to have an organization admin manually search for and mark individual packages for inheritance, which is tedious and error-prone.
Beta Was this translation helpful? Give feedback.
All reactions