# Sonatype Nexus Repository 3.62.0 Release Notes

**Released November 7, 2023**

| #### Highlights in This Release |
| --- |
| **Pro Deployments using PostgreSQL Can Download Cleanup Preview CSVs**<br>Administrators on Sonatype Nexus Repository Pro deployments using PostgreSQL databases can now download a CSV report showing what a selected cleanup policy would remove if it were run as currently configured.<br>**Combined High Availability Helm Chart for AWS, Azure, and On-Premises HA Deployments**<br>Our previously separate AWS and Azure High Availability (HA) Helm charts are no longer available. Instead, we created a Helm chart that supports HA Sonatype Nexus Repository deployments in AWS, Azure, or on-premises.<br>**Deployment Pattern Library**<br>With this release, we are publishing a new library of deployment patterns specifically designed to address three primary concerns: resiliency, scalability, and distribution. |

## New Cleanup Preview Experience for Pro Customers Using PostgreSQL

To help you fine-tune cleanup policies and ensure that you do not unexpectedly remove important components, we've enhanced the cleanup preview experience for Sonatype Nexus Repository Pro deployments using a PostgreSQL database.

Admin users are now able to download a CSV report showing what a selected cleanup policy would remove if it were run as currently configured. The exported CSV lists component namespaces, names, versions, and paths.

Deployments using H2 or OrientDB will still see the old cleanup preview option. Check out the [cleanup policy help documentation](https://help.sonatype.com/en/cleanup-policies.html "Cleanup Policies") for full details on using this feature.

This feature was made possible because of your [feedback](https://ideas.sonatype.com/ideas/IDEAS-I-1308) in the [Ideas Portal](http://ideas.sonatype.com/).

## Cleanup Preview CSV Performance

To help you better plan how and when to use the new cleanup preview feature, we are also providing performance information. Cleanup preview CSV performance data is available in our [cleanup policy help documentation](https://help.sonatype.com/en/cleanup-policies.html "Cleanup Policies") and also shown below:

Generating a Cleanup Preview CSV can take some time depending on deployment size and configuration.

The table below provides a rough estimate of how long generating a CSV might take based on our internal testing using the following specifications:

Deployed on AWS using `ECS c6i.4xlarge` and `Aurora PostgreSQL db.r6g.large` both deployed in the same Availability Zone, Raw hosted repository

| **Components in Repository** | **Time to Generate CSV Report** |
| --- | --- |
| 1M | ~1min |
| 5M | ~2min |
| 10M | ~4min |
| 20M | ~8min |
| 23M | ~10min |
| 25M | ~15min |
| 27M | ~25min |
| 30M | ~40min |

## New Combined Helm Chart for AWS, Azure, or On-Premises High Availability Deployments PRO

We continue to make improvements to help make it easier for you to deploy Sonatype Nexus Repository in an HA environment. With this release, we introduce two big changes.

## HA Helm Charts Consolidated

We previously had separate Helm charts for Azure and AWS HA deployments. We have now consolidated all of our HA Helm charts into one, which you can find in our [Sonatype Nexus Repository HA Helm chart Git repository](https://github.com/sonatype/nxrm3-ha-repository/tree/main/nxrm-ha). We have also updated our [Azure HA deployment documentation](https://help.sonatype.com/en/option-4---high-availability-deployment-in-azure.html "High Availability Deployment in Azure") and [AWS HA deployment documentation](https://help.sonatype.com/en/option-3---high-availability-deployment-in-amazon-web-services--aws-.html "High Availability in Amazon Web Services") with appropriate modifications for the new Helm chart.

If you were previously using one of the individual Azure or AWS HA helm charts, you can find simple instructions on how to move to our new combined Helm chart in our [help documentation for upgrading in an HA environment](https://help.sonatype.com/en/upgrading-nexus-repository-in-an-ha-environment.html "Upgrading Nexus Repository in a Kubernetes Environment"). Note that you will need to customize a new values.yaml with appropriate information for your deployment; you will not be able to use the same custom values.yaml that you used with the individual AWS/Azure Helm charts.

This feature was made possible because of your [feedback](https://ideas.sonatype.com/ideas/IDEAS-I-2090) in the [Ideas Portal](http://ideas.sonatype.com/).

## HA Helm Chart Supports On-Premises Deployment

Our new HA Helm chart can also be used for on-premises HA deployments. This is the same Helm chart available in the [Sonatype Nexus Repository HA Helm chart Git repository](https://github.com/sonatype/nxrm3-ha-repository/tree/main/nxrm-ha). We have updated our [on-premises HA deployment documentation](https://help.sonatype.com/en/option-2---on-premises-high-availability-deployment-using-kubernetes.html "On-Premises High Availability Using Kubernetes") to reflect the new deployment option.

This feature was made possible because of your [feedback](https://ideas.sonatype.com/ideas/IDEAS-I-2181) in the [Ideas Portal](http://ideas.sonatype.com/).

## Support Zip Improvements for HA Deployments PRO

To make it easier for you to generate and download support zips, we've added some improvements to our _Support Zip_ generation screen for HA deployments.

HA deployments will now see a button that allows you to configure your support zip options once but generate support zips for all nodes.

The download link for a node's latest support zip also remains available even if you navigate away from and back to the _Support Zip_ page.

See our [Support Features documentation](https://help.sonatype.com/en/support-features.html "Support Features") for full details.

## Expanded Audit Logging

To improve supportability and help troubleshoot any issues that you may experience, we've expanded our audit logging.

The audit log now includes records for "Clear Cache" and "Change (server) order" [LDAP](https://help.sonatype.com/en/ldap.html "LDAP") events; this is available for all databases.

For H2 and PostgreSQL deployments, we've also added logging for when you create, update, or delete a [routing rule](https://help.sonatype.com/en/routing-rules.html "Routing Rules").

See our [auditing documentation](https://help.sonatype.com/en/auditing.html "Auditing") for details about audit logs.

## Deployment Pattern Library

We recognize that Sonatype Nexus Repository customers face an ever-growing need to balance availability with infrastructure costs while also providing functionality for teams across the globe.

With this release, we are publishing a new [library of deployment patterns](https://help.sonatype.com/en/deployment-pattern-library.html "Deployment Pattern Library") specifically designed to address three primary concerns: resiliency, scalability, and distribution.

The patterns in this library represent proven ways of deploying Sonatype Nexus Repository and can also be combined to meet multiple needs. You can use these patterns to help you plan a Sonatype Nexus Repository deployment that will meet your individual organization's needs.

Check out our new [deployment pattern library](https://help.sonatype.com/en/deployment-pattern-library.html "Deployment Pattern Library") in our help documentation. Specific patterns include the following:

- [Backup/Same-Site Restore](https://help.sonatype.com/en/backup-same-site-restore.html "Backup/Same-Site Restore")

- [Disaster Recovery Site](https://help.sonatype.com/en/disaster-recovery-site.html "Disaster Recovery Site")

- [On-Prem Active/Passive Resiliency](https://help.sonatype.com/en/on-prem-active-passive-resiliency.html "On-Prem Active/Passive Resiliency")

- [Cloud Active/Passive Resiliency](https://help.sonatype.com/en/on-prem-active-passive-resiliency.html "On-Prem Active/Passive Resiliency")

- [On-Prem Active/Active High Availability](https://help.sonatype.com/en/on-prem-active-active-high-availability.html "On-Prem Active/Active High Availability")

- [Cloud Active/Active High Availability](https://help.sonatype.com/en/cloud-active-active-high-availability.html "Cloud High Availability")

- [Star Pattern](https://help.sonatype.com/en/star-pattern.html "Star Pattern")

- [Federated Repositories](https://help.sonatype.com/en/federated-repositories.html "Federated Repositories")

- [Scaling with Proxies](https://help.sonatype.com/en/scaling-with-proxies.html "Scaling with Proxies")

- [Bi-Directional Proxying](https://help.sonatype.com/en/bi-directional-proxying.html "Bi-Directional Proxying")

- [Content Replication Pattern](https://help.sonatype.com/en/content-replication-pattern.html "Content Replication Pattern")

- [Combination Active/Active High Availability + Disaster Recovery Site](https://help.sonatype.com/en/combination-active-active-high-availability---disaster-recovery-site.html "Combination Active/Active High Availability + Disaster Recovery Site")

- [Combination Active/Active High Availability + Disaster Recovery Site + Federated Repositories](https://help.sonatype.com/en/combination-active-active-high-availability---disaster-recovery-site---federated-repositories.html "Combination Active/Active High Availability + Disaster Recovery Site + Federated Repositories")

## Notable Dependency Changes

This release includes updates to the following dependencies:

- Upgraded Jetty from version 9.4.51.v20230217 to version 9.4.53.v20231009

- Upgraded Goodies from version 2.3.5 to version 2.3.6

- Upgraded Eclipse-sisu from version 0.3.4 to version 0.3.5

- Upgraded Guice from version 5.0.1 to version 6.0.0

## HA-C in Extended Maintenance

In mid-October, we announced that our legacy HA solution High Availability-Clustering (HA-C) is now in extended maintenance and will be officially sunset in April 2024. Information can be found in the [Sonatype Nexus Repository 3 Feature Status](https://help.sonatype.com/en/sonatype-nexus-repository-3-feature-status.html "Nexus Repository 3 Feature Status").

Full details about our sunsetting process are also available in the [Sonatype Sunsetting Information section](https://help.sonatype.com/en/sonatype-sunsetting-information.html "Sonatype Sunsetting Information").

| Bug Fixes | Description |
| --- | --- |
| NEXUS-40526 | Fixed a display issue that was causing tag associations to be missing from on raw components after migration to PostgreSQL. **Note**: this was a display issue only and did not result in any missing data. |
| NEXUS-40425 | Fixed an issue that existed in version 3.61.0 that was preventing startup when .bak files existed under restore-from-backup. |
| NEXUS-40423 | Resolved an issue in 3.61.0 where duplicate user tokens were breaking upgrades. Upgrades now succeed and will detect duplicate rows and produce a log warning. |
| NEXUS-40325 | Docker Group repositories return the correct error if someone attempts to use a username/password when the Protect Content feature is enabled in the User Token capability. |
| NEXUS-40313 | User tokens work as expected with Conan repositories. |
| NEXUS-40196 | Created an advanced option for Sonatype Nexus Repository Pro customers to clean up identical Docker image layers across repositories. See the [support knowledge base article](https://support.sonatype.com/hc/en-us/articles/22490107929619) for full details. |
| NEXUS-40120 | Made changes to reduce the number of queries performed when running Nuget V2 `FindPackagesById` in PostgreSQL environments. |
| NEXUS-39411 | Resolved an important database migrator issue that could cause components and assets to be migrated in the wrong order. |
| NEXUS-39150 | Resolved a concurrency issue that was occurring when running the Staging move and Cleanup unused assets task at the same time. |
| NEXUS-38850 | The database migrator --health check option now also checks the configuration database for corruptions in config classes. |
| NEXUS-38257 | Repository configuration changes that occur while a search reindex task is running cause a lock exception after waiting for 60 seconds; however, the repository now stays in a stable state. A subsequent try to save the config change now works as expected once the long-running task is complete. |
| NEXUS-36836 | Running the DeadBlobsFinder groovy script against a large database no longer causes out-of-memory errors. |
| NEXUS-32009 | The last modified date for hosted yum repositories now matches the metadata rebuild date after migrating from OrientDB to H2. |
| NEXUS-22262 | Made changes to address multiple issues that were causing build failures due to failing to return maven-metadata.xml from a group repository.