Sonatype Nexus Repository 3.55.0 Release Notes

Highlights in This Release 

Improved Flexibility in Resiliency Helm Chart PRO

Fluentbit, External DNS, and the Docker Ingress and service are now all optional in the Helm chart for a resilient Sonatype Nexus Repository deployment in AWS. Read more below

Streamlined Experience for Those Using Sonatype Repository Firewall

Those using Sonatype Repository Firewall with Sonatype Nexus Repository will no longer see Repository Health Check references in their Sonatype Nexus Repository instances as Firewall is a much more fully featured tool for identifying security risks in your repositories. Read more below

Quick Actions on Welcome Page

To improve user experience, we've added some quick actions to the welcome page to get you using Sonatype Nexus Repository more quickly. Read more below

What's New and Noteworthy in This Release?


Improved Flexibility in Resiliency Helm Chart PRO 

In order to allow you to better control your resilient deployment's configuration, we've updated our Helm chart for a resilient Sonatype Nexus Repository deployment in AWS to make the following configurations optional:

  • Fluentbit

  • External DNS

  • Docker Ingress and service

Added Conan Endpoint PRO 

In this release, we implemented the /v2/users/authenticate Conan endpoint for hosted Conan repositories on Sonatype Nexus Repository deployments using H2 or PostgreSQL databases.

Sonatype Nexus Repository still only officially supports Conan v1.

Streamlined Experience for Those Using Sonatype Repository Firewall

Because integrating Sonatype Repository Firewall with Sonatype Nexus Repository provides the most robust solution for protecting your repositories from security risks, we wanted to remove some clutter from our Firewall users' screens. To this end, instances that meet the following two conditions will no longer see Repository Health Check references in their Sonatype Nexus Repository instances:

  1. The Enable IQ Server checkbox is checked under Administration → IQ Server.

  2. The IQ Server instance has Sonatype Repository Firewall as a feature.

    1. You can determine if your IQ Server instance has Sonatype Repository Firewall by sending a GET request to the /rest/product/features endpoint in IQ Server.

    2. The service will return a firewall property if it is included as a feature.

This impacts the Health Check column in tables for browsing and managing repositories as well as the Health Check: Configuration capability. 

Quick Actions on Welcome Page 

This feature is only available for those who have the Outreach Management capability enabled for their instance.

Your time is important; we don't want you to spend it hunting for what you need. To improve user experience, we've added some quick actions to the welcome page to get you using Sonatype Nexus Repository more quickly. Here's what you can expect to see:

Quick ActionDescriptionWho Sees It?
System HealthView system status checksThose with nexus:metrics:read permissions
Cleanup Policies

Review component removal policies

Those with nexus:*  permissions
BrowseBrowse your repositories

You will see this option if there is at least one browsable format

SearchSearch for componentsThose with nexus:search:read  permissions
Release NotesRead the Sonatype Nexus Repository Release Notes on https://help.sonatype.com Everyone
DocumentationView our help documentation on https://help.sonatype.com Everyone
CommunityAsk and answer questions on https://community.sonatype.com/Everyone

Bug Fixes 


  • The Standard request timeout and Extended request timeout fields in the UI:Settings capability are now properly updated when upgrading from older versions.
  • Sonatype Nexus Repository now supports Yum repositories using the caret (^) character in RPM names.
  • Staging move respects the Allow redeploy only on 'latest' tag setting as expected.
  • Subdomain routing now reflects the nexus-context-path.
  • NuGet v3 search in non-HA environments now return components that have a dot after a digit. Note that search works differently in HA, and we are still investigating a fix for HA environments.