We are running into an issue where we have repositories that publish to multiple npm private scopes within a single organization (i.e. @scope1 @otherscope). Github NPM registry appears to prevent us from publishing to the registry and returns the following error:
npm ERR! 400 Bad Request - PUT https://npm.pkg.github.com/my-org/@otherscope%2fnpm-test - scope `otherscope` in package name `@otherscope/npm-test` does not match repo owner `my-org` in repository element in package.json
Previously with our private npm registry we have had no issue with having multiple scopes in the same registry. As per the npm documentation this is also stated as possible https://docs.npmjs.com/misc/scope#associating-a-scope-with-a-registry
Any idea how we can overcome this limitation? In the context of mono repos and other workflows it becomes difficult to maintain unique names for packages for an entire organization hence the utilization of scopes as an effective mechanism.