Sonatype Release Notes
44 release notes curated from 46 sources by the Releasebot Team. Last updated: Nov 4, 2026
- Nov 3, 2026
- Date parsed from source:Nov 3, 2026
- First seen by Releasebot:Nov 4, 2026
Sonatype Nexus Repository 3.98.0 Release Notes
Sonatype releases a Nexus Repository update that makes the streamlined Nexus One UI the default, extends Community Edition’s telemetry grace period, and improves component identification and container scanning. The release also fixes repository, security reporting, and administration issues.
What’s New and Noteworthy in This Release?
Nexus One UI Now the Default Experience
Sonatype Nexus Repository now uses the Nexus One UI as the default experience for all users. Previously available as an optional interface, Nexus One provides a more modern and streamlined way to navigate Nexus Repository, search and browse content, and manage repositories and administrative workflows. The updated design also aligns Nexus Repository more closely with other Sonatype products, helping teams move between solutions with a more consistent experience.
Nexus One is designed to reduce navigation friction and make frequently used information and actions easier to find. Improvements include clearer repository information, streamlined navigation, and system health status directly in the global header so administrators can identify conditions that need attention more quickly. Together, these changes make everyday repository management easier while providing a consistent foundation for continued improvements to search, browse, administration, and other workflows.
Users who prefer the previous experience can switch back to the Classic UI from UI Settings or by selecting Switch to Classic UI.
Extended Telemetry Grace Period for Community Edition
Sonatype Nexus Repository Community Edition now provides a 30-day grace period for required telemetry reporting failures, increased from 10 days. This extension gives Community Edition administrators more time to restore telemetry reporting before Nexus Repository switches to read-only mode, helping minimize disruptions to repository operations.
Repository Firewall: Improved Component Identification and Container Scanning Accuracy
Sonatype Repository Firewall now provides more accurate component identification for Python and Java packages, improving CVE reporting for Python packages that contain Red Hat backported security fixes. We have also expanded package detection for Go and APK packages and improved scanning accuracy for Red Hat hardened and OpenShift container images.
These improvements provide more complete visibility into components across supported environments, helping you assess security risks more confidently and prioritize remediation efforts based on more accurate vulnerability information.
Bug Fixes
Issue ID Description NEXUS-55963 JWT library dependencies are kept current, ensuring the distributed application contains only well-maintained transitive components. NEXUS-55862 Audit event persistence and the Audit page are now disabled by default, preventing unbounded growth of the audit_events table on busy instances; operators can enable both by setting nexus.previewui.audit.enabled=true. NEXUS-55730 NuGet V2 proxy repositories no longer generate redundant audit events or unnecessary database writes when re-fetching package metadata that has not changed upstream. NEXUS-55655 Sift appender log discriminators now stay within required length limits, ensuring task, replication, and blob store reconciliation log entries are written to their correct destinations without warnings appearing in the application log. NEXUS-55592 NuGet package downloads now consistently return the correct archive, even when Symbol Server processing is enabled. NEXUS-55520 Cargo group repositories now preserve the pubtime field in sparse-index entries, ensuring that Cargo's registry.global-min-publish-age setting correctly excludes recently published crate versions when resolving dependencies through a group repository, consistent with the behavior of a member proxy repository. NEXUS-55482 Audit event database storage is now controlled more efficiently, with the default retention period reduced from 90 to 30 days and asset download, attribute-change, and proxy metadata refresh events excluded from the audit_events table. These events remain available in audit.log. NEXUS-55364 Hosted Conda repositories with the “Disable redeploy” policy now accept subsequent package uploads and automatically refresh repository metadata files without errors. NEXUS-55294 Repositories configured with Disable Redeploy now correctly reject duplicate NuGet package uploads with HTTP 400. NuGet hosted repositories also correctly reject re-uploads of standard .nupkg packages containing embedded .pdb files. NEXUS-55284 Repository online/offline status displays consistently across all pages when viewing repository details. NEXUS-55283 Ephemeral log storage starts up reliably when fsGroup is configured in the pod security context for HA Helm chart deployments. NEXUS-55232 NuGet V2 OData feed responses now correctly represent unversioned dependencies without an explicit version range, preventing Chocolatey clients from unnecessarily re-downloading and re-executing install scripts for already-satisfied transitive dependencies. NEXUS-55186 The Data Repair Plan task log now includes detailed information for each planned action, showing the blob ID, repository name, file path, reason for the finding, and the specific action that will be taken when the plan is executed. NEXUS-55134 Alpine proxy repository creation in the New UI now works correctly, with the signing key and passphrase fields available for all three Alpine repository types (hosted, proxy, and group), and saved passphrases preserved when editing existing repositories. NEXUS-55128 Advanced cron scheduling in the Tasks UI now returns a clear validation message when an unsupported cron expression is submitted, without exposing internal error details or Java exception information. NEXUS-55077 Direct PUT uploads to a Conda hosted repository now return a clear error when the request URL includes a channel prefix (such as .../main/noarch/package.conda), preventing a situation where a successful upload response did not match the actual stored package location. NEXUS-55064 Maven component deletion from hosted repositories performs consistently regardless of the number of components sharing a groupId. NEXUS-55062 The npm asset Attributes tab now displays the complete set of package metadata fields, including description, author, license, and keywords, in both the Classic UI and Nexus One UI, restoring the visibility that was present prior to version 3.93.0. NEXUS-55035 The repository online/offline toggle button in the Preview UI now displays “Take Offline” and “Bring Online” labels that clearly communicate the action being performed. NEXUS-55020 “Allow Anonymous Docker Pulls” settings on Docker proxy repositories using path-based routing are now enforced correctly, requiring authentication when anonymous pulls are disabled. NEXUS-54976 Metrics endpoints (GET /service/rest/v1/monthly-metrics, GET /service/rest/v1/daily-metrics/egress, and GET /service/rest/v1/daily-metrics/storage) now return results for service accounts granted the nx-metrics-all privilege, without requiring full administrator permissions. NEXUS-54962 Automatic Malware Management findings for flagged components remain active across repeated task runs, with accurate component details preserved and no false retraction records created in the Malware Components report. NEXUS-54867 High-availability distributed cache indexes are created reliably on first startup, preventing cache write failures and ensuring HA cluster functionality after initial deployment. NEXUS-54763 Authenticated sessions on ARM64 deployments remain active for their full configured timeout duration, even under high concurrent request load. NEXUS-54739 Conan and Terraform repository metadata rebuilds correctly after a Data Repair task restores blobs, allowing clients to successfully download components without encountering 404 errors. NEXUS-54540 Search results through group repositories now return components correctly when users have read access to the group but not explicitly to its member repositories. NEXUS-54368 In high-availability clusters, scheduled tasks running on one node remain unaffected when another node restarts, preventing tasks like Rebuild Yum Repository Metadata from being incorrectly marked as interrupted. NEXUS-46259 Tag-based staging promotions complete successfully even when the destination repository already contains components associated with the same tag. FIRE-1227 The Enable Quarantine on All Proxies button is no longer displayed on the Malware Risk page, removing a control that previously appeared functional but had no effect. FIRE-879 Container scans of RedHat UBI images now correctly identify Python packages using their platform-specific variants, eliminating false positive reports that previously required manual investigation to distinguish from genuine security findings.Known Issues & Upgrade Guidance
This section captures known issues in the 3.98x line as well as upgrade guidance.
Open Known Issues
Impacted Version(s) Description Workaround (if available) 3.98.0 Sonatype is aware of an issue impacting Sonatype Nexus Repository 3.98.0 deployments that use PostgreSQL with a custom schema (a schema other than public). During an upgrade, database migrations may fail to add the required deleted_on and deleted_by columns because they only check tables in the public schema. As a result, Nexus Repository fails to start and reports the error ERROR: column "deleted_on" does not exist. With Nexus Repository stopped, manually add the missing deleted_on and deleted_by columns to the affected content tables in the custom PostgreSQL schema. Back up your database before making these changes. Contact Sonatype Support for assistance with the required SQL statements. If you use a custom PostgreSQL schema and cannot apply the workaround, do not upgrade to Nexus Repository 3.98.0. Original source - Oct 20, 2026
- Date parsed from source:Oct 20, 2026
- First seen by Releasebot:Oct 22, 2026
Sonatype Nexus Repository 3.97.0 – 3.97.1 Release Notes
Sonatype releases Nexus Repository 3.97 with the new Pro+ edition, malware protection and policy controls, a smoother search experience, service account tokens across repository formats, stronger chained proxy support, and extensive reliability fixes.
The Sonatype Nexus Repository 3.97.x release line includes exciting new features, enhancements, and bug fixes. Learn more in the sections below!
Release Timeline
- 3.97.0 – October 14, 2026
- 3.97.1 – October 20, 2026
Check Known Issues Before Upgrading
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?
Introducing Nexus Repository Pro+
Sonatype Nexus Repository now offers Pro+, a new edition that builds on Nexus Repository Pro by adding malware protection and policy controls to help organizations govern the open-source components entering their development environments.
Pro+ evaluates components requested by developers, build systems, and AI agents against Sonatype’s open source intelligence and your organization’s policies. It identifies and blocks malicious components, including emerging threats, before they enter your environment. Teams can also apply customized security, legal, architectural, and age-based policies at component intake, helping prevent unwanted components from reaching builds and reducing the need to address risks later in the development lifecycle.
Improved Search and Component Details in the Nexus One UI
Sonatype Nexus Repository now provides a more efficient search and component investigation experience in the Nexus One UI. Search results include accurate result counts, sorting by Last Updated, Name, or Repository, and URL-based search criteria that make searches easy to bookmark and share. Component details also provide clearer repository and component information, consistent timestamps, accurate file and repository counts, and Repository Health Check intelligence such as popularity, age, and license data. Together, these improvements make it faster to find components, understand their context, and share reproducible search results with other users.
Required Base Telemetry with Improved Administrator Guidance
Sonatype Nexus Repository now includes required base telemetry to provide consistent usage reporting. Administrators receive clear guidance for completing the required acknowledgement and verifying connectivity to the Sonatype telemetry service, along with a grace period before any repository restrictions apply.
A new Baseline Telemetry health check provides visibility into acknowledgement status, while actionable upload error messages help identify configuration, licensing, or connectivity problems.
Improved Chained Proxy Reliability Across Repository Formats
Sonatype Nexus Repository now provides more reliable chained proxy support for Ansible Galaxy, Hugging Face, Terraform, and Conda repositories. These improvements help organizations that route dependency traffic through multiple Nexus Repository instances, such as tiered, restricted, or air-gapped environments, keep package and model requests flowing through the expected repository path without exposing inaccessible upstream locations or interrupting authentication.
Ansible Galaxy proxy repositories now rewrite upstream artifact URLs for downstream clients, Hugging Face repositories preserve working pagination across proxy chains, and Terraform repositories provide the authentication challenge required for downstream Nexus Repository instances to complete credential negotiation. Conda proxy repositories also support preemptive authentication, allowing credentials to be sent with the initial upstream request and reducing unnecessary authentication round trips on cache misses. Together, these changes improve dependency availability and reduce failures caused by routing, pagination, and authentication differences between repository formats.
Conda Pre-emptive Authentication
Conda proxy repositories now persist and apply the httpClient.authentication.preemptive setting. If you configured this value through the REST API in an earlier release, review the repository configuration after upgrading and confirm that the setting reflects the authentication behavior you want.
Service Account Tokens Across All Repository Formats
Sonatype Nexus Repository now supports service account tokens across all supported repository formats, making it easier to use dedicated machine identities for CI/CD pipelines, build systems, and other automated workflows. Clients can authenticate with the same sat.* credential using either HTTP Basic or Bearer authentication, depending on the authentication method supported by the repository format and its native tooling.
This expanded support helps organizations reduce their reliance on human user credentials in automation and simplifies credential management across diverse development ecosystems. A service account can be assigned an appropriate role and used consistently across repository formats, giving teams a centralized way to manage, rotate, and revoke access for automated systems. For Basic authentication, use the service account name as the username and the service account token as the password; clients that support Bearer authentication can continue sending the token in the Authorization header.
Improved Remote Storage URL Validation for OCI Proxy Repositories
Sonatype Nexus Repository now validates Remote Storage URL values for OCI proxy repositories consistently with other proxy repository formats. When creating or updating an OCI proxy repository through the UI or REST API, the remote storage URL must begin with http:// or https://.
Nexus Repository also preserves the submitted URL in the stored repository configuration, providing consistent URL validation and configuration behavior across proxy repository formats.
Automatic Repository Health Check for Proxy Repositories
Sonatype Nexus Repository Health Check now operates automatically across proxy repositories, providing repository health insights without requiring administrators to use the Configure for all proxy repositories option.
This simplifies Repository Health Check configuration by automatically applying coverage across proxy repositories
Repository Firewall Support for Swift Proxy Repositories
Sonatype Repository Firewall now supports Swift proxy repositories in Sonatype Nexus Repository, extending policy evaluation and quarantine protection to Swift dependencies. When developers request Swift packages through a protected proxy repository, Repository Firewall evaluates the package against configured Proxy-stage policies and can block packages that introduce unacceptable open source risk before they enter development workflows.
Swift proxy repositories also integrate with Repository Health Check and Firewall reporting, giving teams visibility into policy violations and repository risk alongside other supported package ecosystems. This helps organizations apply more consistent software supply chain controls to Swift development while continuing to manage dependencies through Nexus Repository.
Bug Fixes
3.97.1 Bug Fixes
NEXUS-55897
Startup on PostgreSQL databases with non-English server locales completes successfully when upgrading to 3.97.x
NEXUS-55699
Proxy repository cache tokens now synchronize correctly across all nodes in an HA cluster, ensuring that components with a maximum age of -1 are served from cache without triggering repeated upstream requests after cache invalidation.
NEXUS-55356
PyPI proxy repositories handle high volumes of concurrent simple index requests reliably without triggering out-of-memory errors.
NEXUS-54725
Concurrent Docker proxy pulls of cached tag manifests complete reliably without exhausting request threads or database connections, even for repositories with large numbers of signature artifacts or multi-platform images.
3.97.0 Bug Fixes
NEXUS-55658
HEAD requests to npm group repositories return successful responses instead of HTTP 500 errors when member proxy repositories are included.
NEXUS-55428
PyPI proxy repositories with Preserve Encoded Characters enabled now correctly install packages when proxying through another Nexus instance, resolving 404 errors that occurred for packages whose index pages were fetched without a required trailing slash.
NEXUS-55223
PyPI proxy repositories now return the correct format (HTML or JSON) to each pip client when concurrent requests for the same Simple index page arrive with different Accept headers.
NEXUS-55200
OCI proxy repository blob pulls now complete successfully when the remote registry redirects to a signed storage URL (such as Azure Blob Storage SAS URLs) containing consecutive slashes in the path, preserving the exact redirect path bytes so that upstream signature validation succeeds.
NEXUS-55030
Authentication rate limiting now correctly releases blocked accounts after the advertised Retry-After interval elapses, and successful logins clear the lockout state so automated clients and users can recover without administrator intervention.
NEXUS-55004
Cleanup policies now remove eligible components from RubyGems repositories on PostgreSQL as expected, rather than silently reporting zero assets cleaned up.
NEXUS-54977
NuGet V3 group repositories now return complete version lists, including packages published with release qualifiers alongside their base versions.
NEXUS-54915
"Retain last N versions" cleanup policies now correctly preserve the newest component versions across npm, PyPI, Helm, NuGet, RubyGems, Go, Yum, Terraform, Swift, Apt, and Pub repositories when repositories contain components published before and after a version-normalization format change introduced in 3.94.
NEXUS-54913
Ansible Galaxy proxy repositories correctly forward collection version and pagination requests upstream, allowing ansible-galaxy clients to resolve and install collections without receiving HTTP 404 errors.
NEXUS-54855
User token lookup via GET /service/rest/v1/security/user-tokens/tokens now accepts nameCode as the official query parameter, with the previously undocumented lowercase namecode retained as a backward-compatible alias.
NEXUS-54839
Conda hosted repositories now automatically generate an empty noarch/repodata.json metadata file upon creation, allowing Conda clients to browse and install packages without requiring a noarch package to be uploaded first.
NEXUS-54837
HuggingFace XET presigned URL sweep task logging runs quietly in the background by default, eliminating repetitive log entries that appeared every 60 seconds and caused unnecessary noise in customer logs.
NEXUS-54829
Audit log entries for assets removed by cleanup tasks now include the full asset path, type, and blob store location, providing the complete details needed for selective content recovery.
NEXUS-54817
Go hosted repositories now correctly resolve module versions containing uppercase prerelease characters (such as v1.1.2-PRE-RELEASE) when requested by a standard Go client via GOPROXY.
NEXUS-54771
OCI proxy repositories now enforce the same http:// or https:// remote URL requirement as all other proxy formats, ensuring consistent validation behavior across both the UI and REST API.
NEXUS-54764
Anonymous Docker pulls continue to work correctly after running the Admin – Delete orphaned API keys task, with no authentication failures, rate-limit blocking, or service restart required.
NEXUS-54760
Ansible Galaxy proxy repositories now return Content-Type: application/json for v3 collection metadata endpoints, ensuring compatibility with strict REST clients, API gateways, and content-type-aware tooling.
NEXUS-54753
OCI repository creation and updates complete successfully when subdomain routing is configured on instances that also host legacy Docker repositories.
NEXUS-54715
HEAD requests to npm group repositories return correct responses when the requested package is not yet cached locally.
NEXUS-54691
User tokens remain valid after upgrading from an OrientDB-based installation that was migrated to H2 or PostgreSQL.
NEXUS-54638
XML processing in WebFlux endpoints now correctly enforces configured memory limits when parsing asynchronous XML payloads.
NEXUS-54604
Data Repair Plan tasks against S3 blob stores now scan blob attributes concurrently, eliminating the serial bottleneck that caused reconciliation workers to sit idle and made large-scale repair plans impractical to complete.
NEXUS-54602
Sensitive session tokens in Set-Cookie response headers (including Keycloak identity cookies) are now masked at write time in all log files, rolled archives, Support ZIPs, and cloud JSON logs, with an option to extend masking to additional custom cookie names via the nexus.log.mask.cookies system property.
NEXUS-54601
Large Docker and OCI layer commits to S3-backed blob stores complete successfully during concurrent or high-volume pushes.
NEXUS-54596
Cargo group repository config.json requests are served efficiently without creating or storing unnecessary assets on each request.
NEXUS-54579
The Cleanup Policy Preview repository dropdown now consistently displays all repositories matching the selected format across all supported formats — including npm, PyPI, Go, Helm, NuGet, Yum, RubyGems, Terraform, Swift, Apt, and Pub.
NEXUS-54576
NuGet package publishing to hosted repositories with Disable Redeploy now completes successfully when multiple packages share common embedded PDB files, and packages containing PDBs alongside DLLs are correctly stored as standard NuGet packages rather than symbol packages.
NEXUS-54572
NuGet symbol assets (.snupkg and .pdb files) are now stored with the required package attributes, enabling reliable search and preventing HTTP 500 errors during symbol package operations.
NEXUS-54571
Ansible Galaxy collection downloads through chained proxy repositories now complete successfully, with metadata URLs rewritten to reflect the downstream proxy’s address rather than exposing upstream host information that clients cannot reach.
NEXUS-54570
npm proxy repositories in HA clusters now return consistent responses across all nodes when a previously unavailable package becomes accessible, eliminating the stale 404 responses that persisted on individual nodes until cache expiration.
NEXUS-54568
The Keep database records when blob is missing checkbox on the Verify and Repair Data Consistency task now renders as checked by default for tasks migrated from earlier versions, preventing unintended deletion of database records when saving unrelated task settings.
NEXUS-54563
The Repair - Execute Data Repair Plan task now successfully removes orphaned database records for assets whose blob files are missing, preventing recurring MissingBlobException errors when those assets are subsequently requested.
NEXUS-54558
PyPI proxy repositories configured with an empty indexPath via the REST API will now correctly route upstream requests without appending /simple/ to the URL.
NEXUS-54552
npm package metadata browse nodes remain visible and deletable after all associated tarball assets are removed from a proxy repository.
NEXUS-54550
Docker proxy repositories backed by Amazon ECR accept pre-generated ECR Docker tokens (obtained via aws ecr get-login-password) as valid HTTP Basic authentication credentials when saving repository configuration.
NEXUS-54526
npm proxy repositories now successfully download packages from registries that redirect to Azure Blob Storage, with authentication credentials correctly scoped to each host during cross-domain redirects.
NEXUS-54469
Docker proxy repository responses now return a stable Last-Modified header for cached manifests, ensuring tools like Dependabot correctly recognize unchanged images instead of treating every request as newly modified content.
NEXUS-54468
npm packument responses of any size are now gzip-compressed when clients request it, eliminating the previous 10 MiB ceiling above which compression was silently skipped.
NEXUS-54465
Email server configuration via the REST API now correctly enforces application/json as the required content type, and PUT requests to /v1/email are accepted and validated as expected.
NEXUS-54434
Browser refresh and direct deep links to permission-gated pages now load the intended page reliably, without redirecting to the Welcome page, even for users with large role sets.
NEXUS-54322
User account changes — deletions, deactivations, and role updates — now take effect across all nodes in an HA cluster within seconds, rather than remaining stale on remote nodes for up to two minutes.
NEXUS-54233
Browse tree updates for newly uploaded Raw components now reflect across all repositories promptly, even when instances contain tens of millions of components under high concurrent upload activity.
NEXUS-54229
In clustered PostgreSQL deployments, Sonatype Nexus Repository now propagates repository configuration changes across nodes immediately by default, so consecutive create-and-use requests routed to different nodes no longer fail while waiting for the polling interval.
NEXUS-54208
OIDC logout now terminates the user’s session at the identity provider (such as Keycloak), ensuring that subsequent SSO login attempts require re-authentication as expected.
NEXUS-54132
Docker proxy repositories without configured credentials now log anonymous bearer token exchange failures at the debug level instead of generating misleading warning-level log entries.
NEXUS-54127
Deleting a shared layer blob or a manifest-list child manifest in Docker and OCI hosted repositories now returns HTTP 409 when the asset is still referenced by one or more live manifests, preventing the deletion from proceeding until all referencing manifests are removed first.
NEXUS-53780
Maven group repository metadata merges correctly when Gradle clients issue HEAD requests, ensuring all member repository versions are included in subsequent GET responses.
NEXUS-53722
The classic UI Administration → Repositories list loads significantly faster on instances with large numbers of repositories, as size metrics are now retrieved in a single bulk query instead of one query per repository.
NEXUS-49734
A new REST API at /service/rest/v1/security/oauth2/users enables administrators to create, read, update, and delete locally cached OAuth2 user records directly in the database without forwarding any changes to the remote identity provider.
NEXUS-46386
The HA Helm chart now sets securityContext on all containers, enabling successful pod deployment in Kubernetes environments that enforce the PodSecurity restricted profile, such as vSphere with Tanzu and OpenShift.
NEXUS-44892
PyPI proxy repositories now support a configurable suffix field in the REST API, allowing users to specify custom index sub-paths (such as /api/pypi/simple) when proxying non-standard PyPI-compatible registries like Artifactory or GitLab.
FIRE-774
npm proxy package metadata for frequently requested packages is now served from pre-rendered cached responses, reducing latency on repeated lookups by eliminating redundant parsing of upstream package data on every request.
FIRE-762
Cleanup policy removal of cached Docker images now triggers deletion of the corresponding container evaluation reports in Repository Firewall, preventing orphaned report accumulation on the IQ Server.
Known Issues & Upgrade Guidance
This section captures known issues in the 3.97.x line as well as upgrade guidance.
Open Known Issues
Impacted Version(s): 3.96.0 – 3.97.0
Sonatype is aware of an issue impacting Sonatype Nexus Repository deployments using PostgreSQL. High volumes of audit events can cause excessive growth of the audit_events table, leading to increased database storage consumption. The default 90-day retention period and large attribute-change records can further contribute to database growth.
Workaround: Reduce the audit event retention period using the Retention (days) field in the Audit capability configuration. To reduce the size of newly generated audit events, set nexus.audit.attribute.changes.enabled=false in the nexus.properties file. This setting does not remove existing audit events or change the configured retention period.
Audit Event Persistence Disabled by Default in 3.97.1
Note that audit event persistence is disabled by default as of version 3.97.1. If you are on version 3.97.1 or beyond, you do not need to set nexus.audit.attribute.changes.enabled=false in the nexus.properties file
Resolved Known Issues
Impacted Version(s): 3.97.0
Version in which Issue is Resolved: 3.97.1
In some PostgreSQL-backed deployments, including but not limited to those using a non-English database locale, the upgrade may not add the deleted_on column to the PostgreSQL repository table. Nexus Repository 3.97.0 then fails to start because it cannot find the column.
Original source All of your release notes in one feed
Join Releasebot and get updates from Sonatype and hundreds of other software products.
- Sep 1, 2026
- Date parsed from source:Sep 1, 2026
- First seen by Releasebot:Sep 2, 2026
Sonatype Nexus Repository 3.96.0 Release Notes
Sonatype releases Nexus Repository 3.96.0 with Azure direct downloads, richer Nexus One UI administration, stronger audit and user management, better proxy and npm performance, and a long list of security and reliability fixes.
What’s New and Noteworthy in This Release?
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
- NEXUS-54717: HTTP HEAD requests to Docker manifest endpoints now update the lastDownloaded timestamp, ensuring actively used images are not incorrectly identified as unused by cleanup policies.
- NEXUS-54508: The Firewall Mode option is no longer displayed for repository formats that do not support Sonatype Repository Firewall, preventing unsupported configurations.
- 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 cargo fetch operations.
- 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 contentMaxAge value when starting, avoiding unnecessary warning messages.
- 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.malware.risk.enabled=false now consistently suppresses the Malicious Risk on Disk dashboard banner.
- NEXUS-54043: npm dist-tags, including latest, are now preserved when packages are imported from external files, ensuring clients receive the intended package version.
- NEXUS-54026: npm hosted repository migrations now preserve dist-tags.latest, ensuring unversioned package installs receive the most recently published release.
- 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 status, allowing supported user updates without requiring unrelated profile fields.
- 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.
- August 2026
- No date parsed from source.
- First seen by Releasebot:Aug 6, 2026
2025 Release Notes
Sonatype Nexus Repository adds a 2025 release roundup with major cloud and self-hosted updates, including a new repository browse trim capability, broad bug fixes, performance improvements, and a fix for a data-loss issue in Verify and Repair tasks.
This page contains a list of 2025 Sonatype Nexus Repository releases, links to each release's release notes, and a brief list of major changes per release.
Note that while we strive to fully document new features before releasing them to our Cloud environments, there may be occasional delays. In such instances, we will update this page with links to the relevant help documentation as soon as it becomes available.
Summary of Major Nexus Repository Changes in 2025
The following table lists major changes to Sonatype Nexus Repository in 2025. Consider these changes when upgrading to a new version. Select a self-hosted release to see the fully featured 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.This cloud release contains the following features and bug fixes, which will be provided to self-hosted customers in a future release:
Features:
- New Repository: Browse Trim capability and a Repair - Repository trim browse tree task.
Bug Fixes:
- NEXUS-49805 – The login screen no longer displays the instructions for resetting the initial admin password after it has already been reset.
- NEXUS-49789 – Importing a previously exported Raw hosted repository on Windows now correctly preserves the original directory structure instead of merging it into the asset name.
- NEXUS-49742 – Staging move operations on PostgreSQL now perform faster and clean up empty browse nodes more efficiently.
- NEXUS-49718 – UI load times have been improved for users with a large number of assigned privileges by optimizing how permissions are calculated and checked during login.
- NEXUS-49714 – Tag-based searches and staging move operations in High Availability environments now correctly handle tag names in a case-insensitive manner.
- NEXUS-49613 – Component searches in High Availability environments now return only exact matches when no wildcards are used.
- NEXUS-49566 – R proxy repositories now support SHA256 content-addressable package archives.
- NEXUS-49472 – The UI now allows uploading assets to directory paths that include uppercase letters.
- NEXUS-49424 – The Verify and Repair Data Consistency task now accurately reports elapsed time in logs.
- NEXUS-49369 – The frontend REST API now returns only active Nexus modules.
- NEXUS-49226 – Refreshing a task log using the UI refresh icon now correctly loads the log without triggering a 404 error.
- NEXUS-49156 – The Repositories page now displays the Size column as long as at least one repository format has completed the blob size copy task.
- NEXUS-49142 – The login process now uses a dynamic timeout based on UI settings.
- NEXUS-49069 – Uptime log entries once again include Nexus version information.
- NEXUS-48982 – Concurrent requests to the same asset across High Availability nodes no longer result in errors.
- NEXUS-48739 – npm proxy repositories now correctly update package metadata when a cached package is deleted locally.
- NEXUS-48504 – The Search API now correctly returns blobCreated and blobStoreName values for assets.
- NEXUS-48393 – Cleanup policies using regex patterns with quantifiers now produce consistent and accurate results between preview and execution.
- NEXUS-47174 – Compact Blob Store tasks can now run concurrently across different blob stores.
- NEXUS-46878 – Removed default memory-related JAVA_OPTS values from the Docker image.
- NEXUS-46839 – Helm hosted repositories now correctly block redeployment of .prov files when the disable redeploy policy is enabled.
- NEXUS-46163 – Repository target privileges migrated from Nexus Repository 2 are correctly transformed and visible in the Roles UI.
- NEXUS-45941 – The REST API for creating Maven group repositories now correctly honors the specified versionPolicy.
- NEXUS-45291 – Yum group repository logs now include the specific member repository name when an ETag is missing.
- NEXUS-45234 – Repository content selector privileges created via the REST API with the ALL action are now correctly displayed in the UI with all actions selected.
- NEXUS-44316 – Search API requests that previously failed with a 500 error due to orphaned records in the search_components table are now handled gracefully. An upgrade task removes these invalid entries to restore search functionality without manual intervention.
- NEXUS-41564 – Docker Garbage Collection task logs now include more detailed information about deleted and retained assets.
- NEXUS-40516 – UI searches performed by non-admin users now correctly display and navigate to the expected components and assets within group repositories.
- NEXUS-36868 – Helm proxy repositories now correctly preserve string values like appVersion from index.yaml.
- NEXUS-31898 – Warnings caused by expected BypassHttpErrorException conditions during Docker proxy operations are now logged at the DEBUG level instead of WARN.
- NEXUS-26593 – The Docker - Delete incomplete uploads task no longer logs unnecessary WARN messages when encountering already soft-deleted blobs.
- NEXUS-25286 – Nexus Repository now starts successfully even if a Docker repository is configured to use the same port as the main application connector.
December 17, 2025 cloud release, included in self-hosted version 3.88.0 (January 13, 2026).
Additional releases and detailed bug fixes and features are listed for versions 3.87.1, 3.87.0, 3.86.0, 3.85.0, 3.84.1, 3.84.0, 3.83.2, 3.83.1, 3.83.0, 3.82.1, 3.82.0, 3.81.1, 3.81.0, 3.80.0, 3.79.1, 3.79.0, 3.78.3, 3.78.2, 3.78.1, 3.78.0, 3.77.2, 3.77.1, 3.77.0, 3.76.1, 3.76.0, and 3.70.4 with various bug fixes, new features, known issues, and important notices.
- Sonatype Nexus Repository Cloud was introduced on July 16 2025; Cloud Release Date only applies to versions after this date. All releases before July 2025 were self-hosted only.
- Aug 5, 2026
- Date parsed from source:Aug 5, 2026
- First seen by Releasebot:Aug 6, 2026
Sonatype Nexus Repository 3.95.0 Release Notes
Sonatype adds broader repository support and cleanup controls across Composer, NuGet, PyPI, Hugging Face, Amazon ECR, and Firewall, while improving the Nexus One UI, performance, and reliability with many bug fixes.
What’s New and Noteworthy in This Release?
Added Support for Composer Hosted and Group Repositories
Sonatype Nexus Repository now provides hosted and group repository support for Composer, completing its native support for the PHP package ecosystem. In addition to existing proxy repository support, you can now host your own Composer packages, aggregate hosted and proxy repositories into a single group repository, and manage PHP artifacts alongside the rest of your organization's open source and internal components.
For full details, see the Composer Repositories help documentation.
NuGet Hosted, Proxy, and Group Repositories Support Chocolatey Registry and Microsoft Symbol Server
Sonatype Nexus Repository now offers broader support for NuGet ecosystems by adding compatibility with Chocolatey registries and .NET symbol packages. You can now proxy and host Chocolatey packages with NuGet repositories and expose them through group repositories, giving developers a single endpoint for accessing both standard NuGet and Chocolatey packages. This simplifies repository management while making it easier to distribute and consume Windows software packages across your organization.
Nexus Repository also now supports .snupkg symbol packages and the Microsoft Symbol Server Protocol (SymSrv/SSQP), enabling on-demand delivery of Portable PDB (.pdb) files to supported debuggers. Symbol server functionality is available for hosted, proxy, and group NuGet repositories, helping development teams improve debugging workflows while managing application packages and debugging symbols from a single repository platform.
For full details, see the NuGet Repositories help documentation.
Hugging Face Proxy Repositories now Support the Latest huggingface_hub Client Workflows
Sonatype Nexus Repository now supports the latest Hugging Face client workflows by adding compatibility with the /tree/ API endpoint and inbound Bearer token authentication. These enhancements restore compatibility with the official huggingface_hub Python library versions 1.0 and later, including the changes introduced in version 1.22 that require the /tree/ endpoint for snapshot_download() and hf download.
Nexus Repository also supports the Bearer token authentication model used by newer versions of the client, eliminating the need to rely on legacy Basic authentication.
PyPI Proxy Repository Enhancements Improve Compatibility with Private and Version-Specific Repositories
PyPI proxy repositories now support repository-specific URL encoding rules, allowing you to apply format-specific behavior where needed. For example, PyPI repositories that use PEP 440 local version identifiers can encode + as %2B without affecting other repository formats. Existing global URL encoding configurations continue to work unchanged, so no action is required for current deployments.
Nexus Repository also now supports preemptive authentication for PyPI proxy repositories. This enhancement enables successful proxying of private PyPI repositories that do not issue authentication challenges, including GitLab.com-hosted PyPI repositories. Together, these improvements simplify integration with private package registries and help ensure more reliable access to Python dependencies across diverse repository implementations.
Cleanup Policy Enhancements
Sonatype Nexus Repository now provides more flexible cleanup policy management to help you control repository growth across a wider range of package formats. The Retain last N versions capability is now available for all versioned repository formats that support version semantics. This includes the following formats:
- Apt
- Docker
- Go
- Helm
- Maven
- npm
- NuGet
- Pub
- PyPI
- RubyGems
- Swift
- Terraform
- Yum
This enhancement helps organizations with high-volume CI/CD pipelines manage storage growth consistently across repositories without relying on custom automation.
Cleanup policy administration is also more streamlined. You can now assign a cleanup policy to multiple repositories directly from the policy configuration, view associated repositories in one place, and preview cleanup behavior across those repositories without editing each repository individually.
In addition, Nexus Repository introduces new cleanup policy REST API functionality for targeted cleanup execution, allowing you to run cleanup for a single repository on demand. The API supports synchronous dry runs that report the number of matching components and asynchronous cleanup execution with status tracking, giving administrators greater control over cleanup operations while avoiding repository-wide scheduled runs.
Improvements to the Nexus One UI
The Nexus One UI includes a broad set of usability, accessibility, and reliability improvements across core workflows. This release completes support for task management in the Nexus One UI, allowing you to configure, schedule, run, monitor, and manage all supported task types without switching to the legacy interface. Task configuration forms now provide a more consistent experience across task types while preserving compatibility with existing task definitions. Configuration created in either interface remains synchronized, making it easier to transition between experiences during adoption.
This release also improves the overall Nexus One UI experience with refinements to navigation, search, dashboard, browsing, and user management workflows. Updates include improved accessibility, more consistent interface behavior, clearer feedback throughout common tasks, and continued modernization of the underlying UI architecture. Together, these enhancements provide a more polished and reliable experience while establishing a stronger foundation for future Nexus One UI improvements.
Amazon ECR Proxy Repositories Now Support Temporary AWS Credentials
Sonatype Nexus Repository now supports temporary AWS credentials for Amazon ECR proxy repositories, making it easier to authenticate with modern AWS identity services. You can now configure an optional AWS session token alongside your AWS access key and secret key, enabling authentication with credentials issued by AWS Security Token Service (STS) and AWS IAM Identity Center (SSO). Existing configurations that use long-lived AWS access keys continue to work without changes.
Firewall Success Metrics Dashboard
Sonatype Repository Firewall now includes a new Firewall Success Metrics dashboard in Enterprise Reporting, giving organizations a clearer understanding of how effectively Firewall protects their software supply chain. By bringing key operational and security insights together in one place, the dashboard helps teams measure the impact of their security policies, identify trends in component risk, and determine whether quarantine workflows are reducing exposure to malicious or vulnerable components. At a glance, teams can monitor metrics such as component evaluations, quarantines, malicious component detections, waivers, and quarantine response times to understand how Firewall is performing over time.
With greater visibility into Firewall activity, security, platform, and engineering teams can make more informed decisions about policy tuning, prioritize response efforts, and demonstrate the value of their software supply chain security program. Interactive filtering and detailed reporting make it easier to investigate quarantine trends, understand why components are blocked, monitor waiver usage, and identify opportunities to reduce review times and continuously improve how open source risk is managed across the organization.
For full details, see the Firewall Success Metrics Dashboard help documentation.
Configure the Firewall for Docker Layer Download Timeout
Sonatype Nexus Repository now lets you configure the timeout used by Firewall for Docker when downloading container image layers during policy evaluation. Previously, this timeout was fixed at 10 minutes, which could prevent image evaluation from completing in environments where legitimate network conditions, such as proxy-based antivirus scanning or other network inspection, significantly increase download times. You can now adjust the timeout to up to 240 minutes by setting the nexus.firewall.container.download.timeout.minutes system property to better accommodate your environment while maintaining Firewall for Docker protection for large or slow-to-download images.
Bug Fixes
NEXUS-54092
Terraform module downloads from hosted repositories now succeed for all valid archive formats (.tgz, .tbz2, and .txz), including modules with standard semantic version numbers such as 4.1.1.NEXUS-54089
Cosign signing and attestation against Docker hosted repositories with large numbers of manifests now complete in seconds, thanks to a database path index and a scan cap that prevents exhaustive manifest searches during metadata propagation.NEXUS-53975
Terraform proxy repositories now support a "Use pre-emptive authentication" option, enabling credentials to be sent on the first request to an upstream Nexus instance rather than waiting for a challenge header that never arrives.NEXUS-53923
During upgrades, the asset blob reference migration check runs as a lightweight background task after startup rather than as a blocking scan on the main startup thread.NEXUS-53898
The copy button in the classic UI Browse › Repositories URL column now opens the copy dialog correctly, allowing repository URLs to be copied to the clipboard.NEXUS-53883
Components moved via staging operations retain their normalized version data, allowing Docker cleanup retain-n policies to evaluate and remove eligible components correctly.NEXUS-53874
Dart/Pub hosted repositories now accept package names beginning with an underscore (for example, _my_private_package), aligning with the official pub.dev specification.NEXUS-53833
Browsing the /simple// index on PyPI hosted repositories no longer writes blob files to the blob store on each request, eliminating spurious updated-uploaded audit events and uncontrolled disk growth between Compact Blob Store task runs.NEXUS-53830
Docker layer uploads to Azure blob store repositories now use Azure server-side copy for single-chunk transfers, eliminating the redundant download-and-re-upload cycle that previously caused large layers to take roughly twice as long to push.NEXUS-53828
Transient GCS 503 backend errors encountered during blob attribute writes in doDelete() are now retried with exponential backoff, allowing Docker uploads and similar operations to complete successfully instead of failing immediately.NEXUS-53826
Terraform, Ansible Galaxy, and Swift hosted repositories no longer cache "not found" responses, so post-upload verification requests correctly return the uploaded asset instead of a stale 404.NEXUS-53816
Concurrent repository deletions now complete successfully without leaving repositories in an unrecoverable STOPPED state that previously required a full restart to resolve.NEXUS-53778
Requests carrying a structurally invalid Authorization: Basic header—such as an unexpanded ${NPM_TOKEN} placeholder in an npm .npmrc or CI config—now receive an HTTP 400 Bad Request response instead of 401.NEXUS-53755
The top-level search More Criteria menu now includes Name and Version fields at the generic level, allowing users to filter search results by version across all package formats without navigating into format-specific sections like Composer Repositories.NEXUS-53733
PyPI proxy repositories now send the correct upstream ETag in outbound If-None-Match headers, allowing PyPI to return 304 Not Modified responses instead of forcing full re-downloads, and no longer write a new blob to the blob store on every simple index request.NEXUS-53719
Permission checks for users authenticated through external realms (SAML, LDAP, Crowd, OAuth2) now resolve role-to-permission mappings a single time per login rather than once per privilege checked, eliminating the ~20-second UI load delay experienced by users with large role sets.NEXUS-53697
NuGet hosted repositories now return 206 Partial Content with correct Content-Range headers when clients request byte ranges, eliminating full-package downloads for partial-content requests against local blob stores.NEXUS-53670
R proxy repositories now correctly handle CDN-prefixed content-addressable archive names from r-universe and R-multiverse, and the R-multiverse pollinator resolves package details dynamically from the live index rather than relying on hardcoded versions.NEXUS-53606
Improved JAX-RS client error logging to reduce noise in server logs.NEXUS-53599
Blob store metrics—including BLOB COUNT and USED SIZE—are preserved correctly when a blob store is promoted to a group, eliminating the need to manually run the Recalculate Blob Store Storage task.NEXUS-53586
The Source dropdown selection in Settings > Security > Users is now preserved after deleting a user, keeping the filtered list on the selected realm instead of reverting to Local.NEXUS-53571
Requests carrying a malformed Base64 Authorization header now receive a 401 Unauthorized response instead of an HTTP 500 error.NEXUS-53496
Breaking Change: Ansible Galaxy hosted repositories now return HTTP 409 with a Galaxy-compatible error body when a duplicate collection version is published to a write-once repository; automation or tooling that previously handled the HTTP 400 response must be updated accordingly.NEXUS-53492
PyPI group repositories now serve a single authoritative index entry per filename, giving hosted members precedence over proxy members so pip 26's hash verification receives consistent checksums and installs patched components successfully.NEXUS-53486
The Default Role Realm is now preserved across node shutdowns, preventing it from being inadvertently removed from active realm configuration during AWS ASG instance refreshes or ECS task changes.NEXUS-53476
Existing cached .whl.metadata assets are automatically migrated to application/octet-stream on upgrade, and PyPI proxy repositories now serve .whl.metadata files with the correct content type to prevent WAF rejections and checksum mismatches.NEXUS-53468
Terraform proxy repositories now correctly resolve components from providers with long alphanumeric namespaces without misidentifying the namespace as an authentication token.NEXUS-53463
PyPI group repositories automatically invalidate their cached index when Sonatype Repository Firewall (PCCS) filtering is toggled for any member proxy, ensuring all available package versions are served immediately.NEXUS-53458
The Settings → Repositories page loads in normal time during post-upgrade blob-size copy task execution because task completion checks now cache negative results for 30 seconds.NEXUS-53457
The "Secrets - Migrate secrets" upgrade task now completes successfully for repositories that reference non-existent cleanup policies, automatically removing stale policy names during upgrade.NEXUS-53394
Transient GCS 503 backend errors during Compact Blob Store operations are now retried with exponential backoff, and compaction tasks that fail to hard-delete blobs correctly report as failed.NEXUS-53383
Pub package uploads now consistently identify the root pubspec.yaml as the authoritative metadata source regardless of archive entry order.NEXUS-53373
Telemetry script fetches in air-gapped environments now time out within a configurable window (default 5 seconds) instead of blocking the UI for up to 80 seconds, with stale cached content served as a fallback.NEXUS-53343
Repository search indexes remain queryable throughout the "Repair - Rebuild repository search" task, with orphaned records cleaned up only after re-indexing completes.NEXUS-53338
Pull replication now bypasses the proxy staleness check for modified assets, ensuring updated content is fetched immediately from the source.NEXUS-53317
Stale repodata entries in the browse tree of YUM group and proxy repositories are automatically removed when merged metadata is regenerated.NEXUS-53306
Breaking Change: The Preview UI Firewall column now accurately reflects each proxy repository's protection state, and customizations referencing previous endpoint constants must be updated.NEXUS-53300
NuGet v3 hosted repository query results are now correctly returned for users whose Content Selector privilege includes a path condition on PostgreSQL deployments.NEXUS-53265
Breaking Change: Content selectors using mixed and/or expressions without parentheses must be rewritten with explicit parentheses before upgrading.NEXUS-53263
Breaking Change: Repositories relying solely on Repository Content Selector privileges require a rebuild of repository search indexes after upgrade to restore correct search visibility.NEXUS-52995
When PCCS age-based policy filtering quarantines npm package versions, diagnostic logging now captures the catalog date and policy condition details for each affected version.NEXUS-52942
Pagination Link headers for Docker group repositories accessed via repository URL path now correctly reference the group repository path rather than the internal member proxy path.NEXUS-52934
Assets in group repositories remain accessible throughout a Change Repository Blob Store migration because source blobs are retained until database references are fully updated.NEXUS-52826
Group repositories now display an aggregated Firewall Report status based on their proxy members, and the Firewall Report column header is correctly marked as non-sortable.NEXUS-52283
The Hugging Face proxy now implements the /tree/{revision} endpoint, enabling snapshot_download() and hf download to work with huggingface_hub 1.22.0+ even for repositories with more than 1,000 files.NEXUS-52176
IQ Server connection failures now return actionable error messages instead of the previous generic compatibility message.NEXUS-51938
All nodes in an HA cluster now immediately evict their shared HTTP connection pool when proxy or other HTTP client settings change.NEXUS-51661
Trailing wildcard searches with fewer than three characters before the wildcard now return HTTP 400 with a clear error message instead of silently returning empty results.NEXUS-51526
The Repair - Data Repair Plan task now removes orphaned database records for assets whose .bytes file is missing when "Keep db records" is unchecked.NEXUS-51524
The Repair - Execute Data Repair Plan task now displays the complete plan count by retrieving aggregated statistics from a new server-side summary endpoint.NEXUS-51451
Conan proxy repository search now returns cached results successfully when the remote is manually blocked instead of returning a 500 error.NEXUS-51368
Raw repository searches by filename now return correct results when the filename contains a period character.NEXUS-50783
Removing a member from a Maven group repository now completes quickly, with orphaned asset cleanup running in the background.NEXUS-37620
The Repair - Rebuild Maven repository metadata task now regenerates missing checksum files for maven-metadata.xml when checksum rebuilding is enabled.NEXUS-33892
Group repository caches are automatically invalidated when routing rules are assigned, removed, or modified on any member proxy repository.NEXUS-29245
npm dist-tag add and npm dist-tag rm commands now work against group repositories by delegating tag operations to the configured writable member repository.NEXUS-29099
Task log file handles are now released immediately upon task completion, preventing accumulation of open file descriptors.NEXUS-28581
When thread cooperation limits are exceeded during high-concurrency NuGet proxy requests, logs now emit a detailed warning message identifying the limit and the configuration property to adjust.FIRE-601
Sonatype Repository Firewall enforcement remains active on all High Availability cluster nodes after a Zero Downtime Upgrade, with repository configuration automatically refreshed following the deferred database migration.FIRE-519
Original source
The Automatic Malware Management task now completes successfully against IQ Server versions earlier than 204 by gating the quarantineEnabled field on the connected IQ Server version before sending ad-hoc evaluation requests. Similar to Sonatype with recent updates:
- Grammarly release notes12 release notes · Latest Aug 13, 2026
- Obsidian release notes125 release notes · Latest Nov 12, 2026
- Perplexity release notes33 release notes · Latest Nov 6, 2026
- Gitlab release notes170 release notes · Latest Nov 19, 2026
- Eslint release notes46 release notes · Latest Nov 13, 2026
- MiniMax release notes55 release notes · Latest Nov 11, 2026
- Jul 15, 2026
- Date parsed from source:Jul 15, 2026
- First seen by Releasebot:Jul 16, 2026
July 15, 2026
Sonatype Nexus Repository Cloud ships bug fixes with no new features.
This Sonatype Nexus Repository Cloud release does not include any new features.
See Nexus Repository Cloud Bug Fixes.
Original source - Jul 15, 2026
- Date parsed from source:Jul 15, 2026
- First seen by Releasebot:Jul 16, 2026
Nexus Repository Cloud Bug Fixes
Sonatype releases Nexus Repository Cloud bug fixes that improve search filtering, package downloads, UI performance, Firewall Report status, and upgrade handling, while reducing noisy alert logs and correcting repository read behavior across PyPI, NuGet, and cached metadata.
This page contains a list of bug fixes included in our 2026 Sonatype Nexus Repository Cloud releases.
New features and enhancements are covered in the
2026 Sonatype Nexus Repository Cloud Release Notes.July 15, 2026
This Sonatype Nexus Repository Cloud release includes the following bug fixes:
- NEXUS-53833 – PyPI hosted repository simple index requests no longer create blob store files or updated-uploaded audit log entries during read operations.
- NEXUS-53755 – The top-level search More Criteria menu now includes Name and Version fields, making version-based filtering available across all package formats.
- NEXUS-53739 – JVM heap usage alerts are now logged at WARN level during normal G1GC major collections, reducing unnecessary ERROR-level log entries.
- NEXUS-53719 – Permission checks for users authenticated through external realms now cache role-to-permission mappings per request, improving UI performance for users with large role sets.
- NEXUS-53697 – NuGet hosted repositories now return correct partial content responses for byte-range requests, enabling clients to download only the requested portion of a package.
- NEXUS-52826 – Group repositories now display aggregated Firewall Report protection status based on their proxy members, and the Firewall Report column is correctly identified as non-sortable.
- NEXUS-53476 – Existing cached .whl.metadata assets are automatically migrated to use the application/octet-stream content type during upgrade; remove any reverse proxy rules or workarounds that were previously used to override this header to prevent conflicts.
- Jul 9, 2026
- Date parsed from source:Jul 9, 2026
- First seen by Releasebot:Jul 10, 2026
Sonatype Nexus Repository 3.94.0 Release Notes
Sonatype releases Nexus Repository updates with native OCI repository support, private Amazon ECR proxying, faster PyPI dependency resolution, and a Java EE 10 platform upgrade. It also improves Docker, Terraform, and security workflows while expanding Repository Firewall reporting and waiver management.
What’s New and Noteworthy in This Release?
Support for Open Container Initiative (OCI) Repositories
Sonatype Nexus Repository now supports native Open Container Initiative (OCI) hosted, proxy, and group repositories, giving you a single solution for managing container images and other OCI artifacts throughout your software supply chain. You can proxy content from external OCI registries, publish and protect internally developed artifacts, and expose multiple repositories through a single endpoint to simplify client configuration and artifact management.
This new repository format supports standard OCI-compatible tools, including Docker, Podman, Helm, ORAS, Cosign, Syft, Crane, and Skopeo, making it easier to adopt OCI workflows without changing existing tooling. In addition to container images, Nexus Repository can store and distribute Helm charts, Software Bills of Materials (SBOMs), signatures, attestations, and other OCI artifacts, helping organizations centralize artifact management while supporting modern software supply chain and container security practices.
For full details, see the OCI Repositories help documentation.
Proxy Private Amazon Elastic Container Registry (ECR) Registries with Docker Repositories
Sonatype Nexus Repository now supports proxying private Amazon ECR registries through Docker proxy repositories. You can configure a Docker proxy repository by providing your AWS account's ECR registry URL along with AWS IAM credentials, allowing Nexus Repository to centrally cache and serve container images stored in private ECR registries.
To simplify authentication, Nexus Repository automatically retrieves and caches the ECR authorization token on the first image pull using your configured AWS credentials. This capability reduces repeated authorization calls to Amazon ECR, lowers data transfer costs, and provides a consistent image source for development and CI/CD environments.
For full details, see the Proxy Repository for Docker help documentation.
PyPI Simple API v1.1 Support for Faster Dependency Resolution
Sonatype Nexus Repository now supports Simple API v1.1 (PEP 700) for PyPI repositories, enabling modern Python clients such as pip and uv to access richer package metadata. With this additional metadata, clients can make more informed dependency resolution decisions, reducing the number of requests and improving overall performance when installing packages.
This enhancement maintains full backward compatibility by preserving existing PEP 503 HTML and Simple API v1.0 behavior. Existing clients continue to function without change, while newer tools benefit from improved efficiency and faster dependency resolution workflows.
Java EE 10 Upgrade for Modernized Platform Infrastructure
Sonatype Nexus Repository now uses Java EE 10, modernizing the underlying servlet infrastructure and aligning core components with current standards. This update includes upgrades to key dependencies such as Jetty, RESTEasy, and OpenAPI 3, improving platform consistency, maintainability, and long-term compatibility with modern Java ecosystems.
Note: As part of this change, custom plugins, integrations, and tooling that rely on javax.servlet APIs must migrate to the corresponding jakarta.servlet APIs before upgrading. This ensures continued compatibility and allows extensions to take full advantage of the updated platform.
Improved Docker Repository Management Experience
Sonatype Nexus Repository now streamlines Docker repository management with guided connector configuration and enhanced usability. The system suggests appropriate ports during setup, reducing configuration errors and helping you get repositories up and running more quickly.
Search results now display richer image metadata, giving you better visibility into available artifacts. Additionally, generated docker pull commands automatically reference your Nexus Repository registry, ensuring accuracy and simplifying the process of retrieving images.
Simplified URL Encoding Configuration for Proxy Repositories
Sonatype Nexus Repository now centralizes URL encoding behavior for proxy repositories through the Preserve Encoded Characters setting. This update removes ambiguity by making the repository-level configuration the single control point, allowing you to manage how encoded characters are handled without relying on additional global properties.
Updated Defaults for Conan Proxy Repositories
Sonatype Nexus Repository now defaults new Conan proxy repositories to Protocol Version V2, aligning with the latest Conan ecosystem standards. This update helps ensure compatibility with modern Conan clients and reduces the need for manual configuration during repository setup.
Enhanced Compatibility for Terraform Proxy Repositories
Sonatype Nexus Repository now dynamically detects upstream service discovery paths for Terraform proxy repositories. This improvement allows Nexus Repository to automatically adapt to the structure defined by compliant registries, eliminating the need for manual configuration of service endpoints.
With this enhancement, you can seamlessly proxy content from a wider range of registries, including OpenTofu registries and registry.coder.com. By aligning with each registry’s discovery protocol, Nexus Repository reduces errors and improves reliability when retrieving modules and providers across diverse Terraform ecosystems.
Immediate Session Invalidation on Password Change
Sonatype Nexus Repository now strengthens account security by immediately invalidating all active sessions when a user’s password is changed. This ensures that any existing sessions across devices or browsers are terminated as soon as new credentials are set.
Stronger API Key Generation with UUID v4
Sonatype Nexus Repository now generates API keys for NuGet, npm, Docker, and Conan formats using UUID v4. This update improves the randomness and uniqueness of generated keys, strengthening the overall security of authentication workflows across supported formats.
Existing API keys remain valid and continue to function without change. However, Sonatype recommends regenerating keys to take advantage of the enhanced security model and ensure alignment with current best practices.
Discontinued UBI-Based Docker Images
Sonatype Nexus Repository no longer publishes UBI-based Docker images. This change streamlines supported deployment options and aligns container distribution with the current supported image strategy.
To continue receiving updates and support, update your deployment configurations to use the Alpine-based image variants.
Repository Firewall: New Firewall Success Metrics Dashboard
Sonatype Repository Firewall now includes the Firewall Success Metrics dashboard in Enterprise Reporting, giving organizations a clearer understanding of how effectively Firewall protects their software supply chain. By bringing key operational and security insights together in one place, the dashboard helps teams measure the impact of their security policies, identify trends in component risk, and determine whether quarantine workflows are reducing exposure to malicious or vulnerable components. At a glance, teams can monitor metrics such as component evaluations, quarantines, malicious component detections, waivers, and quarantine response times to understand how Firewall is performing over time.
With greater visibility into Firewall activity, security, platform, and engineering teams can make more informed decisions about policy tuning, prioritize response efforts, and demonstrate the value of their software supply chain security program. Interactive filtering and detailed reporting make it easier to investigate quarantine trends, understand why components are blocked, monitor waiver usage, and identify opportunities to reduce review times and continuously improve how open source risk is managed across the organization.
For full details, see the Firewall Success Metrics Dashboard help documentation.
Repository Firewall: New Malware Threat Landscape Dashboard
Sonatype Repository Firewall now includes the Malware Threat Landscape dashboard in Enterprise Reporting, providing organizations with a broader view of malware activity across the open source ecosystem. By surfacing ecosystem-wide malware trends alongside Firewall blocking activity, the dashboard helps security, platform, and engineering teams better understand the evolving threat landscape, assess potential exposure, and demonstrate the value of proactively blocking malicious components before they reach developers.
The dashboard combines high-level metrics with interactive reporting to help teams monitor trends such as newly discovered malware, attack frequency, malware exposure, and Firewall prevention activity. With filtering by ecosystem, threat type, attack vector, and time period, organizations can investigate emerging threats, identify the ecosystems most affected by malware, and use this insight to strengthen software supply chain security strategies and communicate risk more effectively to stakeholders.
For full details, see the Malware Threat Landscape help documentation.
Repository Firewall: Centralized Waiver Request and Management
Sonatype Repository Firewall now includes a complete in-product waiver management workflow that streamlines how policy exceptions are requested, reviewed, approved, and maintained. Developers can submit waiver requests directly from policy violations, while administrators can review, approve, reject, and renew waivers through a centralized Waivers dashboard. This creates a more structured and transparent approval process, reducing manual coordination and helping ensure policy exceptions receive the appropriate level of oversight.
Repository Firewall: Waiver Expiration Email Notifications
Sonatype Repository Firewall can now send configurable email notifications before component waivers expire, helping organizations stay ahead of expiring policy exceptions. Administrators can define multiple reminder thresholds and notify individual recipients or role-based groups, giving teams ample time to review, renew, or remove waivers before they expire.
By proactively alerting the right stakeholders, this enhancement helps reduce the risk of unexpected component quarantines or workflow disruptions caused by expired waivers. It also improves governance by making waiver lifecycles more visible, encouraging regular review of policy exceptions, and helping ensure temporary waivers do not remain in place longer than intended.
For full details, see the Waiver Expiration Notifications help documentation.
Repository Firewall: Expanded Firewall Webhook Events
Sonatype Repository Firewall webhooks now support Violation Alert and Waiver Request events, enabling real-time notifications for repository proxy policies. This enhancement allows organizations to integrate Firewall activity more easily with ticketing systems, messaging platforms, and automated workflows, helping teams respond more quickly to new policy violations and waiver requests while reducing manual monitoring and accelerating security operations.
For full details, see the Firewall Webhooks help documentation.
Repository Firewall: Repository-Scoped Access to the Firewall Dashboard
The Sonatype Repository Firewall dashboard now supports repository-scoped access, allowing users with read permission on individual proxy repositories to view dashboard data automatically limited to only the repositories they are authorized to access. This enhancement extends Firewall reporting to a broader set of users while preserving access controls, enabling development and operations teams to monitor Firewall activity relevant to their own repositories without exposing data from other parts of the organization.
Repository Firewall: Improved Quarantine Timeline Visibility
Repository Results tables in Firewall now separate Evaluation Time and Quarantine Time into dedicated columns, providing clearer insight into the lifecycle of evaluated components. This enhancement makes it easier to interpret repository activity at a glance and reduces ambiguity when reviewing Firewall results.
Bug Fixes
- NEXUS-53700: Nexus Repository startup completes successfully with analytics disabled, allowing all internal tasks to initialize without errors or repeated retry failures.
- NEXUS-53682: Source RPMs in hosted Yum repositories now carry arch="src" in generated primary.xml metadata, ensuring yum/dnf clients correctly distinguish source packages from binary packages during installation. Upgrade Impact: Yum repository metadata regeneration is required after upgrading. Source RPMs uploaded to hosted Yum repositories before this fix will need their repodata regenerated to reflect the corrected architecture value.
- NEXUS-53492: PyPI group repositories now return the correct package and metadata hashes for locally hosted packages that shadow proxy packages with the same filename, allowing PEP 658/691-aware clients such as pip 26 to install patched packages without hash mismatch errors.
- NEXUS-53454: Duplicate repository.search.update tasks are now prevented in High Availability deployments by a singleton guard that blocks a second node from scheduling the task when one already exists in the scheduler.
- NEXUS-53449: PyPI group repositories now reflect updated package versions from proxy members automatically once the proxy's metadata cache expires, without requiring manual cache invalidation.
- NEXUS-53395: Docker image layer extraction on Windows now handles paths containing illegal characters (such as *, ?, or :) and paths exceeding 260 characters, allowing Firewall for Docker scans to complete successfully on Windows with the same evaluation results as Linux.
- NEXUS-53310: Ansible Galaxy proxy repository metadata now rewrites download URLs dynamically based on the scheme, hostname, and port of each inbound request, ensuring components download successfully regardless of which network address is used to access the instance.
- NEXUS-53297: Package index updates in nested PyPI group repositories now propagate automatically through all group levels when new versions are uploaded or cached, without requiring manual cache invalidation.
- NEXUS-53266: Sensitive HTTP authentication headers—including Authorization: Bearer, Authorization: Basic, X-Auth-Token, and X-API-Key—are now automatically redacted from log files at write time, ensuring support ZIP bundles never contain plaintext credentials.
- NEXUS-53242: Downloading models through a HuggingFace proxy repository now produces complete, non-zero-byte blob files for non-LFS content such as config.json and tokenizer files.
- NEXUS-53199: After login, the UI is immediately interactive while permissions load asynchronously in the background, eliminating the blocking "Loading Permissions" screen experienced by users with large role sets.
- NEXUS-53184: NuGet V2 FindPackagesById() returns only exact package ID matches, preventing packages like Project-main from appearing in results when querying for Project.
- NEXUS-53173: PyPI proxy, hosted, and group repositories now return Simple API v1.1 responses (PEP 700) with size, upload-time, and versions fields when upstream data supports it, while automatically falling back to v1.0 for older clients and mixed-version group members.
- NEXUS-53059: Frontend dependencies axios (1.16.0 → 1.17.0) and tar (7.5.13 → 7.5.16) are updated to versions that resolve high and medium severity security vulnerabilities.
- NEXUS-53007: Rate-limit buckets for NuGet API key authentication are now isolated per token, so an invalid token from one user cannot trigger HTTP 429 errors for other users sharing the same repository.
- NEXUS-52998: Nexus Repository now starts cleanly when a Default Role capability references a role that no longer exists, while still returning HTTP 400 for API requests that attempt to create or update the capability with a nonexistent role.
- NEXUS-52973: NuGet v2 proxy repositories now serve cached package results immediately, reducing FindPackagesById response times from ~18 seconds to under one second for warm-cache requests.
- NEXUS-52961: Support zip exports now include an oauth2UserExport.json file containing OAuth2 user table data, giving support teams visibility into OAuth user records when troubleshooting authorization issues.
- NEXUS-52912: Mandatory Telemetry components load conditionally based on configuration, with threshold comparisons, retry task initialization, and deprecation warnings for nexus.analytics.enabled all behaving correctly across enabled and disabled states.
- NEXUS-52859: PyPI proxy, hosted, and group repositories now serve PEP 691/700-compliant JSON responses—including file size, upload timestamps, and complete version lists—to tools that request the modern Simple API format, while continuing to return HTML to legacy clients. Upgrade Impact: Modern Python tools (pip 23+, uv, Poetry 2.x) will automatically begin receiving JSON responses instead of HTML from PyPI proxy, hosted, and group repositories. Verify that any custom PyPI tooling or scripts in your environment support the PEP 691/700 JSON Simple API format before upgrading.
- NEXUS-52856: Keyword-only searches now display the group repository name for users whose access is granted through a group, while administrators continue to see the actual member repository where the component is stored.
- NEXUS-52855: The Repair - Rebuild Maven repository metadata task gracefully skips repositories that don't contain the specified groupId/artifactId, completing without errors or spurious log warnings.
- NEXUS-52846: Logging out of Nexus instances configured with Okta OIDC now completes successfully, as the required id_token_hint parameter is included in the logout request sent to the identity provider.
- NEXUS-52831: Authentication rate limiting now blocks requests before credentials are evaluated, ensuring that users who have exceeded the failed-login threshold receive HTTP 429 regardless of whether the submitted password is correct.
- NEXUS-52827: Clicking the Repository column header in Search results now sorts correctly across all repository formats instead of returning an error. Upgrade Impact: The repositoryName sort alias is now recognized by the search backend, which means any integrations or scripts that previously relied on the error response from repositoryName sort requests will receive successful sorted results instead.
- NEXUS-52813: PyPI hosted repositories now correctly reflect newly uploaded packages in the per-package simple index for names containing uppercase letters, underscores, dots, or other characters requiring PEP 503 normalization, without requiring a manual metadata rebuild task.
- NEXUS-52799: Downloading macOS universal (fat) binary .exe artifacts through Maven proxy repositories succeeds with strict content type validation enabled, as application/x-mach-o-universal is now recognized as a valid MIME type for .exe files.
- NEXUS-52769: Raw proxy repositories with preserveEncodedCharacters enabled now forward upstream redirect URLs byte-for-byte to storage backends, preserving consecutive slashes and encoded characters required by Cloudflare R2 and AWS S3 SigV4-signed URLs. Upgrade Impact: The preserveEncodedCharacters setting on raw proxy repositories now controls URI normalization behavior. Repositories with this option set to false will continue to have redirect URLs normalized (collapsing // to /), which may affect upstream compatibility.
- NEXUS-52759: Upgrade Impact: Groovy scripts now execute under Groovy 5.0.6, which enforces stricter sandbox security semantics. Existing scripts using indirect imports (for example, System.getProperty(...)) will return an error and must be updated to comply with the new SecureASTCustomizer rules.
- NEXUS-52625: YUM/RPM repository components with thousands of assets are now partially indexed rather than silently excluded from search when their accumulated file paths approach PostgreSQL's internal tsvector size limit.
- NEXUS-52620: Blob store creation and modification through the UI complete successfully when Nexus is accessed via HTTPS.
- NEXUS-52580: Data Repair Plan recovery correctly preserves the MODULE_VERSIONS asset kind for Terraform versions.json files, allowing subsequent module uploads to hosted Terraform repositories to complete successfully.
- NEXUS-52571: Removing all nexus-managed roles from an LDAP or SAML user now saves cleanly, with the Users list remaining fully functional without requiring a page reload.
- NEXUS-52320: Terraform authentication through a context path now correctly extracts user tokens from the request URI, allowing terraform init to complete successfully when "Require User Tokens for Repository Authentication" is enabled.
- NEXUS-52117: Uploading components and artifacts to hosted repositories via the Upload sidebar tab now completes successfully without errors.
- NEXUS-52107: When startup fails to initialize an HTTP client facet due to a missing or stale secret, log output now includes the affected repository name and configuration area (httpclient.authentication.password) to enable faster diagnosis without requiring database-level investigation.
- NEXUS-52050: Clicking the Sonatype logo now navigates correctly to the appropriate landing page in both Cloud and Preview UI environments, replacing the previous blank page behavior.
- NEXUS-52006: The lastDownloaded timestamp update now uses a conditional database operation rather than per-node in-memory tracking, preventing orphaned .tmp and .bak blob attribute files from accumulating on NFS and CIFS blob stores.
- NEXUS-51920: Terraform hosted repositories now correctly upload and download modules with SemVer pre-release versions containing hyphens, such as 0.0.5-main-20260323 or 1.2.3-feature-branch-42.
- NEXUS-51877: Search index rebuild tasks skip empty component batches gracefully, preventing PostgreSQL syntax errors in task and database logs.
- NEXUS-51835: Azure blob store initialization failures now log the root cause exception and full stack trace at the default ERROR log level, eliminating the need to enable DEBUG logging before restarting to diagnose the problem.
- NEXUS-51662: Multi-term search queries on SQL/PostgreSQL backends now respect term order and position when nexus.search.multi.wildcard.regex.enabled=true is set, returning only components where search terms appear in the specified sequence rather than in any order.
- NEXUS-51660: Embedded wildcard patterns such as ubi*-dev and psql*-jdk*-ubi* now return matching components across Name, Tag, Version, and Artifact search fields instead of empty results.
- NEXUS-51643: Helm hosted repositories now return a JSON 409 Conflict response when a chart push is rejected, allowing helm cm-push and other ChartMuseum-compatible clients to parse and display the actual rejection reason instead of an unparseable HTML error page.
- NEXUS-51593: Content selector privileges created or updated via the REST API now display their correct repository and format values in the UI, and editing a privilege through the UI no longer silently overwrites the configured repository scope.
- NEXUS-51522: Mixed-case Docker repository names created before 3.90 are now fully editable via the REST API, with the only restriction being that path-based routing cannot be newly enabled on repositories with non-lowercase names.
- NEXUS-51449: The Repository Health Check column is no longer displayed in the Browse view for customers who have Firewall enabled.
- NEXUS-50725: Startup log messages for the Job Key Unification task now accurately reflect cluster conditions, omitting misleading "old nodes still running" warnings when all nodes are running the same version.
- NEXUS-50701: SSRF validation now defers to the configured global HTTP/HTTPS proxy when direct DNS resolution fails, allowing proxy repository creation and artifact retrieval in locked-down or air-gapped environments where Nexus cannot perform local DNS lookups.
- NEXUS-41851: Logger override configurations are now exported to the support zip in High Availability deployments, where this data is stored in the logging_overrides database table rather than logback-overrides.xml.
- NEXUS-27554: The NuGet API Token section in user profiles is now hidden when the NuGet API-Key realm is disabled, matching the behavior of other realm-dependent features.
Coming Soon
Groovy Scripting Support Reaches End of Life in December 2026
Groovy scripting support in Sonatype Nexus Repository will reach end of life in December 2026. All capabilities that previously required Groovy scripts are now available through the Nexus Repository UI and REST APIs, providing supported options for configuration and automation. If you still use Groovy scripts, begin planning your migration to the UI or REST APIs before the end-of-life date to ensure a smooth transition.
Blob Store Names Cannot Contain HTML Special Characters
Beginning with self-hosted release 3.95.0 (expected August 2026), blob store names cannot contain HTML special characters. This is to enhance protection against stored XSS vulnerabilities. Existing blob stores with non-conforming names must be renamed before upgrading to 3.95.0.
Nexus One UI as Default
The Nexus One UI will soon become the default interface in Sonatype Nexus Repository, providing a faster, more intuitive experience with streamlined navigation and improved repository search and browsing. Users will still be able to switch back to the Classic UI, making it easy to adopt the new experience at your own pace.
Original source - Jun 4, 2026
- Date parsed from source:Jun 4, 2026
- First seen by Releasebot:Jun 5, 2026
Sonatype Nexus Repository 3.93.0 Release Notes
Sonatype adds broad Nexus Repository updates, including Go, Ansible and Alpine repository support, richer PyPI compatibility, new security and admin APIs, default IP Allow List protection, rate limiting, and a refreshed upload UI, alongside many reliability and bug fixes.
Known Issue in Nexus Repository 3.91.x – 3.93.0
Sonatype is aware of an issue affecting Nexus Repository 3.91.x - 3.93.0 deployments that use PyPI proxy repositories.
When a PyPI proxy repository points to a remote repository that returns relative links for Python wheel files, Nexus Repository may incorrectly resolve those links when constructing the upstream download request. This can result in invalid upstream URLs and HTTP 404 responses returned to Python clients.
This issue is known to affect chained PyPI proxy configurations where one Nexus Repository instance proxies another Nexus Repository instance. PyPI proxy repositories configured to proxy PyPI.org directly are not known to be affected.
If you use chained PyPI proxy repositories with another Nexus Repository instance as the remote, do not upgrade to Nexus Repository 3.91.x – 3.93.0.
What’s New and Noteworthy in This Release?
Support for Go Hosted and Group Repositories
Sonatype Nexus Repository now supports Go hosted and group repositories, enabling organizations to manage internal Go modules alongside external dependencies through a centralized repository manager.
With Go hosted repositories, you can securely store and publish internal Go modules, including module ZIP files, directly to Nexus Repository. Go group repositories simplify client configuration by allowing you to combine multiple Go repositories, including hosted and proxy repositories, behind a single URL.
For full details, see the Go repositories help documentation.
Support for Ansible Repository Format
Sonatype Nexus Repository now supports the Ansible Galaxy repository format, enabling teams to centrally manage Ansible collections alongside other development artifacts. By integrating Ansible Galaxy repositories with Nexus Repository, organizations can apply consistent governance, security, and repository management practices across their automation assets and software supply chain.
Nexus Repository supports proxy, hosted, and group repository types for Ansible collections. Teams can cache content from upstream sources such as galaxy.ansible.com, host internally developed collections, and aggregate multiple repositories behind a single endpoint to simplify client configuration.
For full details, see the Ansible repositories help documentation.
Support for Alpine Repository Format
Sonatype Nexus Repository now includes proxy, hosted, and group repository support for Alpine format, allowing teams to manage Alpine Linux packages through the same centralized repository management platform used for other package formats.
Alpine repository support helps teams improve the reliability and security of Alpine-based environments by centralizing package management and reducing reliance on external package sources. Nexus Repository integrates directly with the Alpine apk client, supports repository-specific RSA signing keys to help protect package integrity, and provides flexible access controls through both token-based authentication and anonymous access.
For full details, see the Alpine repositories help documentation.
Renew Expiring Waivers in Firewall Without Recreating Them
Sonatype Repository Firewall now lets authorized users renew existing waivers from the UI or through the new POST /api/v2/firewall/waivers/renew API endpoint. Users can extend waiver expiration dates from Waivers, Policy Violations, Applicable Waivers, and the waiver detail view, helping teams manage policy exceptions without creating replacement waivers.
The renewal workflow supports preset or custom expiration dates, optional waiver reasons and comments, and contextual guidance that explains how the new expiration date will apply. Validation prevents invalid renewal requests, and API responses include renewal counts, not-found counts, and per-waiver error messages for easier automation and troubleshooting.
For full details, see the Renew Waivers help documentation.
New nameCode Parameter in User Token API
Sonatype Nexus Repository administrators can now look up user token ownership information by nameCode through the User Token REST API. This enhancement helps administrators quickly identify the user and authentication realm associated with a token during incident response, security investigations, and troubleshooting activities, reducing the time required to investigate token-related events.
The lookup capability supports both active and expired tokens and returns ownership and lifecycle information without exposing token secrets or credential material.
Granular Control of Uploader Metadata Visibility
Sonatype Nexus Repository now provides more granular control over access to uploader metadata associated with repository assets.
A new nexus:uploader-metadata:read permission controls access to uploader metadata across the Browse UI and REST APIs. Users without this permission no longer see uploader information in asset, component, or search results, while administrators retain access through existing administrative privileges.
By limiting access to sensitive metadata based on user responsibilities, this enhancement supports least-privilege security practices and helps organizations better protect internal user and infrastructure information.
Enhanced PyPI Repository Compatibility
Sonatype Nexus Repository now supports PEP 658 inline metadata and the PEP 691 JSON-based Simple API for hosted and proxy PyPI repositories. These standards improve interoperability with modern Python package management tools while preserving compatibility with existing clients that use the traditional PEP 503 HTML-based Simple API.
With more efficient access to package metadata, Python clients can resolve dependencies without downloading unnecessary package artifacts, reducing bandwidth usage and improving performance for developer workflows and CI/CD pipelines. This enhancement helps organizations deliver a PyPI experience that more closely aligns with modern Python ecosystem standards while maintaining support for existing package consumers.
Note that PEP 658 metadata and PEP 691 JSON support are available automatically in Nexus Repository 3.93.0 and later. Compatible Python clients include pip 23.1+, uv 0.1.0+, and Poetry 1.8+.
New Endpoints in Security management: user roles API
Sonatype Nexus Repository now includes additional endpoints in the Security management: user roles API that allow administrators to programmatically view and manage user role assignments in cloud deployments. Administrators can retrieve existing role assignments, replace assigned roles, add new roles, or remove existing roles through the API. These enhancements provide greater flexibility for organizations that automate user provisioning and access management workflows.
IP Allow List Enabled by Default
The IP Allow List feature is now enabled by default in Sonatype Nexus Repository Pro and Cloud editions. This feature allows administrators to restrict access to Nexus Repository based on source IP addresses and network ranges, providing an additional layer of protection for deployments with network security requirements. Existing IP Allow List configurations are preserved during upgrade.
OAuth2/OIDC Configuration REST API
Sonatype Nexus Repository now provides public API support for managing OAuth2 and OpenID Connect (OIDC) configuration. Administrators can retrieve, update, and remove OAuth2 settings through REST APIs, enabling programmatic management of authentication configuration and reducing the need to perform these tasks through the user interface.
Improved Protection for Proxy Repository Credentials
Sonatype Nexus Repository now applies additional validation when updating proxy repository connection settings. As part of this update, administrators may be prompted to provide authentication credentials when modifying proxy repository connection details. This change strengthens protection for upstream credentials and supports more secure management of authenticated proxy repositories.
Refreshed Artifact Upload User Interface
Sonatype Nexus Repository includes an updated artifact upload UI with improved visual consistency and usability. The refreshed experience introduces a more cohesive layout, addresses several visual presentation issues, and aligns the upload workflow with the design patterns used throughout the application.
Authentication Attempt Rate Limits For Added Protection
Sonatype Nexus Repository now includes authentication rate limiting to help protect against brute force login attempts. After three consecutive failed authentication attempts, login requests to both the user interface and API authentication endpoints are temporarily rate limited, reducing the risk of automated credential-guessing attacks.
Administrators can configure this behavior using the nexus.auth.ratelimit.* properties to align authentication controls with their organization's security requirements.
Bug Fixes
NEXUS-52921
Swift proxy repositories now strip leading "v" and "V" prefixes from Git tags when building the registry version list, so SwiftPM resolves dependencies like 5.3.0 correctly instead of encountering a mismatch with v5.3.0.NEXUS-52812
Outbound TLS connections in FIPS mode now succeed on Java 21, with the SSL layer explicitly enforcing TLSv1.2 and JKS keystore type to ensure compatibility with the BouncyCastle FIPS provider.NEXUS-52690
The Google Cloud Storage blobstore now bundles io.opentelemetry:opentelemetry-api version 1.61.0, resolving CVE-2026-45292 (CWE-770, resource allocation without limits).NEXUS-52659
Anonymous Docker pulls through a group repository now succeed when member repositories have "Allow Anonymous Docker Pulls" disabled, with the group-level anonymous access setting governing requests routed through the group.NEXUS-52631
Original source
UI Branding headers and footers now correctly preserve - May 2026
- No date parsed from source.
- First seen by Releasebot:May 8, 2026
2026 Release Notes
Sonatype lists 2026 Nexus Repository releases with major additions like Swift, Terraform, Conda, Dart and Helm support, a refreshed login experience, stronger SSRF protection, new migration tools, and a steady stream of bug fixes and reliability improvements.
Summary of Major Sonatype Nexus Repository Changes in 2026
This page contains a list of 2026 Sonatype Nexus Repository releases, links to each release's release notes, and a brief list of major changes per release.
Note that while we strive to fully document new features before releasing them to our Cloud environments, there may be occasional delays. In such instances, we will update this page with links to the relevant help documentation as soon as it becomes available.
The following table lists major changes to Sonatype Nexus Repository in 2026. Consider these changes when upgrading to a new version. Select a self-hosted release to see the fully featured release notes.
Major Changes | Cloud Release Date | Included in Self-Hosted Version
Features / Enhancements Preview Sonatype Nexus Repository's new user interface using the Switch to Nexus One UI toggle. Not that an administrator must enable this feature via Settings > System > Nexus One UI before the toggle will be visible (available in 3.92.0). SQL-to-SQL migrations now include SSL/TLS trusted certificates, preserving trust store configurations and reducing manual setup after migration. Configuration export and import now include role mappings for all users, including those from LDAP, SAML, and Crowd, ensuring access control is preserved during migrations. PyPI proxy repositories now support the PEP 658 and PEP 691 JSON API, caching JSON responses to improve performance for modern Python tools.
Bug Fixes NEXUS-51882 – PyPI hosted repositories now maintain consistent metadata during concurrent uploads by marking indexes as stale instead of deleting them, ensuring newly uploaded packages are accurately reflected. NEXUS-51795 – User-configured SAML Entity ID URIs now take precedence over the browser URL when generating SP metadata and authentication requests. NEXUS-51699 – The BlobRepositoryMismatch task now persists per-repository progress, resumes after restarts, logs progress periodically, and uses a CPU-scaled thread count instead of a fixed value. NEXUS-51514 – The compact blob store task now continues processing when individual S3 deletions fail, logging failures at WARN level instead of stopping the task.
April 29, 2026 | 3.92.0 (May 7, 2026) and 3.93.0 (Coming June 2026)
Features / Enhancements Swift repositories can now be migrated between Nexus Repository instances using the Instance Migrator. Package archives and manifests are transferred, while auto-generated metadata is excluded and regenerated on the target instance, enabling seamless migrations. Administrators can now manage SSRF protection settings at runtime using a new SSRF Protection endpoint in the Security Management API.
Bug Fixes NEXUS-52054 - Terraform hosted repository signing key material and passphrase are now redacted in support zip configuration exports. NEXUS-51930 - Conditional GET requests against proxy repositories now undergo Firewall policy evaluation, returning 403 Forbidden when a component is quarantined rather than incorrectly signaling 304 Not Modified. NEXUS-51633 - PyPI repositories now automatically invalidate and rebuild stale indexes after Verify and Repair blob restore tasks complete, eliminating the need to manually trigger index regeneration via API calls.
April 22, 2026 | 3.92.0 (May 7, 2026)
Features / Enhancements Added support for the Dart (pub) package format. Added support for Conda hosted and group repositories. The Instance Migrator can now migrate Terraform and Conda hosted repositories between Nexus Repository instances. Added support for Helm group repositories, allowing aggregation of multiple Helm repositories into a single endpoint (disabled by default; configurable via system property). Conda Hosted and Group repositories are now enabled by default, simplifying setup and providing immediate access to all Conda repository types. New Nexus Repository installations now have Server-Side Request Forgery (SSRF) protection enabled by default, blocking unauthorized access to private network resources out of the box. Existing installations are unaffected but can enable or configure this feature via API. The Usage Insights dashboard now retains daily storage metrics indefinitely, aligning with the retention model used for egress metrics. This ensures a complete and continuous view of storage trends across all time periods, eliminating gaps in historical data. Refreshed the login experience with a unified design across both self-hosted and Cloud deployments. The updated interface aligns with Sonatype’s standard design system, delivering a more consistent and polished user experience without introducing any functional changes. In cloud deployments, the Users page now includes an Invite User button, replacing Create Local User. This streamlines onboarding through your identity provider and simplifies the interface by automatically filtering to OAuth2 users. Self-hosted deployments are unchanged. Introduced a new admin REST API (GET/PUT /v1/security/ssrf-protection) for managing SSRF protection settings dynamically without requiring a restart. This includes support for configuring allowed IPs and domains, ensures cluster-wide consistency, and permanently blocks access to cloud metadata endpoints.
Bug Fixes NEXUS-51909 - PyPI proxy-chain repositories now correctly resolve relative package URLs, restoring successful package downloads. No viable workaround exists in affected versions; downgrade to 3.90.x is recommended until this fix is available. NEXUS-51864 - Version-specific npm requests (such as /lodash/latest) no longer invalidate or corrupt the PCCS cache. Subsequent metadata requests now return the complete and correct set of package versions. NEXUS-51814 - Docker tag pagination responses now correctly preserve connector-based paths when accessed via dedicated connector hosts or ports, ensuring Link headers remain compliant with the Docker Registry HTTP API V2 specification. NEXUS-51659 - The Search API now returns an HTTP 400 response with a clear validation message when unsupported wildcard patterns (such as leading wildcards or short trailing wildcards) are used in the Repository Name field, replacing previous silent empty responses. NEXUS-51540 - Maven group repository metadata now stays up to date when new component versions are uploaded to hosted repositories nested within sub-groups, ensuring accurate version resolution across group hierarchies. NEXUS-51537 - PyPI group repository simple index pages are now served from cache on repeated access, eliminating unnecessary blob creation and improving performance. NEXUS-51523 - The Data Repair Plan task now report "created plan entries" instead of "created plans," accurately reflecting the number of individual repair items identified rather than the number of executable repair plans. NEXUS-51509 - Concurrent Policy Compliant Component Selection requests for the same PyPI or npm package are now deduplicated. Only a single evaluation request is sent to Firewall (IQ Server), with concurrent requests reusing the result. NEXUS-51485 - Docker clients now receive a standards-compliant error response when Repository Firewall blocks a quarantined image. The response includes quarantine details and a link to the Firewall report directly in the JSON payload. NEXUS-51389 - Repositories that fail to initialize during startup are now skipped and marked offline, allowing Nexus Repository to start successfully without being blocked by individual repository failures.
April 20, 2026 | 3.92.0 (May 7, 2026)
The self-hosted Sonatype Nexus Repository 3.91.1 release introduces the following additional bug fixes: NEXUS-51509 – Concurrent PyPI and npm proxy requests for the same package under Policy Compliant Component Selection now share a single upstream evaluation call to Firewall, preventing the duplicate memory loading that previously caused OutOfMemoryError crashes on IQ Server. NEXUS-51485 – Docker clients now receive a Docker Registry HTTP API V2 compliant error response containing the quarantine explanation and Firewall report URL directly in the JSON body when Repository Firewall blocks a pull request. NEXUS-51112 – Policy Compliant Component Selection now uses an increased timeout when evaluating metadata for large PyPI packages, allowing installations of components like tensorflow and duckdb to complete successfully.
April 17, 2026
Sonatype Nexus Repository 3.90.3 provides the following bug fix, which is also included in version 3.91.0: NEXUS-51666 – Added a skipProcessing configuration option to BlobRepositoryMismatchTask for eligible direct upgrades. See our Support Knowledgebase article for details.
3.90.3 and 3.91.0
Bug Fixes NEXUS-51666 – Administrators can now set blob.repository.name.mismatch.skipProcessing=true to allow the blob repository mismatch upgrade task to complete immediately without scanning assets, eliminating weeks-long processing delays for instances upgrading from versions prior to 3.69.0. NEXUS-51551 – The system confirmed protection against malicious axios package versions after npm removed the compromised packages from the registry. NEXUS-51523 – Data Repair Plan task logs now report "identified repair items" and "processing entries" instead of the ambiguous "created plans" terminology, clarifying that counts represent individual blob records requiring attention rather than the number of executable repair plans. NEXUS-51391 – Content selectors using "starts with" operators correctly filter paths with segments shorter than three characters. NEXUS-51334 – Fallback logging in npm group repositories now operates at DEBUG level instead of INFO, reducing log volume and removing misleading references to PCCS policy differences. NEXUS-51283 – Single RubyGems file uploads now update only the necessary metadata indices instead of regenerating data for every gem in the repository, eliminating temporary blob storage spikes during upload operations. NEXUS-51282 – Download URLs generated from UI search results now correctly reference the group repository path instead of underlying member repositories, allowing users with group-only permissions to access assets without encountering authorization errors. NEXUS-51279 – Search API requests using unsupported wildcard patterns now return HTTP 400 responses with descriptive validation messages, ensuring consistent behavior across all search fields. NEXUS-51266 – Improved PostgreSQL query performance for prefix-based component searches by enabling index scans on key search_components columns, reducing reliance on sequential table scans. NEXUS-51247 – Concurrent requests for the same component no longer generate ERROR-level log entries when multiple threads update blob property files simultaneously NEXUS-51112 – Increased timeout for Policy Compliant Component Selection when evaluating large PyPI packages (such as tensorflow and duckdb), allowing installations to complete successfully. NEXUS-50782 – NuGet v2 proxy repositories now correctly follow OData pagination links for FindPackagesById queries, ensuring all package versions and dependencies are cached and installable in a single operation. NEXUS-49855 – Prefix-based component name searches in High Availability deployments now return only components whose names begin with the specified term, ensuring accurate and predictable results. NEXUS-48607 – The UI telemetry service now avoids repeated attempts to reach unavailable remote endpoints, eliminating long page load delays in air-gapped and network-restricted environments.
April 8, 2026 | 3.92.0 (May 7, 2026)
Caution Known Issue with npm Group Repositories in Sonatype Nexus Repository 3.90.2; Issue fixed in 3.91.0 Sonatype is aware of an issue in Sonatype Nexus Repository 3.90.2 where npm group repositories may serve stale package metadata after upstream repositories are updated. This issue is fixed in version 3.91.0. This issue occurs when requesting packages with versions or dist-tags (for example, npm install storybook@latest or npm install @sonatype/[email protected]). The cache invalidation process fails, causing the group repository to return outdated version information. Symptoms may include: npm builds failing with version mismatch errors. Recently published package versions not visible through the group repository Server logs showing errors such as: IllegalArgumentException: Non URL-safe name Workaround: Manually invalidate the package cache through the Nexus UI: Browse → Select repository → Right-click package → Invalidate cache
Features / Enhancements Database connection pool metrics are now exposed through the metrics API, enabling administrators to monitor active, idle, and pending connections to optimize database performance and troubleshoot connection issues. (Available in self-hosted 3.92.0)
Bug Fixes NEXUS-51488 - Terraform service discovery now requires repository-level endpoint access at /repository/{repository-name}/.well-known/terraform.json instead of root-level access. Terraform CLI can successfully discover hosted registry services through this endpoint, enabling module and provider resolution. NEXUS-51407 - Maven proxy repositories now accept macOS Mach-O executables (such as ARM64 protoc binaries) when strict content type validation is enabled. NEXUS-51397 - Blob repository mismatch tasks now process blobs concurrently across available threads, significantly improving completion time during post-upgrade validation. NEXUS-51301 – Disabling IQ Server integration in Nexus Repository Cloud instances completes immediately without blocking or causing node unresponsiveness. NEXUS-51267 - Failed login attempts are now recorded in the audit.log file with detailed authentication failure information, including failure reasons.
April 1, 2026 | 3.91.0 (April 7, 2026) and 3.92.0 (May 7, 2026)
Features / Enhancements Proxy repository migrations from OrientDB to self-hosted instances now preserve authentication credentials and HTTP request settings (such as connection timeout, retries, and user agent). This eliminates the need for manual reconfiguration after migration. If credentials cannot be securely migrated due to missing encryption configuration, only the authentication details are removed while all other repository settings are retained. Added an informational alert in the Historical Usage section to clarify that usage data is updated every 48 hours. This helps set expectations and explains why recent repository changes may not be immediately reflected in storage metrics. Yum repository migrations now automatically regenerate repository metadata, including required files such as repomd.xml and associated .xml.gz files. This ensures migrated repositories remain complete and fully functional without requiring manual intervention.
Bug Fixes NEXUS-51311 - Capability state changes now complete without causing thread deadlocks that could block UI loading and API responses. NEXUS-51210 - Maven group metadata remains available during blob store migration tasks, preventing temporary inconsistencies. NEXUS-51191 - The Remove a member from a blob store group task now completes successfully when multiple instances run concurrently. NEXUS-51164 - Log messages for invalid Maven metadata files now include the repository name, improving troubleshooting. NEXUS-51030 - Proxy repository creation via the REST API no longer requires the blocked field, which now defaults to false when omitted. NEXUS-50808 - Docker tag listing now handles large tag sets without causing a StackOverflowError during pagination. NEXUS-50585 - Upgrade tasks now skip and log deprecated task types, such as OrientDB backup tasks, instead of failing during processing. NEXUS-50510 - DEBUG-level logging now records when SSRF protection blocks outbound proxy requests to private or local network addresses. NEXUS-50471 - Docker container startup now detects existing memory settings in INSTALL4J_ADD_VM_PARAMS and avoids adding duplicate JVM parameters. NEXUS-50384 - Docker content validation now correctly recognizes application/zstd layers, improving performance during image staging, push, and pull operations. NEXUS-50322 - Staging delete operations now log additional request details, enabling troubleshooting without requiring TRACE-level logging. NEXUS-47043 - Default reconcile thread usage has been reduced to better balance CPU consumption and minimize impact on smaller deployments. NEXUS-37039 - Cleanup tasks now remove stale asset blob records for deleted blob stores, preventing repeated warnings and unnecessary data growth.
March 25, 2026 | 3.91.0 (April 7, 2026)
Features / Enhancements Nexus Repository now supports Swift group repositories. This allows you to aggregate multiple Swift package sources into a single endpoint for simplified dependency management.
Bug Fixes NEXUS-50905 – S3 blob stores on different endpoints now validate bucket existence independently, preventing initialization conflicts when multiple blob stores share the same node. NEXUS-50831 – Group repositories in Nexus Repository Cloud deployments now accurately calculate and display their total size, including content from nested group members. NEXUS-50813 – Tag association operations now complete synchronously, allowing immediate component promotion and tag-based searches without delays in both High Availability and non-HA deployments. NEXUS-50640 – SAML authentication handles missing cookies gracefully when reverse proxies strip cookie headers, preventing server errors during the login flow. NEXUS-50628 – Schedule modifications to the Admin - Cleanup expired user tokens task persist across Nexus Repository restarts. NEXUS-50552 – The Browse menu now appears for users who have content selector privileges with browse action, matching the visibility behavior of standard repository-view permissions. NEXUS-50532 – Docker group repositories now return a 504 Gateway Timeout error when firewall scanning encounters a cooperative wait timeout, instead of incorrectly returning 404 Not Found. NEXUS-50196 – SAML external role mappings now synchronize on every login, removing outdated role assignments when IdP groups change and preventing users from retaining elevated privileges after group revocation. NEXUS-50167 – Added support for configuring pod-level securityContext in the Sonatype Nexus Repository HA helm chart StatefulSet, enabling fsGroup and fsGroupChangePolicy to reduce volume permission overhead and improve pod startup times on large storage deployments. NEXUS-49003 – Repository browse rebuild tasks now display overall progress across all repositories, showing the current repository name, completion percentage, and repository count. NEXUS-48819 – The Default Role capability now supports built-in roles like nx-anonymous and nx-admin across instance restarts and upgrades. NEXUS-45518 – Tag creation, updates, and deletions are recorded in the audit log with details about the initiator, tag name, and attributes. NEXUS-44583 – Maven repositories no longer allow non-timestamped SNAPSHOT artifacts (e.g., my-app-1.0-SNAPSHOT.jar) uploaded directly through the GUI; all SNAPSHOT artifacts must now use timestamped versions (e.g., my-app-1.0-20241016.074913-1.jar) as generated by standard Maven or Gradle deployment tools. Asset views display successfully when clicking on SNAPSHOT components that were uploaded directly via the GUI with non-timestamped versions.
March 18, 2026 | 3.91.0 (April 7, 2026)
This release introduces an Instance Migrator that allows OrientDB-based Nexus Repository 3.70.5 instances to either Nexus Repository Cloud or self-hosted Nexus Repository version 3.90.2+. See the Instance Migrator help documentation for full requirements and migration details.
Bug Fixes (3.90.2) NEXUS-51040 – Docker proxy repositories handle bearer token authentication requests without encountering null pointer exceptions during HTTP context operations. NEXUS-50764 & NEXUS-39228 – Group repositories now properly detect policy-filtered version changes in member proxy repositories, ensuring metadata remains current and complete across npm and PyPI formats.
3.70.5 and 3.90.2 (March 23, 2026)
Bug Fixes NEXUS-51199 – Deleting a Docker manifest now removes all associated tags, preventing orphaned tags from remaining in the repository. NEXUS-51148 – Nexus Repository now logs detailed diagnostic information when npm package metadata requests to IQ Server approach timeout thresholds, including request timing, cache behavior, and actionable configuration guidance. NEXUS-51144 – Blob store configuration changes now display warning messages only when modifying settings that affect data availability, such as storage location updates. NEXUS-51143 – Terraform modules with subdirectory syntax (using //) now download directly from Git sources rather than through the proxy cache, ensuring correct directory structure resolution. Note: Module downloads will bypass Nexus Repository caching and connect directly to upstream Git repositories (for example, GitHub) when using subdirectory references like terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts. NEXUS-50861 – Docker repositories accept image names containing consecutive underscores, aligning with OCI Distribution Specification requirements. NEXUS-50809 – The Swagger API documentation for the GET /v1/repositories endpoint now includes the size field, displaying repository size in bytes and matching the actual API response structure. NEXUS-50504 – Container image scanning handles large Go binaries (500MB+) without memory exhaustion by using a streaming parser that maintains constant memory usage regardless of file size. NEXUS-50246 – Wildcard version searches now return only packages where the version starts with the specified pattern, preventing matches on partial segments within version numbers. NEXUS-49457 – APT proxy repositories now include cached packages in metadata even after upstream removal, allowing installations to succeed from the local cache. NEXUS-41419 – Role editing operations automatically remove references to obsolete privileges instead of displaying error messages. NEXUS-40545 – Conda proxy repositories now apply the "maximum metadata age" setting to repodata.json files instead of treating them as components subject to "maximum component age" rules.
March 11, 2026 | 3.91.0 (April 7, 2026)
This self-hosted release fixes an issue in Sonatype Nexus Repository 3.90.0 Community Edition that prevented the application from starting upon initial installation or upgrade. Community Edition users can now safely upgrade to version 3.90.1.
3.90.1 (March 6, 2026)
Features / Enhancements Repository Firewall now supports global webhooks for quarantine events, automatically notifying your systems when components are quarantined or blocked due to policy violations. This enables real-time integration with your security workflows and incident response systems, allowing you to immediately track and respond to potentially risky components.
Bug Fixes NEXUS-50951 – From Nexus Repository version 3.89.0+, newly created Docker repositories must use lowercase names. This fix allows users to edit, via the UI, the configuration of upgraded Docker repositories that have mixed/upper case naming. NEXUS-50929 – Terraform token authentication no longer applies to non-Terraform repository formats. Anonymous access to raw hosted repositories works correctly for paths matching /v1/providers/** patterns. NEXUS-50761 – Repository browse displays all content for users with administrative permissions, regardless of any additional content selector privileges assigned through other roles. NEXUS-50623 – npm group repositories now return valid JSON metadata with a single _id field instead of duplicating it at the top level. NEXUS-50616 – Hugging Face proxy repositories correctly process filenames containing spaces and special characters by properly encoding URI segments in outbound requests. NEXUS-50251 – Search indexing completes successfully for components with tens of thousands of associated file paths by implementing PostgreSQL parameter limits. NEXUS-48954 – Session timeout values configured in the UI Settings capability now apply correctly in High Availability deployments, ensuring users remain logged in for the specified duration. NEXUS-45172 – When attempting to redeploy an asset with the "Allow Redeploy" setting disabled, error messages now explicitly state that redeployment is not permitted for the repository, replacing the previous generic "blob upload invalid" message across all repository formats. NEXUS-44209 – The Compact blob store task now successfully removes soft-deleted blobs after they've been relocated by the Remove a member from a blob store group task. NEXUS-42338 – Yum repositories now correctly identify the architecture of signed RPM packages by reading metadata from the RPM header tags instead of the lead header. NEXUS-39798 – Database connection failures during authentication now return HTTP 503 Service Unavailable instead of HTTP 401 Unauthorized, clearly indicating a server-side infrastructure issue rather than incorrect credentials. NEXUS-39080 – Docker proxy repositories now return HTTP 404 (Not Found) instead of HTTP 400 (Bad Request) when remote content fails digest validation. NEXUS-29440 – PyPI proxy repositories support remote URLs without the /simple endpoint by allowing an empty index path configuration for services like GemFury and NVIDIA PyPI.
March 4, 2026 | 3.91.0 (April 7, 2026)
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.
Features / Enhancements Support for Swift hosted repository format. Support for Terraform group repository format. The User Token API now allows administrators to create, view, and delete user tokens. With the appropriate privileges, administrators can generate tokens for specific users and realms, retrieve token summaries (excluding sensitive fields), and manage tokens across individual or all realms, including options to include expired tokens in responses. (self-hosted) The Repository - Copy Blob Size to Asset Table task is now available in the user interface. While this task is typically a one-time migration task that runs automatically during startup or upgrade, administrators can now manually run or schedule it if repository metrics become inconsistent, such as if the Size column no longer appears on the Repositories page. This update enables faster recovery from metrics corruption without requiring a restart or configuration changes. (self-hosted) New Recovery Mode feature that prepares self-hosted Nexus Repository deployments for reconciliation operations when repository or blob store data becomes inconsistent. This feature inclues a dedicated Recovery Mode page under the Support section as well as a new Recovery Mode API.
Bug Fixes NEXUS-50718 – Terraform hosted repositories now correctly generate provider metadata for all uploaded providers, ensuring consistent discovery and installation through the Terraform CLI. NEXUS-50711 – Improved search API filtering to accurately return results when combining component criteria (such as name or repository) with asset-level checksums in a single query. NEXUS-50706 – Improved cache invalidation for npm proxy repositories to properly handle packages with names starting with underscores or periods. NEXUS-50690 – Corrected npm search query handling to ensure consistent result ordering and de-duplication in PostgreSQL environments. NEXUS-50574 – npm audit requests for projects without dependencies now complete successfully instead of generating error logs. NEXUS-50554 – During Change repository blob store migrations to S3, asset requests now validate blob existence in the target cloud store and properly fall back to the source blob store, preventing 500 errors and build failures while migration is in progress.
February 25, 2026 | 3.90.0 - 3.90.1 (March 5, 2026) and 3.91.0 (April 7, 2026)
This self-hosted patch release fixes the following bugs: NEXUS-50621 – Metadata generation for hosted APT repositories now correctly includes all applicable package versions in Packages files, ensuring clients receive complete and accurate repository metadata. NEXUS-50490 – The LDAP configuration REST API now properly handles authentication password parameters when creating LDAP server connections. NEXUS-50487 – The LDAP configuration API now correctly handles updates when using URL-encoded connection names in REST API requests. NEXUS-50473 – User access to group repositories now correctly inherits read and browse permissions from member repositories, with consistent enforcement of content selectors across authorization checks and Browse previews. NEXUS-50338 – LDAP configuration updates via REST API now reliably preserve all required fields during credential rotation and server configuration changes. NEXUS-48604 – Enhanced LDAP credential rotation in High Availability clusters to ensure cache synchronization across all nodes when updating bind credentials.
February 11, 2026 | 3.89.1 (February 11, 2026)
Features / Enhancements Proxy URL validation is enabled by default to block outbound connections to private network addresses, localhost, and cloud metadata endpoints. Sonatype Repository Firewall now writes firewall.quarantine audit log events when components are newly quarantined or when users attempt to download already quarantined components. Note that you must be using self-hosted IQ version 201 or Sonatype Lifecycle Cloud (SaaS) for this to take effect. Improvements to the Sonatype Nexus Repository Cloud login page.
Bug Fixes NEXUS-50621 – APT hosted repositories now correctly include all package versions in generated Packages files for each architecture. (Also fixed in self-hosted 3.89.1.) NEXUS-50612 – Upgraded installations now successfully migrate the asset_blob_size column when upgrading directly from versions prior to 3.67.0 to 3.87.0 or later, ensuring artifact uploads complete without database errors. NEXUS-50592 – Content selectors now appear in alphabetical order within the Repository Content Selector Privilege dropdown, making it easier to locate specific selectors when working with large lists. NEXUS-50362 – Maven repositories now correctly return HTTP 404 responses when requesting non-existent hash signature files with compound extensions like
.md5.asc. NEXUS-50277 – Improved repository synchronization in high availability deployments to maintain consistent state across all nodes during concurrent deletion operations. NEXUS-50273 – Improved Quartz scheduler initialization to prevent extended startup delays, reducing the time required for Sonatype Nexus Repository to become fully operational after restart. NEXUS-50243 – Improved Maven group metadata accuracy to consistently reflect the latest artifact versions across nested group configurations. NEXUS-50153 – Yum group repositories now serve cached metadata to clients while regenerating merged metadata in the background, preventing incomplete repodata responses during the merge process. NEXUS-48604 – Enhanced LDAP credential rotation to maintain consistent cache synchronization across all nodes in high availability clusters. (Also fixed in self-hosted release 3.89.1.) NEXUS-47776 – Improved URL encoding handling in proxy repositories to preserve special characters in redirect URLs, ensuring successful retrieval of artifacts from remote sources. NEXUS-47618 – Cleaned up Prometheus metrics by removing unused S3 blob store timers that always displayed zero values. NEXUS-46841 – Improved Docker token request handling to reliably process concurrent authentication attempts from the same client. NEXUS-46805 – Non-administrator users can now configure Content Replication with repository-specific privileges without encountering permission errors. NEXUS-46315 – Added JVM memory and garbage collection monitoring logs to help diagnose system resource issues across all deployment configurations. NEXUS-44226 – Added a new paginated REST API endpoint for retrieving SAML users, with the existing endpoint now limiting results to 100 users to improve performance and scalability for large user bases. NEXUS-43881 – Improved browse tree cleanup in YUM repositories to properly remove directory nodes when deleting duplicate RPM files uploaded to multiple paths.January 28, 2026 | 3.89.0 - 3.89.1 (February 3, 2026) and 3.90.0 - 3.90.1 (March 5, 2026)
Features / Enhancements Support for Swift proxy repository format. (Available in Self-Hosted 3.89.0) Support for Terraform hosted repository format. (Available in Self-Hosted 3.89.0) Breaking change: SAML login requires SAML2_AUTH_REQUEST cookie beginning in 3.89.0
Bug Fixes NEXUS-50419 – Updated the image scanning process to ensure temporary resources are properly cleaned up, improving system stability and preventing potential memory issues. NEXUS-50338 – LDAP configuration updates via REST API now reliably preserve all required fields during credential rotation and server configuration changes. (Fixed in self-hosted 3.89.1) NEXUS-50313 – The log management API now works as expected to retrieve audit or request type events in Nexus Repository Cloud environments. Documentation will also be available soon. NEXUS-50240 – Anonymous access to Terraform proxy repositories now correctly allows unauthenticated users to retrieve provider versions without receiving a 401 response. NEXUS-50163 – The user interface handles rapid navigation during page loading without encountering null reference errors. NEXUS-50133 – Support zip log files now truncate from the bottom up, preserving the most recent log entries needed for effective troubleshooting. NEXUS-50116 & NEXUS-50151 – Resolved an issue with the Repair - Execute Data Repair Plan task that previously led to some unexpected assets being removed. Note that this task remains disabled by default in release 3.89.0. NEXUS-50112 – Importing Docker images no longer removes the /library/ namespace prefix. NEXUS-50056 – Docker tag list responses now include the correct Link header path when requests are made using repository or path-based URLs. NEXUS-50040 – The REST APIs for Hosted Repository Analysis now evaluate artifacts without returning an HTTP 500 error, preventing a NullPointerException when determining repository scan support. NEXUS-49769 – Uploading RPMs to a Yum hosted repository no longer leaves behind empty repodata folders in the Browse UI. NEXUS-49722 – Search results for pre-upgrade components with underscores in the group name now return correctly after upgrading without requiring a manual search index rebuild. NEXUS-49164 – Wildcard searches in HA environments now correctly return results when the search term includes a hyphen-prefixed token. NEXUS-48701 – The nexus_cluster.log file is no longer created when using H2 or PostgreSQL, eliminating confusion caused by an unused log file in non-OrientDB environments.
January 21, 2026 | 3.89.0 (February 3, 2026)
To prevent potential data loss caused by a known issue impacting Sonatype Nexus Repository 3.83.0 and later, we have disabled the Repair - Execute Data Repair Plan task by default.
3.84.2 (January 15, 2026) 3.85.1 (January 15, 2026) 3.86.3 (January 15, 2026) 3.87.2 (January 15, 2026)
Bug Fixes: NEXUS-49996 – Improved repository deletion performance and reliability by optimizing role privilege cleanup and addressing race conditions across HA nodes. NEXUS-49970 – Improved performance of delta APT metadata rebuilds for large hosted repositories by optimizing how metadata updates are written to the database. NEXUS-49845 – Corrected a race condition that caused npm group metadata updates to fail when handling non–URL-safe package names. NEXUS-49758 – Group repositories now correctly honor the offline status of member proxy repositories. NEXUS-49414 – Updated permission checks in the Browse interface. NEXUS-47679 – Improved synchronization of password changes across HA nodes to ensure updated credentials are recognized immediately. NEXUS-45388 – Improved the Admin - Cleanup Tags task to gracefully handle missing components by skipping over them. NEXUS-42793 – Improved PyPI index page handling in Repository Firewall by filtering out invalid component versions during processing. NEXUS-38502 – Corrected YUM group metadata handling so repositories with invalid or missing member metadata no longer return an empty repomd.xml, instead rebuilding metadata or returning a 404 to reflect the invalid state accurately.
Original source - May 7, 2026
- Date parsed from source:May 7, 2026
- First seen by Releasebot:May 8, 2026
Sonatype Nexus Repository 3.92.0 Release Notes
Sonatype releases Nexus Repository updates with a new Nexus One UI preview, broader support for Pub, Conda and Helm repositories, stronger migration and metrics APIs, default SSRF protection for new installs, and new Firewall webhooks and bulk waivers, plus bug fixes and a Java 25 requirement coming soon.
What’s New and Noteworthy in This Release?
Get a First Look at Sonatype Nexus Repository’s New User Interface
You can now preview a redesigned user experience in Sonatype Nexus Repository using a Switch to Nexus One UI toggle. This update introduces a more streamlined interface built to reduce clicks, improve navigation, and make repository search and browsing more intuitive. The new design aligns Nexus Repository with Sonatype’s other solutions, creating a more consistent experience across the Sonatype platform while lowering training overhead and cognitive load for users.
To access the preview, an administrator must first enable the feature under Settings > System > Nexus One UI. Some areas are still under development and will appear as Coming Soon, including Users, Roles, Privileges, Upgrade, and Licensing. You can also provide feedback directly within the UI to help guide ongoing improvements as we continue to expand coverage and accelerate feature delivery.
Pub Repository Support for Dart and Flutter
Sonatype Nexus Repository now supports Pub repositories, enabling you to manage Dart and Flutter packages directly within your repository manager. With support for proxy, hosted, and group repositories, you can centralize access to public packages from pub.dev, publish internal packages with versioned metadata and checksums, and aggregate multiple repositories into a single endpoint. This integration helps improve control over package consumption and distribution while reducing reliance on external sources.
For full details, see the Pub repositories help documentation.
Support for Conda Hosted and Group Repositories
Sonatype Nexus Repository now includes hosted and group repository support for Conda, providing a complete solution for managing Python and data science packages.
With hosted repositories, you can publish proprietary Conda packages with full version control and automatically generated metadata. Group repositories allow you to combine proxy, hosted, and other group repositories into a single endpoint, simplifying client configuration and enabling unified package resolution. These enhancements make it easier to manage Conda ecosystems at scale while improving consistency and efficiency across development workflows.
For full details, see the Conda repositories help documentation.
Support for Helm Group Repositories
Sonatype Nexus Repository now supports Helm group repositories, allowing you to expose multiple Helm repositories through a single URL. By combining proxy, hosted, and other group repositories into one endpoint, you can simplify dependency management and reduce the need for complex client-side configuration.
For dull details, see the Helm repositories help documentation.
Instance Migrator Support for Migrating Swift, Terraform, and Conda Hosted Repositories
The Sonatype Nexus Repository Instance Migrator now supports migrating Swift, Terraform, and Conda hosted repositories, making it easier to move modern package ecosystems between instances. This enhancement helps you migrate critical artifacts and repository configurations with greater confidence, reducing manual effort and minimizing disruption during upgrades, consolidations, or infrastructure changes.
The migrator focuses on transferring essential package assets, such as Swift package archives and manifests, Terraform provider and module packages (including associated checksum and signature files), and Conda package binaries across supported architectures. Automatically generated metadata is excluded during migration and regenerated on the target instance, helping ensure consistency and integrity without unnecessary data transfer. This approach streamlines migrations while preserving repository structure and expected package behavior.
For setup and technical details, see the Instance Migrator help documentation.
Database Connection Pool Metrics Accessible via API
Sonatype Nexus Repository now exposes HikariCP database connection pool metrics through the Service Metrics Data API, providing deeper insight into system health and database utilization. You can track active, idle, total, and pending connections across connection pools, helping you better understand real-time demand and identify potential bottlenecks.
With this added visibility, you can make more informed decisions about connection pool sizing and quickly troubleshoot performance issues without relying on external monitoring. Note that this API does not appear in the in-product Swagger; instead, check out our Service Metrics Data API help documentation for details.
Server-Side Request Forgery (SSRF) Protection Enabled by Default and New SSRF API Endpoint
Sonatype Nexus Repository now enables SSRF protection by default for new installations, helping you secure outbound connections and reduce exposure to malicious requests without requiring additional setup. Existing installations are not impacted by this change, avoiding unintended service disruption. You can review your configuration, add trusted internal endpoints to an allowlist, and enable protection when ready.
This release also introduces a new administrative API to manage SSRF protection settings, giving you more flexible and centralized control over enablement and configuration. For full details, see the help documentation on securing Nexus Repository.
Usage Insights Dashboard Retains Daily Storage Metrics
The Usage Insights dashboard now retains daily storage metrics indefinitely, giving you a complete and uninterrupted view of storage trends over time. By aligning storage retention with the existing egress metrics model, this update eliminates gaps in historical data and provides more reliable long-term visibility.
With continuous access to storage usage history, you can better analyze growth patterns, support capacity planning, and make more informed decisions about repository management without losing critical historical context.
Webhook Support for Repository Firewall Events
Sonatype Repository Firewall now supports webhooks, providing real-time notifications when components are blocked or quarantined due to policy violations. This allows you to integrate Firewall events with external systems for faster incident response, alerting, and automation.
Webhook payloads include key details such as policy violations, threat levels, and component identifiers, helping you quickly understand and act on security events. Notifications also distinguish between new quarantines and repeated access attempts, giving you clear and actionable insight into Firewall activity.
For full details, see the Firewall Webhooks help documentation.
Firewall Bulk Waivers for Faster Quarantine Management
Sonatype Repository Firewall now supports Bulk Waivers, allowing you to waive multiple policy violations at one time while applying consistent scope, expiration, and context. This reduces manual effort and helps prevent inconsistencies when managing quarantined components across repositories.
Bulk Waivers are available directly from Repository Results or Component Details, making it easier to take action where quarantine status is visible. Built-in safeguards for unknown or unclaimed components help maintain control, while a complete audit trail ensures traceability for all actions.
For full details, see the Firewall Bulk Waivers and Bulk Waivers API help documentation.
Bug Fixes
Issue ID | Description
NEXUS-52054 | Terraform hosted repository signing key material and passphrase are now redacted in support zip exports.
NEXUS-51930 | Firewall policy evaluation now applies to conditional GET requests (If-None-Match / If-Modified-Since), ensuring quarantined components return 403 Forbidden rather than 304 Not Modified.
NEXUS-51909 | Corrected PyPI proxy chaining so package downloads resolve with the repository path intact, preventing 404 errors when retrieving components through a proxy-to-proxy configuration.
NEXUS-51882 | PyPI hosted repository metadata stays consistent during concurrent uploads, with index assets marked as stale and rebuilt on demand rather than deleted mid-operation.
NEXUS-51864 | Version-specific npm requests (e.g., /package/latest) no longer invalidate the PCCS cache, ensuring subsequent full metadata requests return the complete set of available package versions.
NEXUS-51814 | Docker tag pagination Link headers now preserve the original connector-based request path, allowing clients to correctly retrieve subsequent pages of tags.
NEXUS-51795 | The user-configured SAML Entity ID URI now takes precedence over the browser URL when building SP metadata and authentication requests.
NEXUS-51699 | The BlobRepositoryMismatchTask now saves per-repository progress checkpoints, resumes after node restart, logs completion status and throughput, and scales thread count based on CPU cores.
NEXUS-51659 | The Search API now returns a 400 error with a descriptive message when unsupported wildcard patterns are used in the repository name field.
NEXUS-51633 | PyPI repository indexes are automatically invalidated and rebuilt on the next client request following a "Verify and Repair" blob restore operation.
NEXUS-51540 | Maven group repository metadata propagates correctly through all nesting levels when new component versions are uploaded.
NEXUS-51523 | The Repair - Data Repair Plan task summary log now reports "created plan entries" instead of "created plans."
NEXUS-51509 | Concurrent Policy Compliant Component Selection requests are now deduplicated, reducing redundant upstream evaluations.
NEXUS-51485 | Docker pull errors for quarantined images now include the quarantine reason and IQ report URL directly in the response body.
NEXUS-51397 | The repository.blob.mismatch.task upgrade task now processes blobs concurrently without blocking other upgrade tasks.
NEXUS-51391 | Content selectors using "starts with" expressions now correctly filter results for short path segments.
NEXUS-51334 | Fallback member retrieval in npm group repositories now logs clearer DEBUG-level messages without misleading Firewall references.
NEXUS-51327 | Wildcard component name searches against paths with leading slashes now return correct results across all formats.
NEXUS-51319 | npm proxy repositories now send valid ETags, ensuring cached tarballs return 304 responses instead of triggering re-downloads.
NEXUS-51283 | This fix changes RubyGems metadata behavior so uploads trigger incremental index updates rather than full repository rebuilds.
NEXUS-51282 | Download URLs in UI search results now point to the group repository path, allowing access without 403 errors.
NEXUS-51281 | The Firewall Proprietary Names task now correctly implements the Cancelable interface.
NEXUS-51279 | Search API requests using unsupported wildcard patterns now return HTTP 400 with a descriptive error message.
NEXUS-51267 | Failed login attempts are again captured in the audit log with user ID, IP, and failure reason.
NEXUS-51266 | text_pattern_ops indexes enable efficient prefix searches, eliminating slow sequential scans on large databases.
NEXUS-51247 | Concurrent requests for the same component no longer generate ERROR-level log entries during blob property updates.
NEXUS-51112 | Policy Compliant Component Selection now uses an increased timeout for PyPI metadata evaluation, supporting large packages.
NEXUS-50971 | Upgrade ensures LDAP configuration events deserialize correctly across HA nodes, preventing REST API failures.
NEXUS-50945 | OAuth2/OIDC authentication now uses Nexus’s managed HTTP client, supporting truststore and proxy settings.
NEXUS-50782 | NuGet v2 proxy repositories now follow OData pagination links, ensuring all package versions are retrieved.
NEXUS-49855 | Prefix wildcard searches now correctly match only components that begin with the specified term.
NEXUS-48607 | The UI no longer experiences delays on initial load when telemetry endpoints are unreachable.
NEXUS-43728 | Audit logs in HA clusters now record blob store creation events only on the originating node.
NEXUS-40929 | The Health Check column automatically hides from Browse and Repositories pages when IQ Server Firewall is enabled, preventing unnecessary API calls since Firewall provides vulnerability data directly.Coming Soon to Sonatype Nexus Repository
Java 25 Required as of 3.93.0
Starting with version 3.93.0, Sonatype Nexus Repository will require Java 25. This update ensures continued alignment with supported Java versions and enables access to the latest performance improvements and security enhancements provided by the Java platform.
Original source - Apr 8, 2026
- Date parsed from source:Apr 8, 2026
- First seen by Releasebot:Apr 9, 2026
Sonatype Nexus Repository 3.90.0 - 3.90.3 Release Notes
Sonatype Nexus Repository adds Terraform group repositories, Swift hosted repositories, Recovery Mode, a new User Token API, and improved npm metadata visibility, while also delivering broad reliability, security, migration, and performance fixes across the platform.
Caution
Known Issue with npm Group Repositories in Sonatype Nexus Repository 3.90.2; Issue fixed in 3.91.0
Sonatype is aware of an issue in Sonatype Nexus Repository 3.90.2 where npm group repositories may serve stale package metadata after upstream repositories are updated. This issue is fixed in version 3.91.0.
This issue occurs when requesting packages with versions or dist-tags (for example, npm install storybook@latest or npm install @sonatype/[email protected]). The cache invalidation process fails, causing the group repository to return outdated version information.
Symptoms may include:
- npm builds failing with version mismatch errors.
- Recently published package versions not visible through the group repository
- Server logs showing errors such as: IllegalArgumentException: Non URL-safe name
Workaround:
Manually invalidate the package cache through the Nexus UI: Browse → Select repository → Right-click package → Invalidate cache
What's New in 3.90.3?
Released April 8, 2026
Note
Sonatype Nexus Repository 3.90.3 is available for download from the Nexus Repository 3 Download archive.
Added Skip Processing Configuration
NEXUS-51666 – Added a skipProcessing configuration option to BlobRepositoryMismatchTask for eligible direct upgrades. See our Support Knowledgebase article for details.
What's New in 3.90.2?
Released March 23, 2026
New Instance Migrator Helps Nexus Repository 3.70.5 Deployments Move to Nexus Repository Cloud or Self-Hosted Nexus Repository 3.90.2 Without Downtime
Sonatype Nexus Repository now provides a migration path from OrientDB 3.70.5 to modern, supported platforms without requiring service interruption. With the new Instance migrator, you can migrate to either of the following without downtime:
- Nexus Repository Cloud
- Nexus Repository self-hosted version 3.90.2+
Migration preserves core configuration and repository data, enabling a seamless transition to a more scalable and supported architecture.
Key Capabilities
Preserves repository data and configuration
Migrates hosted repository content, repository configurations, and associated settings to the target environment.
Maintains user and access configurations
Transfers users, roles, and authentication mappings to ensure continuity of access control.
Secure handling of sensitive data
Encrypts and transfers secrets using supported security standards during migration.
Automated validation checks
Prevents invalid configurations, such as missing blob stores, and provides clear feedback during migration.
No service interruption
Keeps your source instance online and operational throughout the migration process.
Important Migration Requirements
Blob stores must exist on the target instance
Create blob stores in the target environment before migration. Do not reuse storage locations from the source instance.
Shared storage is not supported
Using the same S3 bucket, Azure container, or file path across source and target instances can lead to data corruption.
LDAP/Crowd users require external server configuration
While user tokens and role mappings for LDAP/Crowd users will migrate successfully, the target instance must be manually configured to connect to the same external authentication servers for these users to authenticate after migration.
Some configurations require manual setup
SSL/TLS certificates export from the source but may require manual import configuration on the target instance depending on your environment.
Proxy/group repository cached content does not migrate
Only hosted repository content is migrated.
For full migration requirements and process details, see the Instance Migrator help documentation. You can download the instance migrator for version 3.70.5 from the OrientDB Downloads page.
Bug Fixes in 3.90.2
This release includes the following additional bug fixes
Issue ID | Description
NEXUS-51040 | Docker proxy repositories handle bearer token authentication requests without encountering null pointer exceptions during HTTP context operations.
NEXUS-50764 & NEXUS-39228 | Group repositories now properly detect policy-filtered version changes in member proxy repositories, ensuring metadata remains current and complete across npm and PyPI formats.
What's New in 3.90.1?
Released March 6, 2026
Fix for Nexus Repository 3.90.0 Community Edition
This release fixes an issue that prevented Sonatype Nexus Repository 3.90.0 Community Edition deployments from starting upon initial installation or upgrade.
Community Edition users can now safely upgrade to 3.90.1.
What’s New in 3.90.0?
Released March 5, 2026
Support for Terraform Group Repositories
Sonatype Nexus Repository now supports the Terraform group repositories, allowing you to aggregate multiple Terraform hosted and proxy repositories into a single endpoint. This capability simplifies configuration for developers by providing one consistent URL for Terraform modules and providers, while centralizing control and visibility for repository administrators.
Terraform group repositories include intelligent caching with configurable TTL values for modules and provider versions, along with request deduplication to reduce redundant upstream queries. When the same version exists in multiple member repositories, you can apply configurable conflict resolution strategies to determine which artifact is served. The implementation also tracks member health and automatically handles unhealthy members, while exposing comprehensive metrics to help you monitor cache performance and overall repository health.
For full details, see the Terraform Repositories help documentation.
Support for Swift Hosted Repositories
Sonatype Nexus Repository now supports Swift hosted repositories, enabling you to publish and manage Swift packages as .zip files with MIME type validation. This capability allows teams to securely store and distribute internal Swift artifacts and approved third-party components through Nexus Repository, providing a centralized and reliable source for Swift dependencies.
Swift hosted repositories support enterprise controls such as access management and auditing, along with optional anonymous access where appropriate. For full details, see the Swift Repositories help documentation.
Re-enabled Repair - Execute Data Repair Plan Task
In Sonatype Nexus Repository 3.90.0, the Repair - Execute Data Repair Plan task is re-enabled by default. We previously disabled this task in 3.88.0 to prevent potential data loss while we addressed issues affecting the Verify and Repair and Data Repair Plan tasks.
You can now safely use the Repair - Execute Data Repair Plan task to correct data inconsistencies between the database and blob store. This update restores the intended maintenance workflow and allows you to run data repair operations with confidence.
This re-enablement aligns with the introduction of Recovery Mode, which provides a controlled operational state to help protect data integrity during repair and reconciliation activities.
New Recovery Mode for Safe Data Reconciliation
Sonatype Nexus Repository now includes Recovery Mode, a controlled operational state designed to support safe reconciliation between the database and blob storage after outages or data inconsistencies. When enabled, Recovery Mode helps protect data integrity by preventing specific background tasks from interfering with repair operations. This feature is available only for self-hosted deployments and requires administrative privileges. Before enabling Recovery Mode, consult Sonatype Support to confirm it is appropriate for your situation.
For full details, see the Recovery Mode help documentation.
New User Token API
A new User Token API allows administrators to create, view, and delete user tokens. With the appropriate privileges, administrators can generate tokens for specific users and realms, retrieve token summaries (excluding sensitive fields), and manage tokens across individual or all realms, including options to include expired tokens in responses.
For full details, see the User Token API help documentation.
Improved Transparency for Policy-Compliant Component Selection in npm Metadata
Sonatype Nexus Repository now enhances policy-compliant component selection (PCCS) by exposing filtered npm package versions directly in the package metadata. When PCCS filters versions that violate your Repository Firewall policies, those versions appear in the sonatype_filtered_versions field in the component's metadata. This update provides clearer visibility into which versions were excluded, helping teams quickly understand why a version is unavailable and identify an acceptable alternative.
Granular Permissions for Log Management API in Nexus Repository Cloud Environments
Sonatype Nexus Repository Cloud now supports more granular access control for the Log Management API. Previously, access to the Log Management API required the broad nexus:* permission, which is granted only to the nx-admin role. You can now grant access to this API using the built-in nexus:logging:read permission and the associated nx-logging-read privilege. This update enables teams to follow the principle of least privilege by allowing service accounts to download logs without granting administrative access across the entire tenant.
Removed Legacy Application Health Check and Hosted Repository Analysis
In this release, we removed the legacy Application Health Check plugin from Sonatype Nexus Repository. This plugin previously provided both Application Health Check and Hosted Repository Analysis capabilities.
Sonatype Lifecycle replaces these capabilities with more robust and fully supported software composition analysis. Lifecycle offers CLI-based scans, binary uploads, comprehensive policy evaluation, and continuous monitoring across your development lifecycle.
Removing these features reduces technical debt, eliminates non-functional UI elements and APIs, and simplifies the Nexus Repository codebase.
Note
This change applies to self-hosted Nexus Repository deployments only. These capabilities were never available in Nexus Repository Cloud.
Bug Fixes
The following sections group recent fixes by functional area to make them easier to scan and reference. Together, they reflect improvements across repository formats, search, HA, storage, migration, security, usability, and operational reliability.
Repository Format–Specific Fixes
These fixes address behavior specific to individual repository formats such as Docker, Maven, NuGet, Yum, APT, Helm, npm, Terraform, and RubyGems. The updates improve metadata accuracy, caching behavior, authentication handling, concurrency, and client compatibility to ensure predictable and standards-compliant interactions across all supported ecosystems.
Issue ID | Description
NEXUS-50951 | From Nexus Repository version 3.89.0+, newly created Docker repositories must use lowercase names. This fix allows users to edit, via the UI, the configuration of upgraded Docker repositories that have mixed/upper case naming.
NEXUS-50929 | Raw hosted repositories now support anonymous access to paths matching Terraform provider patterns when anonymous access is enabled globally.
NEXUS-50181 | Optimized Docker image retrieval by digest to achieve performance comparable to tag-based pulls.
NEXUS-50105 | Imported Docker images now maintain the correct content-type metadata for manifests and tags.
NEXUS-50056 | Corrected the Docker tags pagination Link header to include the complete repository path.
NEXUS-49785 | Enhanced Firewall quarantine checks for Docker proxy repositories to better handle concurrent pulls.
NEXUS-46841 | Improved Docker token handling to reliably process concurrent authentication requests.
NEXUS-50362 | Maven repositories now correctly return 404 responses for non-existent checksum signature files.
NEXUS-50243 | Corrected maven-metadata.xml generation in nested Maven groups.
NEXUS-44467 | Improved Maven POM uploads to correctly handle version numbers containing hyphens.
NEXUS-50205 | NuGet v3 search queries now correctly handle format-specific sorting parameters.
NEXUS-45352 | NuGet group repositories now retrieve cached packages from available proxy members.
NEXUS-44177 | NuGet v3 search queries now return locally cached replicated packages.
NEXUS-50153 | Yum group repositories now serve cached metadata during background regeneration.
NEXUS-49769 | Browse UI now removes outdated Yum metadata entries after repodata regeneration.
NEXUS-43881 | Improved cleanup of directory browse nodes in Yum repositories.
NEXUS-37102 | Optimized thread management in APT and Yum repositories to prevent blocking during concurrent operations.
NEXUS-23790 | The distribution field is now optional when configuring APT proxy repositories.
NEXUS-46491 | Helm repository metadata now updates correctly following database migration.
NEXUS-50706 | Improved cache invalidation for npm proxy repositories handling special-character package names.
NEXUS-50718 | Terraform hosted repositories now correctly generate and expose required provider metadata.
NEXUS-49752 | Firewall audits for RubyGems repositories now exclude metadata files from evaluation.
Search and Indexing
This set of fixes improves the accuracy, consistency, and performance of search operations. Enhancements address filtering logic, wildcard and token handling, database-specific behavior, and request optimization so that users and automation tools receive correct and complete results across deployment types.
Issue ID | Description
NEXUS-50711 | Checksum-based searches now correctly filter results when combined with repository or format parameters.
NEXUS-50435 | Improved search API handling of the prerelease parameter when using H2 databases.
NEXUS-49722 | Improved search tokenization to correctly index components with underscores in group names.
NEXUS-49164 | Enhanced search functionality in HA deployments to correctly handle wildcard queries with hyphens.
NEXUS-40204 | Optimized HEAD request handling in proxy repositories to improve response times.
High Availability, Clustering, and Concurrency
These updates strengthen reliability in clustered and high availability deployments. They resolve state consistency issues, improve concurrency handling, clarify clustering diagnostics, and reduce the likelihood of race conditions or configuration mismatches across nodes.
Issue ID | Description
NEXUS-50277 | Improved repository deletion in HA deployments to maintain consistent state across nodes.
NEXUS-50168 | Added warnings for unsafe file blob store paths in HA deployments.
NEXUS-48604 | Improved LDAP credential rotation handling in HA clusters.
NEXUS-46663 | Parallel API requests to create content selectors now complete successfully without race conditions.
NEXUS-40099 | Enhanced HA deployment log messages to clarify clustering configuration mismatches.
Blob Stores and Storage Management
These fixes focus on blob store validation, lifecycle management, and cleanup behavior. They improve correctness and resilience for both file- and S3-based storage, ensuring safe configuration, reliable deletion, and consistent data handling across UI and API operations.
Issue ID | Description
NEXUS-50503 | Improved credentials provider lifecycle management for S3 blob stores using AWS IRSA.
NEXUS-44209 | Compact blob store task now removes soft-deleted blobs after relocation.
NEXUS-37989 | Strengthened blob store name validation across UI and REST API operations.
NEXUS-28332 | Blobstore deletion now works correctly regardless of the chosen name.
Import, Export, and Migration
This group enhances upgrade, migration, import, and export workflows. The improvements ensure schema completeness, preserve metadata integrity, increase resilience to interruptions, and optimize performance when working with large or complex repositories.
Issue ID | Description
NEXUS-50612 | Upgrades from versions prior to 3.67.0 now include required database schema changes.
NEXUS-50402 | Asset import operations now preserve original uploader identity and IP address attributes.
NEXUS-45357 | Improved repository import process to handle non-UTF-8 metadata files.
NEXUS-42488 | Improved asset blob reference migration reliability after restarts or interruptions.
NEXUS-42251 | Optimized repository export prerequisite checks for large repositories.
NEXUS-34351 | Optimized import task performance for repositories with millions of flat-directory assets.
NEXUS-34303 | Database migrator now handles assets referencing missing components with improved logging.
NEXUS-42709 | Database migration logs now accurately reflect filtered records.
Security and Authentication
These changes improve system security posture and authentication reliability. They address third-party library vulnerabilities, permission model consistency, credential handling edge cases, and secure communication behavior across integrations and identity providers.
Issue ID | Description
NEXUS-50640 | SAML authentication now handles reverse proxy configurations that strip cookies during the identity provider redirect process.
NEXUS-49531 | Upgraded the CycloneDX core library to address an XML External Entity vulnerability.
NEXUS-47010 | Updated proxy repository authentication to properly handle passwords containing special characters.
NEXUS-47819 | Administrators can now remove all roles from SAML users through the API.
NEXUS-46805 | Simplified permission requirements for Content Replication configuration.
NEXUS-13303 | Improved email server connection handling to support plaintext SMTP when Trust Store is enabled.
UI, Permissions, and Usability
These fixes align user interface behavior with documented expectations and API behavior. They improve visibility, ordering, task reporting accuracy, and permission handling to create a more predictable and consistent administrative experience.
Issue ID | Description
NEXUS-50592 | Content selectors now appear in alphabetical order in the privilege dropdown.
NEXUS-48336 | Settings menu access now works correctly for users with nx-users-* privileges.
NEXUS-48281 | Task duration displays now reflect actual execution time.
NEXUS-40728 | Move Up and Move Down buttons now correctly reorder repositories in rebuild tasks.
Metrics, Logging, and Diagnostics
These updates enhance observability and troubleshooting. They improve log accuracy and persistence, align UI and API metrics, remove unused telemetry, and provide better diagnostic data to support operational monitoring and issue resolution.
Issue ID | Description
NEXUS-50133 | Support zip log truncation now retains the most recent log entries.
NEXUS-48701 | Removed the unused nexus_cluster.log file from deployments.
NEXUS-47716 | Metrics displayed in the UI now align with REST API values.
NEXUS-47618 | Removed unused S3 blob storage metrics from the Prometheus endpoint.
NEXUS-47362 | ROOT logger level settings now persist across system restarts.
NEXUS-46315 | Added JVM memory and garbage collection monitoring logs.
Configuration and Deployment
This category includes fixes that improve installation, configuration validation, and deployment workflows. The changes clarify documentation, prevent common misconfigurations, and ensure operator- and platform-based installations behave as expected.
Issue ID | Description
NEXUS-47399 | Corrected PostgreSQL configuration documentation examples.
NEXUS-45379 | H2 database backup task now trims whitespace from configured backup paths.
NEXUS-43752 | OpenShift Operator now correctly populates the ingress TLS hosts field.
Performance and Startup Optimization
These improvements reduce startup time and operational overhead. They streamline scheduler initialization and capability loading to help instances become fully operational more quickly after restart or configuration changes.
Issue ID | Description
NEXUS-46266 | Optimized Firewall Audit Capability initialization to reduce startup time.
NEXUS-50273 | Improved Quartz scheduler initialization to reduce restart delays.
Coming Soon
Change to Nexus Repository Docker Image Base and Tagging
As of 3.91.0, the base nexus3 image will be built off of alpine instead of ubi. This should be an invisible change for anyone using our image from dockerhub. If you are building an image off of our image, you will need to update your build process. Effective with 3.94.0, we will no longer publish new versions of the nexus3 image with the -ubi and -alpine suffix.
Change to Private Network Blocking Default Behavior
Sonatype Nexus Repository will soon block private networks by default. Customers are encouraged to review their configurations for any internal IP addresses or private network ranges and update them as needed to prevent service disruptions.
Note that this is a change to the default behavior only; you will still be able to configure this setting to allow private network access if your deployment requires it.
This update is designed to improve security by preventing unauthorized or unintended access from Nexus Repository to internal services. It helps protect production environments where repository administrators should not be able to connect to arbitrary internal endpoints.
Note that this was previously planned to become the default behavior in the 3.90.0 release; however, we have delayed its implementation to a future release.
Original source - Apr 7, 2026
- Date parsed from source:Apr 7, 2026
- First seen by Releasebot:Apr 9, 2026
Sonatype Nexus Repository 3.91.0 Release Notes
Sonatype Nexus Repository 3.91.0 adds a new Instance Migrator, Swift group repository support, database connection pool metrics, preserved proxy settings during migration, automatic Yum metadata regeneration, and global firewall quarantine webhooks, while also updating Docker image tagging and AWS reference architectures.
What’s New and Noteworthy in This Release?
In Case You Missed It: New Instance Migrator
In Nexus Repository 3.90.2 (March 23, 2026), we introduced a new Instance Migrator, which allows those on OrientDB-based Nexus Repository 3.70.5 to migrate to either Nexus Repository Cloud or self-hosted version 3.90.2+ without downtime.
Migration preserves core configuration and repository data, enabling a seamless transition to a more scalable and supported architecture. See the Nexus Repository 3.90.2 release notes for high-level details and the Instance Migrator help documentation for an in-depth look at the migration process and requirements.
You can download the instance migrator for version 3.70.5 from the OrientDB Downloads page.
Docker Tagging Update for Nexus Repository Images
As of release 3.91.0, Sonatype Nexus Repository has updated its Docker image tagging strategy, making the Alpine-based image the default variant. With this change, the 3.91.0, 3.91.0-alpine, and latest tags now point to the Alpine image, while the 3.91.0-ubi tag continues to reference the UBI-based image. Shifting the default to Alpine lowers risk exposure and improves security posture for containerized deployments.
Support for Swift Group Repository Format
Sonatype Nexus Repository now supports Swift group repositories, enabling you to aggregate multiple Swift package sources into a single endpoint. This capability simplifies dependency management by allowing teams to configure a single repository URL while seamlessly pulling components from multiple hosted, proxy, or group repositories. By consolidating access, you can reduce configuration overhead and improve consistency across development workflows.
For full details, see the Swift Repositories help documentation.
Database Connection Pool Metrics Available Through the Metrics API
Sonatype Nexus Repository now exposes database connection pool metrics through the metrics API, providing visibility into active, idle, and pending connections. This enhancement allows administrators to better understand how database resources are utilized in real time, without requiring additional tooling or manual inspection.
Preserved Proxy Repository Configuration During Migration
Sonatype Nexus Repository now preserves authentication credentials and HTTP request settings when migrating proxy repositories from OrientDB to self-hosted instances. Key configurations, such as connection timeout, retry attempts, and user agent values, carry over automatically, reducing the need for post-migration setup and ensuring repositories remain operational immediately after migration.
If authentication credentials cannot be securely migrated due to missing encryption configuration, Nexus Repository removes only the credential details while retaining all other repository settings. This approach maintains repository integrity while prompting you to reconfigure sensitive information as needed.
Automated Yum Repository Metadata Regeneration
Sonatype Nexus Repository now automatically regenerates Yum repository metadata during repository migrations, including required files such as repomd.xml and associated .xml.gz files. This enhancement ensures migrated repositories remain complete and immediately usable, eliminating the need for manual metadata repair or post-migration steps.
Global Webhooks for Firewall Quarantine Events
Sonatype Repository Firewall now supports global webhooks for quarantine events, automatically notifying your systems when components are quarantined or blocked due to policy violations. This capability enables seamless, real-time integration with your existing security and DevOps workflows, reducing the need for manual monitoring.
Cloud-Native AWS Reference Architectures for Sonatype Nexus Repository
Sonatype is now providing new cloud-native AWS reference architectures for Sonatype Nexus Repository, replacing the legacy reference architectures 1–4. The updated set includes five right-sized deployment options (XS, S, M, L, and XL) designed to support a range of scalability and performance needs. Each architecture includes Terraform configurations to simplify provisioning and accelerate time to value, enabling teams to deploy Nexus Repository in AWS with greater consistency and reduced operational overhead.
These architectures are now published in the Platform Cloud-Native Reference Architectures section alongside the existing IQ reference architectures, reinforcing Sonatype’s platform-oriented approach. The Sonatype Platform AWS Reference Architectures landing page provides a high-level overview of each architecture with links to specific details for each option. The previous Nexus Repository reference architectures are now marked as "Legacy" and will be removed in a future release.
Bug Fixes
This section summarizes the bug fixes included in Nexus Repository 3.91.0, grouped by functional area to highlight the most relevant improvements. The updates focus on improving repository correctness, system stability, performance, and user experience, while also addressing edge cases across supported formats and deployment environments. Each category provides a high-level view of related fixes, with details for individual issues listed below.
npm and PyPI Fixes
These updates focus on improving metadata accuracy, caching behavior, and policy enforcement for npm and PyPI repositories. They address inconsistencies caused by filtering, improve logging visibility for policy decisions, and ensure repository responses remain correct and performant under concurrent and edge-case scenarios.
Docker Fixes
These fixes target Docker repository behavior, focusing on correctness, scalability, and standards compliance. They improve handling of large datasets, manifest and tag integrity, permission evaluation, and compatibility with modern OCI image formats.
Other Repository Format Fixes
These changes improve compatibility and correctness across a range of repository formats, including Maven, Terraform, Conan, Yum, and others. They address edge cases in metadata handling, packaging behavior, and protocol support to ensure consistent interactions with upstream tools and clients.
High Availability, Concurrency, and System Stability
These updates improve system resilience under load, particularly in high availability and multi-node environments. They address concurrency issues, reduce the likelihood of deadlocks or timeouts, and ensure consistent behavior during distributed operations and resource-intensive tasks.
Blob Stores, Storage, and Data Integrity
These fixes focus on improving reliability and correctness in storage-related operations, including blob store management, migrations, and data consistency. They help ensure accurate metadata, prevent data loss, and improve behavior during concurrent or complex storage operations.
UI, Permissions, and User Experience
These updates enhance usability and consistency across the user interface and permission model. They resolve visibility issues, improve navigation behavior, and ensure that access controls and UI elements behave predictably for different user roles.
Logging, Observability, and Diagnostics
These changes improve visibility into system behavior through enhanced logging and diagnostics. They make it easier to troubleshoot issues by providing clearer, more detailed log output and ensuring relevant operational events are properly recorded.
Authentication and Security
These fixes strengthen authentication flows and ensure accurate enforcement of access control policies. They address issues with session handling, role synchronization, and HTTP response codes to provide clearer and more secure behavior.
Search and Indexing
These updates improve the reliability and accuracy of search and indexing operations. They address performance limits, ensure correct query matching behavior, and guarantee that index updates are applied consistently before results are returned.
Scheduled Tasks and Background Jobs
These fixes improve the reliability and behavior of scheduled and background tasks. They ensure task configurations persist correctly, prevent failures during upgrades, and provide better resource management and visibility into task execution progress.
Coming Soon to Sonatype Nexus Repository
Transition to Alpine-Only Docker Images (UBI Deprecation Notice)
Starting with Sonatype Nexus Repository 3.94.0, the Alpine-based image will become the sole supported variant, with both the 3.94.0 and latest tags pointing to Alpine. Version 3.93.x will be the final release to include the -ubi tag, providing a transition window for teams that still rely on the UBI-based image.
Original source - Mar 23, 2026
- Date parsed from source:Mar 23, 2026
- First seen by Releasebot:May 8, 2026
Sonatype Nexus Repository 3.70.0 - 3.70.5 Release Notes
Sonatype releases Nexus Repository 3.70.5 with a new Instance Migrator that helps move from OrientDB to Nexus Repository Cloud or the latest self-hosted release without downtime, while preserving core data, configuration, and access settings. It also reinforces the OrientDB sunset path.
Important
The Nexus Repository 3.70.x line is the last release line to support OrientDB. If you must remain on OrientDB, you will need to remain on our 3.70.x release line until you can migrate to H2 or PostgreSQL.
As of January 9, 2026, OrientDB is considered officially sunset.
What's New in 3.70.5?
Released March 23, 2026
Here's what's new in 3.70.5:
New Instance Migrator Helps You Move to Nexus Repository Cloud or the Latest Self-Hosted Release Without Downtime
Sonatype Nexus Repository now provides a migration path from OrientDB 3.70.5 to modern, supported platforms without requiring service interruption. With the new Instance migrator, you can migrate to either of the following without downtime:
- Nexus Repository Cloud
- Nexus Repository self-hosted version 3.90.2+
Migration preserves core configuration and repository data, enabling a seamless transition to a more scalable and supported architecture.
Key Capabilities
- Preserves repository data and configuration
Migrates hosted repository content, repository configurations, and associated settings to the target environment.
- Maintains user and access configurations
Transfers users, roles, and authentication mappings to ensure continuity of access control.
- Secure handling of sensitive data
Encrypts and transfers secrets using supported security standards during migration.
- Automated validation checks
Prevents invalid configurations, such as missing blob stores, and provides clear feedback during migration.
- No service interruption
Keeps your source instance online and operational throughout the migration process.
Important Migration Requirements
- Blob stores must exist on the target instance
Create blob stores in the target environment before migration. Do not reuse storage locations from the source instance.
- Shared storage is not supported
Using the same S3 bucket, Azure container, or file path across source and target instances can lead to data corruption.
- LDAP/Crowd users require external server configuration
While user tokens and role mappings for LDAP/Crowd users will migrate successfully, the target instance must be manually configured to connect to the same external authentication servers for these users to authenticate after migration.
- Some configurations require manual setup
SSL/TLS certificates export from the source but may require manual import configuration on the target instance depending on your environment.
- Proxy/group repository cached content does not migrate
Only hosted repository content is migrated.
For full migration requirements and process details, see the Instance Migrator help documentation. You can download the instance migrator for version 3.70.5 from the OrientDB Downloads page.
What's New in 3.70.4?
Released February 13, 2025
Here's what's new in 3.70.4:
New Docker Tag for 3.70.x Releases
Sonatype Nexus Repository now publishes a latest-3.70.x tag on Docker Hub for the 3.70.x OrientDB releases. This tag ensures that customers using the 3.70.x series can consistently pull the most recent version without affecting deployments that rely on the main latest tag.
Bug Fixes
Sonatype Nexus Repository release 3.70.4 fixes multiple bugs. See the Bug Fixes section for details.
What's New in 3.70.3?
Released October 10, 2024
Sonatype Nexus Repository 3.70.3 fixes two cleanup policy-related bugs. We switched the order of staging delete and move operations to avoid a concurrency issue when running staging move and cleanup tasks at the same time. We also resolved an issue that was preventing the option to retain a select number of previous versions when running cleanup from working as expected.
- Upgraded protobuf-java from 1.36.0 to 3.25.5
- Upgraded pax-url-aether from 2.6.7 to 2.6.12
What's New in 3.70.2?
Released September 3, 2024
Sonatype Nexus Repository 3.70.2 fixes a Database Migrator issue that caused some customers to see duplicate key errors after migrating from OrientDB to H2. Both Pro and OSS users seeking to migrate from OrientDB to H2 should now upgrade to 3.70.2 and then use the 3.70.2 Database Migrator to move to H2.
- Upgraded axios back to 1.6.4
What’s New in 3.70.1?
Released July 10, 2024
Sonatype Nexus Repository 3.70.1 fixes an issue that broke UI functionality in instances using a custom context path. This issue only impacted the UI and did not impact other functionality (e.g., requests for components). Sonatype Nexus Repository deployments should upgrade to 3.70.1 when possible.
- downgraded axios to 0.27.2 to address the issue
What’s New in 3.70.0?
Released July 9, 2024
Here's what's new in Nexus Repository 3.70.0.
H2 Database Upgraded to Version 2.2.244
Tip
Required Action Before Upgrading
If you are using an H2 database, you must use the Admin - Export SQL database to script task (released in 3.69.0) to create a SQL script export of your H2 database before upgrading to Nexus Repository 3.70.0. This means you must upgrade to 3.69.0 before upgrading to 3.70.0.
In release 3.70.0, we have upgraded Sonatype Nexus Repository’s embedded H2 database to use version 2.2.244. As there are considerable changes between version 1.4.200 and 2.2.244, those using an H2 database will need to take some additional steps to upgrade to Nexus Repository 3.70.0.
In release 3.69.0, we added an Admin - Export SQL database to script task you can use to create a SQL script export of your H2 database. If you are using an H2 database, you will need to run this task and follow our H2 upgrade instructions in order to upgrade to release 3.70.0. This means that you must upgrade to version 3.69.0 before upgrading to 3.70.0.
You can learn more about the differences between the H2 1.x and 2.x version lines in the H2 documentation.
If you are unsure what database your deployment is using, follow the help documentation for determining your current database.
Create and Manage Cleanup Policies via New REST API (Pro Only)
Administrators can now create and manage cleanup policies using the REST API, making it easier to enhance automation in your DevOps workflows and take advantage of a powerful Nexus Repository feature without having to access the user interface.
The new API allows you to retrieve, create, update, and delete cleanup policies. Learn more in our Cleanup Policies API documentation.
This feature was made possible through your feedback in the Sonatype Ideas portal.
Create and Manage Tasks via API (Pro Only)
Administrators who prefer to work via API instead of the user interface can now create, update, and delete tasks through new endpoints in the Tasks REST API. Learn more in our updated Tasks API documentation.
This feature was made possible through your feedback in the Sonatype Ideas portal.
Retrieve and Set IQ Audit and Quarantine Statuses via API (Pro Only)
Sonatype Nexus Repository deployments that are also using Repository Firewall can now leverage Nexus Repository’s IQ REST API to retrieve and set audit and quarantine statuses for repositories. This allows administrators to configure further automation of CI/CD pipelines. Learn more in our updated IQ API documentation.
This feature was made possible through your feedback in the Sonatype Ideas portal.
New Database Migrator Flow
We have changed our Database Migrator flow to improve performance and reliability. Check out our help documentation for the new steps for migrating your database.
OrientDB, Java 8, and Java 11 Enter Extended Maintenance
Release 3.70.0 marks a turning point for Sonatype Nexus Repository as it is the final release that will include OrientDB alongside H2 and PostgreSQL. Starting in August 2024, OrientDB, Java 8, and Java 11 will all enter extended maintenance as defined in our Sunsetting documentation. Release 3.71.0+ will require either an H2 or PostgreSQL database and Java 17.
Note
Note that both H2 and PostgreSQL are currently only available to Pro customers. We expect to announce a new database option for OSS customers and will provide detailed migration paths in our August 2024 release.
Sonatype is invested in continually improving our solutions to take advantage of newer, more advanced technologies. As such, we are strategically moving away from legacy technologies like OrientDB, Java 8, and Java 11 and investing in supporting newer database options and Java versions. Moreover, Sonatype has observed data integrity problems in some deployments using OrientDB.
As migrating to H2 or PostgreSQL can take some time and planning, Sonatype will continue to provide security patches and critical bug fixes to release 3.70.0 while it is in extended maintenance. We encourage Sonatype Nexus Repository Pro customers using an OrientDB database to follow our documentation for migrating to H2 or PostgreSQL.
Dependency Updates in 3.70.0
- commons-io upgraded to 2.15.0
- org.apache.commons: commons-compress upgraded to 1.26.1
- com.h2database : h2 upgraded to 2.2.224
- axios upgraded to 1.6.4 (Note: this update was reverted in Nexus Repository 3.70.1)
Bug Fixes
Bug fixes in Nexus Repository 3.70.x.
[Issue ID] [Description]
NEXUS-45471 (Release 3.70.4) Resolved an issue that impacted Azure blob store users where attempting to download binary files exceeding 2GB could cause Nexus Repository to become unresponsive.
Original source
NEXUS-45363 (Release 3.70.4) Resolved an issue that prevented the Retain Select Versions Cleanup Policy option (PostgreSQL-only) from displaying in the UI.
NEXUS-45286 (Release 3.70.4) OrientDB users are now able to create and edit cleanup policies as expected.
NEXUS-45283 (Release 3.70.4) Improved the responsiveness of Nexus Repository when interacting with Azure blob storage in HA environments by adding timeouts to prevent delays.
NEXUS-44780 (Release 3.70.4) The Number of Versions option now displays as expected in the user interface when creating a Docker cleanup policy.
NEXUS-44578 (Release 3.70.4) Enabling/disabling a capability on one node in an HA cluster enables/disables it on other nodes as well and no longer results in a deadlock in some cases.
NEXUS-44351 (Release 3.70.4) Database Migrator - Improved logging for filtered assets.
NEXUS-43764 (Release 3.70.4) After migrating from OrientDB to PostgreSQL, the browse rebuild task only runs once.
NEXUS-43758 (Release 3.70.4) After migrating to a PostgreSQL database, the search rebuild index task only runs once.
NEXUS-39919 (Release 3.70.4) Users can search using the REST API or UI for components and assets as long as they have nx-search-read and nx-repository-view---browse permissions. Note that NuGet v2 does not need browse for searching while NuGet v3 does.
NEXUS-44370 (Release 3.70.3) Switched order of staging delete and move operations to avoid a concurrency issue when running staging move and cleanup unused asset tasks at the same time.
NEXUS-43516 Database Migrator version 3.70.1 - Resolved an issue that was causing some OrientDB to Postres migrations to fail with an error when a Maven2 repository contained npm assets.
NEXUS-44337 (Release 3.70.3) Resolved an issue that was preventing the option to retain a select number of previous versions when running cleanup from working as expected.
NEXUS-43935 (Release 3.70.2) Resolved a Database Migrator issue that was causing some users to see duplicate key errors after migrating from OrientDB to H2.
NEXUS-43523 (Release 3.70.1) Fixed an issue that broke UI functionality in instances using a custom context path. This issue only impacted the UI and did not impact other functionality (e.g., requests for components).
NEXUS-43307 Updated documentation to accurately state that access to SAML UI and API requires nx-all privileges.
NEXUS-43004 Errors will no longer be seen in HA mode.
NEXUS-42854 The npm view command works as expected for scoped packages.
NEXUS-42336 Database records that cause exceptions during database migration are appropriately logged.
NEXUS-39818 Running npm audit should no longer result in unexpected exceptions.
NEXUS-39799 In Yum repositories, all pathnames in the filelist.xml.gz file are properly escaped.
NEXUS-39462 If an asset’s format is incorrect, the Database Migrator will continue with migration and skip corrupted records.
NEXUS-22888 Added componentId validation when trying to view an asset that does not have a component. If the componentId is an empty string, string of blank spaces, null, or undefined, then the LifeCycle Component panel is not displayed. - Feb 3, 2026
- Date parsed from source:Feb 3, 2026
- First seen by Releasebot:Apr 9, 2026
Sonatype Nexus Repository 3.89.0 Release Notes
Sonatype releases Nexus Repository 3.89.x with Swift proxy and hosted Terraform repository support, faster UI page loads, expanded Terraform authentication, and a broad set of bug fixes for LDAP, APT metadata, permissions, HA, and repository reliability.
Known Issue in Sonatype Nexus Repository 3.89.0 - 3.89.1
Sonatype is aware of an issue in Sonatype Nexus Repository versions 3.89.0 - 3.89.1 where using the Admin - Remove a member from a blob store group task on a blob store group can cause moved blobs to become unreachable.
This issue is fixed in Nexus Repository 3.90.0. Upgrade to version 3.90.x before running the Admin - Remove a member from a blob store group task.
What's New and Noteworthy in 3.89.1?
Released February 11, 2026
Sonatype Nexus Repository release 3.89.1 fixes the following bugs:
- NEXUS-50621: Metadata generation for hosted APT repositories now correctly includes all applicable package versions in Packages files, ensuring clients receive complete and accurate repository metadata.
- NEXUS-50490: The LDAP configuration REST API now properly handles authentication password parameters when creating LDAP server connections.
- NEXUS-50487: The LDAP configuration API now correctly handles updates when using URL-encoded connection names in REST API requests.
- NEXUS-50473: User access to group repositories now correctly inherits read and browse permissions from member repositories, with consistent enforcement of content selectors across authorization checks and Browse previews.
- NEXUS-50338: LDAP configuration updates via REST API now reliably preserve all required fields during credential rotation and server configuration changes.
- NEXUS-48604: Enhanced LDAP credential rotation in High Availability clusters to ensure cache synchronization across all nodes when updating bind credentials.
What’s New and Noteworthy in 3.89.0?
Released February 3, 2026
Known Issue in Sonatype Nexus Repository 3.89.0
Sonatype is aware of an issue in release 3.89.0 that affects APT hosted repositories. Repository metadata may be incomplete or incorrect, even though all packages exist in the repository.
If you rely on APT hosted repositories, we recommend delaying your upgrade to 3.89.0 until a fix is available.
Support for Swift Proxy Repository Format
Sonatype Nexus Repository now supports the Swift proxy repository format, enabling teams to integrate Swift Package Manager (SPM) into their existing repository management workflows.
Nexus Repository provides a registry-based alternative to SPM’s traditional Git-based dependency resolution, offering an HTTP- and JSON-driven approach to discovering, resolving, and consuming Swift packages. This allows organizations to centralize access to public Swift packages, reduce reliance on external Git hosting services, and improve build performance through caching and reuse of dependencies.
Swift proxy repositories are available in both Pro and Community editions. Teams can apply enterprise controls such as access management and auditing while continuing to support both registry-based dependencies (available with Swift 5.7 and later) and Git-based dependencies.
For full details, see our Swift Repositories help documentation.
Support for Terraform Hosted Repository Format
Sonatype Nexus Repository now extends its Terraform support to include hosted repositories. With hosted Terraform repositories, you can centrally distribute Terraform modules as versioned source archives and platform-specific binaries as well as Terraform providers packaged as .zip files. This enables teams to securely host internally developed Terraform assets and reduce reliance on external sources.
This enhancement also streamlines provider management by automatically generating required provider metadata, checksum files, and GPG signatures, while supporting multiple provider versions and incremental platform uploads. Repository-level permissions allow you to control access to Terraform content, and full REST API support makes it easier to automate repository and artifact management as part of your infrastructure-as-code workflows.
For full details, see our Terraform Repositories help documentation.
Expanded Authentication Options for Terraform
Sonatype Nexus Repository now enables access to Terraform repositories through expanded authentication support.
Terraform repositories can now be accessed using anonymous access when enabled, allowing unauthenticated clients to discover and retrieve provider versions without authorization failures.
In addition, authentication logic now correctly validates Base64-encoded username and password tokens, allowing Terraform clients to authenticate successfully without relying on Pro-only user tokens.
Improved User Interface Performance and Faster Page Loads
This release significantly improves the Sonatype Nexus Repository user interface by reducing initial page load times and making the application more responsive. Improvements include decreased bandwidth usage and improved caching efficiency, resulting in a more scalable, modern UI that performs consistently for users regardless of location or deployment size.
Change in Permissions for Executing Rolling Upgrades
The ability to inspect and execute rolling (i.e., zero-downtime) upgrades is now available to users with the nx-atlas-all privilege. This change simplifies access control by reducing the permissions required to manage rolling upgrades, enabling more teams to perform upgrade operations without expanding administrative privileges while still maintaining a secure deployment model.
Breaking change: SAML login requires SAML2_AUTH_REQUEST cookie
Starting in Sonatype Nexus Repository 3.89.0, SAML authentication requires the SAML2_AUTH_REQUEST cookie to complete the login flow. Environments, infrastructure, or browser configurations that block third-party cookies can prevent this cookie from being set, causing SAML login to fail after upgrade. Before upgrading, ensure that policies or browser settings allow the SAML2_AUTH_REQUEST cookie so that SAML authentication continues to function as expected.
Bug Fixes
This release delivers a wide range of fixes and improvements. For better readability, we’ve organized these improvements into logical sections below.
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.
Repository Storage, Uploads, and Data Integrity
This release includes several important improvements to how repositories handle data at scale, with a focus on stability, performance, and correctness during heavy operations. Changes address memory pressure during large uploads, race conditions during repository lifecycle events, safer execution of repair tasks, and more resilient database migrations and restores. Together, these fixes reduce the risk of outages, unexpected data loss, and failures during upgrades or maintenance in large or high-concurrency environments.
Formats and Ecosystem-Specific Fixes
A wide range of format-specific fixes improve reliability, performance, and standards compliance across supported ecosystems. Package managers such as APT, NuGet, npm, Maven, Docker, PyPI, Terraform, Conan, and Yum all benefit from targeted updates to metadata handling, search behavior, proxying, and rebuild logic.
Notably, Yum has received several improvements over the last couple of releases, including better metadata rebuild performance, safer handling of invalid group metadata, clearer diagnostics, and more efficient XML merging, resulting in more predictable behavior for large or complex Yum repositories.
Search, Browse, and Indexing
Search and browse functionality has been refined to be more accurate, predictable, and scalable, particularly in HA and large-repository environments. These changes improve filtering correctness, restore expected matching semantics, eliminate silent result truncation, and harden APIs against invalid requests. Performance optimizations also reduce the likelihood of failures during search rebuild tasks and high-volume query scenarios.
Security, Permissions, and Access Control
Several fixes improve how Nexus Repository evaluates permissions and access rules, both in terms of correctness and performance. Updates ensure that permission checks behave consistently across the UI and APIs, reduce authorization overhead in environments with frequent access checks, and ensure group repositories properly reflect the availability state of their members.
High Availability, Clustering, and Operations
HA and clustered deployments benefit from improved coordination, consistency, and operational safety. Fixes address credential synchronization across nodes, reduce migration-related memory issues, and improve the reliability and predictability of Helm-based HA deployments. These changes help ensure smoother upgrades and more stable behavior in multi-node environments.
UI and User Experience
User-facing workflows have been polished to remove friction, prevent common errors, and improve clarity. These updates include safer handling of whitespace in repository configuration, restored or simplified UI controls, and fixes to edge cases that could cause confusing behavior after session timeouts or during repository creation.
Logging, Monitoring, and Diagnostics
Logging and diagnostic output has been refined to be more actionable and less noisy. Improvements include clearer upgrade and metadata warnings, better visibility into long-running operations, consolidated request logging, and more informative startup and shutdown messages. These changes make it easier to troubleshoot issues and understand system behavior in production environments.
Tasks, Cleanup, and Maintenance
Maintenance and background tasks are now more resilient and resource-efficient, particularly when operating on large datasets. Enhancements ensure cleanup and repair tasks behave safely when encountering unexpected states, reduce memory usage during intensive operations, and improve overall system stability during scheduled or manual maintenance activities.
Documentation and API Fixes
Documentation and API examples have been corrected to better reflect supported behavior and real-world usage. These fixes remove misleading parameters and ensure example requests are accurate and usable, helping users avoid configuration errors and reducing friction when integrating with Nexus Repository programmatically.
Coming Soon to Sonatype Nexus Repository
Change to Nexus Repository Docker Image Base and Tagging
As of 3.91.0, the base nexus3 image will be built off of alpine instead of ubi. This should be an invisible change for anyone using our image from dockerhub. If you are building an image off of our image, you will need to update your build process. Effective with 3.94.0, we will no longer publish new versions of the nexus3 image with the -ubi and -alpine suffix.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.