Sonatype Nexus Repository 3.87.0 - 3.87.2 Release Notes
Known Issue in Sonatype Nexus Repository 3.83.0 - 3.89.1
There is an issue in Sonatype Nexus Repository 3.83.0 - 3.89.1 where running the Verify and Repair or Data Repair Plan tasks can incorrectly delete valid assets, leading to potential data loss.
This issue is fixed in version 3.90.0.
Upgrade to version 3.90.0 before running the Verify and Repair or Data Repair Plan tasks.
Known Issue in Sonatype Nexus Repository 3.87.0 - 3.87.2
Sonatype is aware of an issue impacting Sonatype Nexus Repository 3.87.0 - 3.87.2 High Availability (HA) deployments that use group blob stores created using the REST API. After upgrading, the Blob Stores page can fail to load, and errors are logged during startup.
If you are using Nexus Repository in an HA configuration and have configured group blob stores via API, we recommend delaying your upgrade to 3.87.0 - 3.87.2 until a fix is available.
What's New and Noteworthy in 3.87.2?
Released January 15, 2026
Repair - Execute Data Repair Plan Task Disabled
To prevent potential data loss caused by a known issue impacting Sonatype Nexus Repository 3.83.0 and later, this release disables the Repair - Execute Data Repair Plan task by default.
Attempting to run this task will result in a failure and an error in the logs. The task remains visible in the UI, and any existing instances of this task will not be removed. However, execution is blocked by default.
While it is possible to manually re-enable this task by setting the nexus.reconcile.task.enabled property to true, it is important that you not do so until you are using a release that restores support.
We will announce when it is safe to re-enable this task in a future release note.
Bug Fixes in 3.87.2
Issue ID | Description |
|---|---|
NEXUS-50152 | The blob attribute loading process no longer deletes properties files on transient I/O errors or unhandled exceptions. |
What's New and Noteworthy in 3.87.1?
Released December 8, 2025
Multiple Bug Fixes
This release contains multiple bug fixes impacting release 3.87.0:
Issue ID | Description |
|---|---|
NEXUS-49788 | Restored a missing Netty class dependency that was required for Azure client initialization. Sonatype Nexus Repository instances using Azure blob store now start as expected. |
NEXUS-43821 | The Compact Blob Store task now gracefully handles 404 responses from Azure during deletion, allowing the task to continue when a blob is already missing instead of marking the task as failed. |
What’s New and Noteworthy in 3.87.0?
Released December 2, 2025
Java 21 Now Minimum Required Java Version
Java 21 is now the minimum required version for running Sonatype Nexus Repository. All official Docker images and installers have been updated to include Java 21 by default, ensuring compatibility with the latest platform improvements and long-term support standards.
Change Impacting Non-AWS S3 Blob Stores
Starting with Nexus Repository Manager 3.87.x, the AWS SDK used for S3 blob stores has been upgraded from version 1.12.658 to 2.33.5 because the AWS SDK for Java 1.x reaches end of life on December 31, 2025.
This change impacts users of non-AWS S3–compliant blob stores. Customers using S3-compatible storage should review compatibility with AWS SDK for Java 2.x when upgrading.
For example, Dell S3-compatible storage is currently incompatible with the latest AWS SDK.
Adjustments to Community Edition Usage Limits
To better align with our goals of supporting individual developers and small teams, Sonatype Nexus Repository Community Edition now supports up to 40,000 total components and 100,000 requests per day. These adjustments ensure consistent, reliable performance for intended use cases and help maintain Community Edition’s long-term sustainability.
When either threshold is exceeded, the addition of new components will pause until usage returns below both limits. This behavior helps safeguard performance and provides a clear signal that your development needs may benefit from the scalability and enterprise features offered in Sonatype Nexus Repository Pro.
Administrators can continue to monitor usage through the Usage Center. For details on interpreting usage and planning for growth, refer to the Usage Center documentation.
Repository Firewall Supports Release Integrity for NuGet
Repository Firewall now extends Release Integrity protection to NuGet components. This enhancement allows teams using NuGet to benefit from Sonatype’s analysis, which flags suspicious or malicious component behavior and automatically quarantines high-risk releases. By broadening ecosystem coverage, this update helps secure .NET development pipelines against emerging supply chain threats with minimal manual effort.
For full details, see the Release Integrity help documentation.
New Configuration API for Instance Configuration and Metadata Migration
A new Configuration API is now available to support configuration management and metadata migration between Nexus Repository instances. This API enables you to programmatically export and import repository configuration and retrieve or migrate asset metadata, making it easier to automate and streamline tasks such as environment setup, backup, and migration.
For details on available endpoints and usage examples, refer to the Configuration API documentation.
Modernized Login Experience
This release introduces a redesigned login experience that delivers a consistent, modern interface that aligns with enterprise accessibility standards.
OAuth2 Realm Now Enabled by Default with JWT
In Sonatype Nexus Repository Pro, the OAuth2 realm is now automatically enabled when nexus.jwt.enabled is set to true, either by default in high availability (HA) deployments or when manually configured in the nexus.properties file. This update ensures a smoother out-of-the-box experience for environments using token-based authentication and reduces the need for manual security realm configuration.
Bug Fixes in 3.87.0
This release includes a wide range of stability, performance, and usability improvements across Sonatype Nexus Repository. For better scannability, we've broken our bug fix listings into categories:
Repository and Format-Specific Fixes
Issue ID | Description |
|---|---|
NEXUS-49171 | APT repository metadata is now properly updated in both the source and target hosted repositories after performing a component move via the REST API. |
NEXUS-48894 | Docker pull requests against repositories with Repository Firewall enabled no longer fail due to a missing base URL; the system now derives it from the inbound request instead of requiring manual configuration. |
NEXUS-48777 | Docker login requests now succeed for users with access to at least one Docker repository, even when path-based routing is enabled. |
NEXUS-48729 | Deleting an individual npm metadata asset from the Browse page now correctly updates the UI without falsely indicating that the entire package directory has been removed. |
NEXUS-48561 | The proprietary component synchronization process now excludes orphaned Maven components without assets, preventing unintended quarantining of valid open source components. |
NEXUS-48463 | Routing rules now apply correctly to Huggingface proxy repositories. |
NEXUS-48330 | Nexus Repository now correctly caches and reuses remote ETags for npm package root requests when PCCS is enabled. |
NEXUS-48259 | Nexus Repository now consistently serves PyPI package metadata for proxy repositories protected by PCCS, regardless of whether the request URL includes a trailing slash. |
NEXUS-48000 | APT hosted repositories now generate Filename fields in metadata without a leading slash. |
NEXUS-47603 | Scoped npm packages in hosted repositories now appear with their full names (including the scope prefix) in search results. |
NEXUS-47551 | Outbound requests for scoped npm packages now correctly encode slashes, ensuring compatibility with strict registries and restoring support for scoped package installs in environments that require encoded URLs. |
NEXUS-47148 | Added validation for Composer package distribution types to prevent errors when processing certain upstream package metadata. |
NEXUS-45796 | Tag association requests in Sonatype Nexus Repository no longer return 404 errors immediately after uploading a component. |
NEXUS-42101 | Ensured that group-level maven-metadata.xml files are updated correctly when a version is deleted from a member repository. |
NEXUS-36481 | Docker group repository searches now handle invalid responses from member proxy repositories more gracefully. |
NEXUS-27439 | Anonymous access settings for Docker repositories in Sonatype Nexus Repository now correctly respect per-repository configurations, ensuring global anonymous permissions no longer override repository-level restrictions. |
User Experience and Access Control
Issue ID | Description |
|---|---|
NEXUS-49753 | Repository permission checks now defer evaluation of content selectors using the path variable to the asset level, restoring search and tag operations that failed after upgrading to 3.86.0 - 3.86.2. |
NEXUS-49653 | Authenticated users who navigate to the |
NEXUS-48888 | Search queries containing slashes ( |
NEXUS-48889 | Search queries using double quotes for exact matches now return correct results in High Availability (HA) Sonatype Nexus Repository deployments, aligning behavior with documented expectations. |
NEXUS-48542 & NEXUS-48540 | New login experience properly handles deep links. Users who log in with a username and password are now correctly redirected to their intended destination after authentication. |
NEXUS-48410 | The Blob Stores UI now displays Used Size instead of Total Size to more accurately reflect current storage usage and reduce confusion for administrators. |
NEXUS-47018 | Anonymous users with only |
NEXUS-46707 | The licensing UI now displays a more accurate message when updating a license, clarifying that a restart is only required if installing a license for the first time. |
NEXUS-44162 | The Blob Store and Repositories pages now display a "Calculating..." message while metrics are still being processed after a database migration. |
NEXUS-43689 | Creating LDAP server connections via the Swagger UI now works as expected. |
NEXUS-27044 | Enhanced LDAP logging to include full exception details and complete query information. |
NEXUS-25658 | Users only need edit and read privileges for a specific repository to access the Invalidate Cache button. |
Blob Store and Storage Management
Issue ID | Description |
|---|---|
NEXUS-49200 | You can no longer accidentally create blob stores with invalid names via the API. |
NEXUS-49091 | Cleanup policies now properly delete components when using the H2 database. |
NEXUS-49031 | Corrupted or unreadable blob properties files are now automatically deleted across all supported blob stores, allowing recovery tasks to proceed and preventing component download failures. |
NEXUS-48143 | Improved error handling in file and S3 blob stores now suppresses misleading warnings when simultaneous requests temporarily fail to update blob property files. |
NEXUS-48087 | Repository deletions now complete successfully even when group cleanup operations encounter issues; affected groups are logged for review. |
NEXUS-47545 | Failures during S3 blob store creation are now logged at the error level with full exception details, making it easier to diagnose issues without requiring debug-level logging. |
Performance, High Availability, and Scalability
Issue ID | Description |
|---|---|
NEXUS-49043 | Improved performance of the Users page by optimizing role mapping queries to prevent timeouts in environments with a large number of user roles. |
NEXUS-49032 | Support zip generation no longer logs serialization errors or truncates logs when SAML is configured. |
NEXUS-48160 | Task-specific log files are now preserved when deploying via Helm charts, improving troubleshooting by maintaining separate logs per task type while still supporting the combined allTasks.log output for Kubernetes environments. |
NEXUS-47926 | Improved the asset export task to gracefully handle missing blobs by skipping over them and logging warnings, allowing the export to complete successfully even if some blobs are unavailable. |
NEXUS-47826 | Improved reliability of the rolling upgrade process by preventing timeouts during schema changes from leaving the system in a failed or partially upgraded state. |
NEXUS-42345 | Added a global configuration option to control URL escaping behavior for proxy repositories. Details are included in the Configuring the Runtime Environment help documentation. |
NEXUS-40172 | The |
NEXUS-21637 | Improved support zip generation to prevent duplicate file path errors. |
Schema, API, and Configuration Improvements
Issue ID | Description |
|---|---|
NEXUS-49379 | Ensured the |
NEXUS-49154 | Refactored schema management to ensure all database changes are handled through Flyway migrations, preventing startup delays and outages caused by schema modifications under load. |
NEXUS-49120 | Sonatype Nexus Repository no longer includes |
NEXUS-48505 | Corrected the Components API response to include the appropriate blob store name instead of returning |
NEXUS-47905 | The archetype-catalog.xml file is now automatically updated after deploying new SNAPSHOT base versions of Maven archetypes, eliminating the need to manually delete the file to reflect recent changes. |
NEXUS-36020 | REST API updates to Maven repositories now validate deployment policy values correctly. |
NEXUS-25475 | Updated the REST API to accept |
Licensing and Audit
Issue ID | Description |
|---|---|
NEXUS-46449 | Tag association and disassociation with components are now recorded in the audit log. |
Coming Soon to Sonatype Nexus Repository
We’re excited to share that the following enhancements will be coming soon to Sonatype Nexus Repository:
Nexus Repository Instance Migrator
Sonatype’s new Nexus Repository Instance Migrator supports both configuration and content migration through a powerful command-line interface. Designed to handle complex, large-scale migrations with reliability and flexibility, the Instance Migrator includes features like repository mapping, real-time asset polling, persistent state tracking, and detailed logging.
Already using Nexus Repository Cloud? The migrator is already available for customers with an active cloud tenant. Our team will work directly with you to guide the setup and migration process for your Cloud onboarding.