Sonatype Nexus Repository 3.76.0 - 3.76.1 Release Notes

This release introduces full native support for Conan 2.0, bringing significant improvements to your C/C++ development workflows. This enhancement empowers your development teams to leverage the latest advancements in Conan, including improved package IDs, streamlined recipe formats, and a redesigned command-line interface.

By integrating Conan 2.0 with Nexus Repository Pro, you gain full control over your C/C++ dependencies, ensuring consistency, reproducibility, and efficiency across your development lifecycle. Benefit from enhanced security, simplified workflows, and improved collaboration, all while leveraging the comprehensive features of Nexus Repository Pro, including repository management, cleanup policies, high availability, content replication, and robust security measures.

To ensure a smooth transition from Conan 1.x to 2.0, you will need to maintain separate repositories for Conan 1.x and 2.0 packages within Nexus Repository. This avoids conflicts and allows for a phased migration approach, enabling you to update your recipes and client configurations gradually while continuing to leverage existing Conan 1.x packages. Note also that support for group Conan repositories is limited to version 2.0 only. For detailed guidance, see our Conan format help documentation.

Malicious components can infiltrate your repositories even before you've implemented security measures like Sonatype Repository Firewall. To combat this, Nexus Repository Pro now includes a dedicated Malware Remediation task that performs a deep inspection of all components in your proxy repositories, regardless of when they were ingested.

This new task complements the malware warning banner introduced in version 3.73.0 by providing a streamlined way to identify and manage existing malware. Configure the Malware Remediation task to leverage Sonatype Repository Firewall and analyze components for potential threats to identify malicious components in your repositories. The task generates a comprehensive report accessible through a dedicated Malware Audit page, offering valuable information such as component name, repository location, and quarantine status.

For full details, see the Malware Risk help documentation.

Nexus Repository now automatically detects and uses your Nexus Repository instance’s GCP region when creating new GCP blob stores. This eliminates the need to manually specify the region, simplifying your configuration and reducing the risk of errors.