Sonatype Nexus Repository 3.48.0 Release Notes

Released February 27, 2023

New and Improved Content Replication PRO

In 3.34.0, we introduced our first replication feature, which used a manually run replicator tool to copy binaries from one blob store to another. We've learned a lot since our initial replication release, and we've gratefully received and listened to your feedback.

In this release, we introduce a simpler, more straightforward way to make your artifacts readily available across distributed teams: content replication

With content replication, you can manage what binaries are copied from one instance and pre-emptively pulled via HTTP to other instances.

There are multiple ways you can use content replication, including having multiple targets proxying one source, bi-directional content replication, or replicating a subset of content. You can learn more about these use cases and how to configure them in Content Replication Use Cases and Scenarios.

Content replication removes the requirement for manually running a separate replicator tool. It is far easier to configure and automatically runs every minute (or on your desired schedule as configured).

Content replication also has a shorter list of prerequisites and supports more formats.

Sonatype Nexus Repository Formats	Legacy Replication	Content Replication
Apt
Docker
Helm
Maven
npm
NuGet v3
R
Raw
RubyGems

Neither content replication nor legacy replication support Cocoapods, Conan, Conda, Git LFS, Go, p2, PyPI, or Yum formats

We cover this fully in the content replication documentation; however, if you're looking to reduce latency and make your content available to distributed teams quickly and efficiently, then we designed content replication with you in mind. Follow the simple content replication setup procedure to get started.

Content replication is not appropriate for disaster recovery. If you need a disaster recovery solution, please see our resilient deployment options and backup and restore procedures.

While help documentation for legacy replication remains available, it will be unavailable for general use, and we will eventually remove it. Reach out to your CSE if you are still using legacy replication and would like to continue using it.

Improved NuGet v2 Performance on PostgreSQL PRO

In this release, we made pagination performance improvements for NuGet v2 repositories on deployments using a PostgreSQL database. After upgrading to 3.48.0, users can expect pagination in NuGet v2 repositories to improve so that retrieving a page takes only milliseconds rather than multiple seconds.

Notable Upgrade Impacts

After upgrading to 3.48.0, those using an H2 or PostgreSQL database will need to run ataskfor each existing Helm and Yum repository in order to rebuild their metadata: