Resolve "Publish npm package from sub group/project"
What does this MR do?
Currently NPM packages can only belong to a top level namespace. To allow for the publishing of NPM packages from subgroups, packages must be able to be named without the forward slash character, or rather, without using the full path of the project. This change allows users to name a package with the format @root_namespace_path/any-name. The logic in publishing/creating a package has been updated to detect if there is a name collision within the given root namespace and return an error if there is. The logic in installing/pulling a package has been updated to find the package by the package name, rather than looking it up by the full path of the project with is no longer applicable. An update to the documentation is included in MR29935 for gitlab-ce.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Performance and testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #9960 (closed)