Sonatype Nexus Repository 3.96.0 - 3.96.3 Release Notes
The Sonatype Nexus Repository 3.96.x release line includes exciting new features, enhancements, and bug fixes. Learn more in the sections below!
Release Timelines
3.96.0 – September 1, 2026
3.96.1 – September 12, 2026
3.96.2 – September 18, 2026
3.96.3 - September 22, 2026
Check Known Issues Before Upgrading
This version line contains important known issues
Before upgrading, see the Known Issues & Upgrade Guidance section at the end of these release notes to determine whether any known issues or upgrade recommendations apply to your environment.
What’s New and Noteworthy in This Release?
The Sonatype Nexus Repository 3.96.x release line includes the following new features and enhancements:
Azure Direct Download for Azure Blob Stores
Sonatype Nexus Repository Pro now supports direct artifact downloads from Azure Blob Storage using short-lived SAS URLs. When enabled for an Azure blob store, Nexus Repository redirects clients directly to Azure Storage instead of proxying artifact data through the Nexus Repository server. This can reduce network and server resource usage while improving download throughput.
Azure Direct Download supports Shared Key, Managed Identity, and Environment Variable authentication. Nexus Repository also validates the configured Azure permissions when you enable direct downloads and automatically falls back to standard proxied delivery if a SAS URL cannot be generated, helping maintain reliable artifact access without requiring changes to client workflows.
Nexus Repository 2-to-3 Upgrade Wizard Removed
As of release 3.96.0, Sonatype Nexus Repository no longer includes the legacy Nexus Repository 2-to-3 Upgrade Wizard. The wizard and its associated migration capability have been removed from the product, reducing the surface area of legacy functionality and simplifying Nexus Repository administration.
This change does not affect standard Nexus Repository 3 upgrades or the Nexus One UI Upgrade page, which continues to provide current version information and upgrade resources. For customers migrating from Nexus Repository 2, see the Nexus Repository 2 migration documentation for supported migration paths.
OAuth2 and SSL Certificate Management in the Nexus One UI
Sonatype Nexus Repository now provides OAuth2 and SSL Certificate management in the Nexus One UI, giving administrators a modern interface for configuring authentication and managing trusted certificates. The new experience provides improved form validation, certificate inspection, and integration with the Nexus Repository truststore, making it easier to configure and maintain secure connections to external identity providers.
The Nexus One UI also improves related security administration workflows, including preserving privilege searches when assigning multiple privileges and clearly displaying role types when editing existing roles. These enhancements provide a more consistent and efficient experience for managing authentication and security settings.
Improved Component Details Experience in the Nexus One UI
Sonatype Nexus Repository now provides an improved component details experience in the Nexus One UI, with faster version browsing and format-aware dependency information. The Versions tab now loads results incrementally, making it easier to work with components that have large numbers of versions while providing accurate version counts and ordering.
The Component Overview tab now displays dependency snippets that match the component's repository format, giving developers relevant commands and configuration examples they can copy directly into their projects. Component details and format information are also presented more consistently, with applicable registry links and other information shown only when relevant.
Improved Community Edition Usage Visibility in the Nexus One UI
Sonatype Nexus Repository Community Edition now provides a more consistent and informative experience for monitoring usage across the Classic UI and Nexus One UI. Usage status and alerts are surfaced more clearly throughout the product, while the Usage Metrics dashboard provides administrators with a central view of component counts, request activity, and other usage information.
The enhanced experience makes it easier to understand current usage and take action when approaching Community Edition limits. Alerts now provide direct access to usage details, and metric cards include additional context to help administrators interpret their usage without leaving the dashboard.
Improved Audit Logging and Visibility in the Nexus One UI
Sonatype Nexus Repository now provides an improved audit logging experience with persistent audit event storage and a dedicated Audit Log page in the Nexus One UI. Administrators can browse, filter, and review significant configuration and security events directly in the interface, making it easier to monitor administrative activity and support compliance and troubleshooting workflows.
The enhanced audit experience includes configurable retention to help manage stored audit data, improved query performance, and more meaningful event records by excluding high-volume operational activity. Audit events also maintain accurate user attribution, including for asynchronous configuration changes, and administrators can view audit history for individual repositories directly from Repository Settings.
Streamlined User Management in the Nexus One UI
Sonatype Nexus Repository now provides a streamlined user management experience in the Nexus One UI. Selecting a user takes you directly to the appropriate view based on your permissions, while user editing combines profile details, role assignments, and an interactive security tree into a single page. The security tree updates as you change role assignments, helping you review effective privileges before saving.
The updated experience also simplifies common user administration tasks with a cleaner user list, safer user deletion controls, and save and cancel actions that activate only after changes are made. Together, these improvements make it easier to manage users and review their access with fewer steps.
LDAP and Atlassian Crowd Configuration Now Available in the Nexus One UI
Sonatype Nexus Repository now provides configuration pages for LDAP and Atlassian Crowd in the Nexus One UI. Administrators can configure and manage external authentication through the modern interface without switching to the Classic UI.
The new configuration experience provides improved validation, connection testing, error handling, accessibility, and overall usability. LDAP and Crowd administrators can more easily identify configuration errors, verify connections and user mappings, manage existing LDAP servers, and navigate configuration forms using keyboard and screen reader support. This enhancement brings the LDAP and Crowd administration experience in the Nexus One UI in line with the existing Classic UI functionality while providing a more consistent experience across Nexus Repository settings.
Improved Chained Proxy Support Across Multiple Repository Formats
Sonatype Nexus Repository now provides improved chained proxy support for OCI, Swift, Pub, Ansible Galaxy, Hugging Face, Terraform, and Conda repositories. Organizations can more reliably use these formats in tiered, restricted, or air-gapped network environments where one Nexus Repository proxy repository retrieves content through another Nexus Repository instance before reaching the upstream source.
This enhancement improves authentication, request routing, and artifact resolution across the proxy chain. OCI and Swift repositories can authenticate with intermediate Nexus Repository instances, Pub repositories correctly construct upstream requests, Ansible Galaxy rewrites download URLs for downstream clients, Hugging Face supports pagination across chained proxies, and Terraform and Conda support preemptive authentication where applicable. These improvements help provide more reliable artifact retrieval while simplifying dependency management in isolated environments.
Reduced Bandwidth for npm Metadata Responses
Sonatype Nexus Repository now reduces the amount of data transferred for npm metadata requests, helping improve package installation performance and reduce bandwidth and egress costs. When supported npm clients request abbreviated package metadata, Nexus Repository returns a smaller metadata representation instead of the full packument. Nexus Repository continues to use the full metadata internally and returns full metadata to clients that do not request the abbreviated format, preserving compatibility with existing workflows.
Nexus Repository can also gzip-compress npm JSON responses when clients indicate gzip support through the Accept-Encoding header. This compression applies specifically to eligible npm responses, including large packuments, without enabling compression globally for other repository formats. Together, abbreviated metadata and gzip compression can substantially reduce npm response sizes while maintaining compatibility with npm, Yarn, and pnpm clients and ensuring caches and CDNs distinguish between response variants correctly.
npm Abbreviated Packument Support for Faster Package Installs
Sonatype Nexus Repository now supports the npm abbreviated packument format, allowing npm clients to receive only the package metadata required for installation. This reduces the amount of metadata transferred during npm install operations, with payload sizes reduced by up to 89% for packages with large numbers of published versions.
POM Metadata Size Protection for Maven Repositories
Sonatype Nexus Repository now limits the size of name and description metadata stored from Maven POM files to 10,000 characters. Values that exceed this limit are truncated during deployment, helping protect repository metadata from excessively large values and ensuring that stored component information remains available for browsing and retrieval.
Consistent Scripting Controls
Sonatype Nexus Repository now consistently enforces the nexus.scripts.allowCreation setting across all script operations.
This enhancement provides clearer and more predictable administrative control over scripting, while maintaining the security best practice of keeping scripting disabled when it is not required. To run existing scripts, temporarily enable scripting through nexus.properties and restart Nexus Repository.
Telemetry Delivery Notification
Nexus Repository 3.96.0 adds an administrator notification when required base telemetry cannot be delivered. This notification does not affect repository operation or upgrade behavior. If you see the notification, confirm that your server can reach the Sonatype telemetry service, then run the Upload Retry task. If the issue continues, contact Sonatype Support.
For details about the anonymous, non-sensitive information collected by Nexus Repository, see the Nexus Repository Telemetry help documentation.
Bug Fixes
The tables below detail notable bug fixes in each release within this release line.
3.96.3 Bug Fixes
Issue ID | Description |
|---|---|
NEXUS-55218 | The Change Repository Blob Store task now removes only blobs associated with the moved repository, preserving content from other repositories in the source blob store and keeping it available for download. |
3.96.2 Bug Fixes
Issue ID | Description |
|---|---|
NEXUS-54576 | NuGet package publishing to hosted repositories with Disable Redeploy configured now completes successfully when multiple packages share common embedded PDB files, and regular NuGet packages containing PDBs are correctly stored and resolvable by consumers. |
NEXUS-54572 | NuGet symbol assets ( |
3.96.1 Bug Fixes
Issue ID | Description |
|---|---|
NEXUS-54915 | The Retain N versions cleanup policy now uses correctly normalized component versions when ranking pre-release components, preventing newer versions from being selected for deletion while older versions are retained. |
3.96.0 Bug Fixes
Issue ID | Description |
|---|---|
NEXUS-54717 | HTTP HEAD requests to Docker manifest endpoints now update the |
NEXUS-54508 | The Firewall Mode option is no longer displayed for repository formats that do not support Sonatype Repository Firewall, preventing unsupported configurations. |
NEXUS-54507 | Concurrent HEAD and GET requests for the same uncached proxy repository asset now complete successfully without returning HTTP 500 errors. |
NEXUS-54504 | Netty has been upgraded to improve security and compatibility, including strengthened TLS and SSL hostname verification and SNI handling. |
NEXUS-54364 | OCI proxy repositories now honor globally configured HTTP and HTTPS proxy settings for outbound requests. |
NEXUS-54339 | Docker proxy repositories now return all available image tags, including images with more than 10,000 tags. |
NEXUS-54326 | Cargo sparse-index metadata is now served more efficiently for proxy and group repositories, improving performance during cold |
NEXUS-54290 | Users authenticated through Remote User Token authentication are now directed to the appropriate page when the Nexus Repository user interface loads. |
NEXUS-54261 | The Remote Index Path field is now available in the Classic UI for PyPI proxy repositories, allowing repositories with non-standard upstream paths to be configured and edited directly in the user interface. |
NEXUS-54251 | Local usage metrics are now collected independently of external telemetry. |
NEXUS-54199 | User invite and deletion activity in Nexus Repository Cloud is now recorded in the audit log and available through the Audit REST API, improving visibility into user lifecycle changes. |
NEXUS-54198 | Nexus Repository Cloud now records user invite activity in the standard logs, making invitation and email delivery activity easier to trace. |
NEXUS-54157 | NuGet proxy repositories now correctly apply the configured |
NEXUS-54142 | NuGet searches against hosted repositories in a group now complete successfully when individual assets have incomplete format metadata. |
NEXUS-54141 | NuGet V3 registration index requests now complete successfully when proxied components contain incomplete metadata. |
NEXUS-54133 | Nexus Repository 2-to-3 migration connections now complete successfully when an upgrade is initiated through the Migration Assistant. |
NEXUS-54130 | Not Found Cache entries are now coordinated across nodes in High Availability deployments, providing consistent responses for the same proxy repository requests. |
NEXUS-54087 | Concurrent uploads to raw hosted repositories now return a clear conflict response when another operation removes the same component, instead of returning an unexpected server error. |
NEXUS-54074 | User searches on the Security → Users page now query the server using the entered filter, allowing users to be found regardless of the number of accounts in the selected source. |
NEXUS-54068 | Setting |
NEXUS-54043 | npm |
NEXUS-54026 | npm hosted repository migrations now preserve |
NEXUS-53976 | Repository Evaluation Settings now load and save correctly when Nexus Repository runs behind a reverse proxy with a custom context path. |
NEXUS-53973 | Blob cleanup tasks now remove orphaned database records when their corresponding blob files are missing, preventing repeated warnings and allowing cleanup to complete successfully. |
NEXUS-53918 | Repositories with legacy cleanup policy references now initialize successfully after an upgrade, without requiring manual removal of obsolete configuration. |
NEXUS-53864 | NuGet proxy repositories with strict content type validation now reject zero-byte JSON responses from upstream sources instead of treating them as valid assets. |
NEXUS-53861 | The Delete action is now hidden from read-only users in the Nexus One UI browse view, accurately reflecting their permissions. |
NEXUS-53847 | SAML user mappings can now be retrieved through a paginated REST API, allowing organizations with more than 1,000 users to retrieve the complete set of mappings. |
NEXUS-53749 | npm JSON responses are now gzip-compressed when requested by the client, reducing bandwidth usage and improving performance for npm workloads. |
NEXUS-53662 | The user update REST API now accepts requests that update only the user's |
NEXUS-53644 | The OrientDB security alert now appears only for deployments using OrientDB, preventing irrelevant alerts on PostgreSQL and H2 deployments. |
NEXUS-53560 | Webhook and other capability event delivery now automatically recovers when an underlying dependency is restored, eliminating the need for manual recovery or a service restart. |
NEXUS-53425 | Docker Firewall scans on Windows now complete successfully for Linux-built images containing files with trailing spaces in their names. |
NEXUS-53389 | Azure S3-compatible blob store configuration now validates the specified region when saved, preventing invalid configurations that could cause startup failures. |
NEXUS-53288 | The Log Management API now returns complete hourly request logs instead of only a subset of entries near the hour boundary. |
NEXUS-52934 | Assets in group repositories remain available while a Change Repository Blob Store migration is in progress. |
NEXUS-51541 | Blob store operations no longer generate false ERROR-level log entries during concurrent component requests. |
NEXUS-51211 | Pinned-version R package installations now complete successfully against CRAN proxy repositories, including archived package versions. |
NEXUS-35825 | Assets restored through the Repair - Reconcile Blob Store task no longer generate repeated cache warnings on subsequent requests. |
NEXUS-22163 | Yum group repositories now correctly discover and serve modular repository metadata, allowing DNF clients to resolve modular packages through group repositories. |
NEXUS-15051 | npm repositories now return abbreviated packument metadata when requested by the client, reducing metadata payload sizes by up to 89% and improving package installation performance. |
Known Issues & Upgrade Guidance
This section captures known issues in the 3.96.x line as well as upgrade guidance.
Resolved Known Issues
Impacted Version(s) | Version in which Issue is Resolved | Description |
|---|---|---|
3.96.0 – 3.96.2 | 3.96.3 | When running the Change Repository Blob Store task under certain conditions, it can delete blobs that remain associated with repositories other than the repository being moved. This can make affected components unavailable from those other repositories. |
3.95.0 – 3.95.3 & 3.96.0 | 3.95.4 & 3.96.1 | For self-hosted deployments, this issue can occur after taking both of the following actions:
Cloud deployments that use the Number of Versions field (or Retain in the API) with an affected format are also impacted. Changes to version normalization can cause components created before and after the upgrade to use different normalized version formats. When a cleanup policy uses the Number of Versions field (or Retain in the API), Nexus Repository may sort these mixed values incorrectly. As a result, the cleanup policy may select newer component versions for deletion while retaining older versions. |