Sonatype Nexus Repository 3.87.0 is now available.
With this release, Sonatype Nexus Repository now minimally requires Java 21. This release also includes adjusted Community Edition usage limitations, a new Configuration API for instance configuration and metadata migration, and multiple bug fixes.
For full details, see the Sonatype Nexus Repository 3.87.0 Release Notes.
Why did you reduce the number of components stored on a Community Edition instance? Your justification makes no sense and is unwarranted — thank you for reverting it back to the previous state.
Do you truly believe users can operate under the constant threat of new limitations appearing in each upcoming release? You have now reduced them by more than 50%. The initial limitation introduced in 3.77 already caused significant disruption within our IT team. This latest change only deepens the frustration. If the goal had been to undermine the long-standing trust we had in Sonatype Nexus Repository, it could hardly have been more effective.
Hi! I understand the frustration here. I spoke to some leaders about your feedback.
We recognize that this change may create challenges for some users. We updated the usage limits for Nexus Repository Community Edition to keep the product sustainable and ensure we can continue delivering the reliability, security, and ongoing feature improvements that teams need. Community Edition remains free for smaller teams whose needs fall within the new limits, while larger or more complex environments will require Nexus Repository Pro or our cloud offering. These adjustments help us maintain a high-quality free option for the community and ensure that organizations operating at scale are using solutions built for that level of demand.
If you’re concerned that the new usage limits will cause friction, review our documentation on usage and remember that you’re only restricted from adding new components while you’re over the limits; when usage falls below the limits, the restriction is lifted.