Cleanup allow_custom_root_folder_name_in_npm_upload FF
What does this MR do and why?
In Fix publishing npm package with custom root fol... (!159095 - merged), we allowed publishing NPM packages to the npm Registry if their tarballs have custom root folder name.
The change was behind a feature flag, and it was globally enabled on gitlab.com for 2 weeks now without any issues.
In this MR, we clean up the feature flag and release the fix.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #473225 (closed)
Edited by Moaz Khalifa