Nexus Repository 3.35.0 Released

We are pleased to announce Nexus Repository 3.35.0!

Improvements to Repository Replication
As outlined in detail below, we’ve made a number of improvements to the repository replication feature introduced in 3.34.0. If you’re new to repository replication, be sure to check out our Repository Replication help documentation.

Replicator Now Supports Docker and npm Formats
In addition to repositories using raw and Maven formats, source and target repositories can now also be in Docker or npm formats.

Replicator Now Runs Continuously by Default
You no longer need to run a separate bash script to keep the Replicator running continuously. Check out our new, simpler help instructions in Running Replicator.

New Replication Administrator Role
To simplify setup and managing privileges, we’ve created a Replication Administrator role that has all six privileges that relate to replication. Learn more in our Repository Replication help documentation.

Updated Database Migrator for Easier Migration Between PostgreSQL and H2 Databases
Those wishing to migrate between PostgreSQL and H2 databases can now use the Database Migrator utility to move from H2 to PostgreSQL or vice versa. We’ve provided updated instructions about migrating to a new database in our help documentation. You can also download the Database Migrator utility from our downloads page.

Conan Hosted Support for PostgreSQL and H2 Databases
Those requiring Conan hosted format support can now take advantage of our new PostgreSQL or H2 database options. See our help documentation for more information on using a hosted Conan repository.

Faster Imports with Hardlink Support for All Formats
In order to speed up import, we have added hard link support for all remaining formats that previously did not support hard links. This includes Docker, npm, NuGet, PyPI, RubyGems, and Yum.

Enabling hard links will create hard links for the blobs in the source directory to be used in the target directory. A physical copy of the blobs will not be created in the target directory. This can save time if the source directory will continue to be accessible by the current instance. Please note that detaching the source directory where the blobs are located from the current instance after using this option to import the artifacts will result in the blobs becoming inaccessible.

Read more in our Repository Import help documentation.

What’s New for Everyone?

Firewall Integration Improvement: Policy-Compliant Component Selection for npm
For those integrating Nexus Firewall with Nexus Repository, we have added a new Remove Quarantined Versions option to the Nexus Repository settings page. By enabling this option, Nexus Firewall will remove quarantined versions from the npm package metadata to prevent you from selecting a version with policy violations.

The Remove Quarantined Versions option will eventually replace the Remove Non-cataloged Versions option since, using properly configured policy, it is able to do that on top of additional functionality.

Check out our help documentation for more information on enabling this feature.

For more information, please refer to the 3.35.0 full release notes for more details.

Nexus Repository Team

1 Like