My Profile Photo

Sheogorath's Blog

Depending on the time of the day a friend, a colleague, a wise guy. The beauty of the world is its sense of humor to show humans their way by letting them search their own.

Cover image for this blog post

Schroedinger's publish

Today I learned that GitLab silently drops published NPM packages due to a wrong package prefix, while yarn publish thinks it successfully published a package to GitLab’s integrated NPM package repository. The key to solve it, is to prefix your package with the exact value of $CI_PROJECT_ROOT_NAMESPACE. For example, when your package is hosted under, your package has to use @sheogorath as package prefix, otherwise GitLab will silently drop it.

I came across this while using the feature for the first time on my GitLab. To be fair, it’s documented in the instructions, but it still was confusing to me to have a successfully published package according to yarn, that never showed up anywhere.