Nexus Repository Manager 2.14.4 Release Notes

Nexus Repository Manager 2.14.4 Release Notes

These notes are a compilation of new features and significant bug fixes for Nexus Repository Manager 2.14.4.

See the complete release notes for all resolved issues.

New and Noteworthy

Nexus 3.x Upgrade Compatibility

Nexus 2.14.4 is upgrade compatible with the Nexus 3.3.0 release. Upgrading from a different Nexus 2.x version into Nexus 3.3.0 is explicitly blocked.

Edge-cases for corrupted or invalid npm and NuGet components that may exist in your Nexus 2.x instance will no longer block your upgrade to Nexus 3.x .

npm scoped packages support

By popular demand we have implemented package scope support for deploying and depending on scoped npm packages. Nexus Repository Manager 3.x already has this feature and now 2.x installations can start using scoped packages and be assured their packages will migrate correctly to Nexus 3 when they are ready.

Associating a scope with a registry is possible only by manually editing your ~/.npmrc file. Nexus 2.x does not support the special handling required to automatically add or remove scoped registries using adduser/login or logout commands. If you want this feature, using Nexus 3.x is still required.

Disabling Security Prompts for RUT Authentication

We have added a feature to disable user interface security prompts when using RUT authentication and LDAP realms together.

General Improvements


  • [ NEXUS-12483] Bug invalid nexus 2.x NuGet repository files will cause nexus 3.x upgrade to fail with NullPointerException
  • [ NEXUS-12513] Bug invalid nexus 2.x npm packages will fail the upgrade to nexus 3.x with 500 internal server error


  • [ NEXUS-6857] Improvement Support for npm scoped packages


  • [ NEXUS-11888] Bug http request header values should be checked for validity before allowing a request to proceed security
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk