Nexus Repository Pro+ evaluates components requested by developers, build systems, and AI agents against Sonatype intelligence and organization policies before they are migrated to development environments. The new edition builds on Nexus Repository Pro with malware protection in addition to security, legal, architectural, and age-based intake policies.
Nexus Repository Pro+
Pro+ can identify and block malicious components, including emerging threats, before they reach builds. Its policy controls apply at component intake, giving organizations a way to govern which open-source components may enter their environments.
Nexus One search and component details
The Nexus One UI now reports accurate result counts and supports sorting by Last Updated, Name, and Repository. Search criteria are displayed in URLs, so users can bookmark or share a query.
Component details now show much clearer repository and component information, consistent timestamps, accurate file and repository counts, and Repository Health Check data for popularity, age, and licenses.
Required base telemetry
Base telemetry is now required for consistent usage reporting. Administrators receive guidance for acknowledging the requirement and checking connectivity to the Sonatype telemetry service; a grace period applies before repository restrictions take effect.
The Baseline Telemetry health check shows acknowledgement status. Upload errors provide actionable details for configuration, licensing, or connectivity issues.
Chained proxy reliability
Chained proxies receive format-specific corrections for Ansible Galaxy, Hugging Face, Terraform, and Conda repositories. Ansible Galaxy rewrites upstream artifact URLs for downstream consumers; Hugging Face retains usable pagination; and Terraform returns the authentication challenge downstream Nexus Repository instances need for credential negotiation.
Conda proxy repositories can send credentials with their first upstream request, reducing authentication exchanges when cache misses occur.
Conda preemptive authentication persistence
Conda proxy repositories now persist and apply the httpClient.authentication.preemptive setting. Organizations that set this value through the REST API before version 3.97.0 should review the repository configuration after upgrading and confirm the intended behavior.
Service account tokens across formats
Service account tokens now work with every supported repository format. Automated clients may use the same sat.* credential through HTTP Basic or Bearer authentication where the format and native client support it.
For Basic authentication, use the service account name as the username and the token as the password. This permits dedicated machine identities for CI/CD, build systems, and other automation across package ecosystems.
OCI proxy URL validation
When an OCI proxy repository is created or updated through the UI or REST API, its Remote Storage URL must start with http:// or https://. Nexus Repository retains the submitted URL in its stored configuration.
Automatic Health Check coverage
Repository Health Check now runs automatically for proxy repositories. Administrators no longer need to select Configure for all proxy repositories to apply this coverage.
Swift proxy Firewall support
Repository Firewall now supports Swift proxy repositories. Swift dependency requests can be evaluated against configured Proxy-stage policies and blocked when they present unacceptable open-source risk.
Swift proxy repositories also contribute to Repository Health Check and Firewall reporting, alongside supported package ecosystems.
Bug fixes
Version 3.97.0 includes fixes across access control, database migration, high-availability startup, blob stores, repository formats, search, SAML, Docker, APT, npm, PyPI, Maven, LDAP, support ZIP creation, and REST APIs. Notable corrections include content-selector privilege evaluation, H2-to-PostgreSQL migration, rolling upgrades with long Maven index creation, corrupted blob-property repair, and audit logging for REST API tag associations.
Based on the official Sonatype release notes.
How Merito helps
Merito can help teams plan and validate self-managed Nexus Repository upgrades through Implementation Services and Premium Support. Review Sonatype expertise for related support options.
Merito is an authorized Sonatype reseller and services partner. Our Sonatype Nexus Repository team can scope licensing, sizing, and rollout for 97, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.