Nexus Repository 3.47.0 - 3.47.1 Release Notes
Warning Missing Blob Exception Fix (3.47.1) This release fixes an issue that was causing missing blob exceptions for those upgrading to 3.47.0. If you have not upgraded to 3.47.0, upgrade to 3.47.1 instead. If you have already upgraded to 3.47.0, upgrade to 3.47.1 as soon as possible. Migrate Multiple Deletion Index Files (3.47.0) Nexus Repository now migrates all deletion index files, ensuring that all soft-deleted blobs are migrated when moving from an HA-C environment or where Bug Fixes (3.47.0) This release primarily focuses on improving Nexus Repository quality and, as such, includes multiple bug fixes. |
3.47.1Released February 9, 2023
Missing Blob Exception Fix
This release fixes an issue that was causing missing blob exceptions for those upgrading to 3.47.0. If you have not upgraded to 3.47.0, upgrade to 3.47.1 instead. If you have already upgraded to 3.47.0, upgrade to 3.47.1 as soon as possible.
3.47.0 Released February 7, 2023
Continued UI Improvements
We continue to improve user experience and accessibility by converting our UI to use React components. In this release, we made the updated HTTPS Settings and SSL Certificates pages visible to all users.
Improve Migration Experience for Those Migrating to a SQL Database PRO
When migrating from OrientDB to a SQL database, Nexus Repository previously only migrated the deletion index file (where soft-deleted blobs are indexed) matching the current nodeId. However, sometimes your nodeId may not match that of the deletion index file you need to migrate. Moreover, if you are migrating from a High Availability Clustering (HA-C) environment, you will have and want to keep multiple deletion index files. To account for these scenarios and ensure all soft-deleted blobs are migrated, we made improvements so that Nexus Repository migrates all deletion index files.
Ticket Number | Description |
|---|---|
NEXUS-37325 | Fixed an issue that was causing missing blob exceptions for those upgrading to 3.47.0. |
NEXUS-36506 | Resolved an issue that was causing an error to be thrown when making an npm group request while one member proxy is unavailable. If a member repository is blocked/unavailable, then Nexus Repository will still try the other members as expected. |
NEXUS-36617 | PyPi indexes are now updated or generated as expected when importing a repository on H2 and PostgreSQL deployments. |
NEXUS-36667 | The logged execution time for database upgrade steps now correctly reports as milliseconds. |