Released: 02 February, 2026
Warning
Hugging Face Repository Layout Deprecation
As of June 2026, the Hugging Face repository layout will be deprecated.
All new local and remote Hugging Face repositories use the new Machine Learning repository layout by default. Any older repositories must be migrated before June 2026 to preserve complete functionality.
For more information, see Migrate Legacy Hugging Face Repositories.
Feature Enhancements
Improved Helm metadata processing
Helm metadata processing has been improved by eliminating redundant version comparison during repository indexing. This optimization reduces CPU overhead during index.yaml generation and virtual repository rewrites, significantly improving performance and scalability for repositories with a large number of chart versions.
Improved Pub error handling and status codes
For Pub clients older than version 2.15.0, error handling and status codes have been changed to align with proper authorization behavior. When a user without write permissions tries to download a package from a remote, virtual, or smart remote repository, Artifactory will now return HTTP
403 (Forbidden)instead of404.AQL Limit Applied to the Artifactory Server to Protect the Database Server from Overload
An AQL limit has been applied to the Artifactory Server to protect the Database Server from overload caused by excessive AQL search requests issued by end-users. The AQL limit includes concurrency limits at both global and per-user levels. This ensures that the database server has enough remaining capacity to serve other critical activities, such as upload and download.
Enhanced UI Support for DNF Client in RPM Packages
This release adds the DNF client option to RPM Set Me Up instructions. While Artifactory has long supported both YUM and DNF clients, the Set Me Up instructions previously only displayed YUM option. Artifactory is prioritizing the DNF client to align with modern RPM-based distributions where DNF is the default package manager.
Draft Release Bundle v2 versions
You can now use the Create Release Bundle v2 Version REST API to create an unlocked, mutable draft. Use the new Update Draft Release Bundle v2 Content REST API to add sources—such as artifacts, packages, builds, or bundles—as needed. When the draft is final, use the new Finalize Draft Release Bundle v2 Version REST API to lock the bundle and make it immutable. Please note that evidence cannot be added to a draft Release Bundle version until it is finalized. For more information about draft versions, including other limitations, see Create a Draft Release Bundle v2 Version.
Performance improvements when exporting Release Bundle v2 versions
We are excited to announce significant performance improvements to the export Release Bundle v2 feature. This enhancement provides a more efficient and streamlined experience for users in both self-hosted and SaaS environments. Key improvements include:
Faster processing times: Reduced export times for Release Bundles, allowing for quicker access to essential data.
Optimized resource usage: More efficient utilization of system resources during the export process, leading to enhanced overall performance.
Scalability enhancements: Improved handling of larger datasets, ensuring consistent performance with support for big bundles, allowing users to export extensive Release Bundles without performance degradation.
Resolved Issues
JIRA Issue | Component | Severity | Description |
|---|---|---|---|
RTDEV-73702 | Packages | High | Fixed an issue whereby npm virtual metadata ignored the override base URL for the X-Artifactory-Override-Base-Url header for certain packages. |
RTDEV-71255 | Repositories | Medium | Fixed an issue whereby platform-level and Artifactory-level proxy settings were affecting local repository replication settings. |
RTDEV-63325 | General | Medium | Fixed an issue whereby when attempting to download a file via a URL in the native browser, if Allow Anonymous Access was enabled but authorization was still required, a pop-up appeared requesting a username and password to complete the download instead of an auto-redirect to the SAML login page. |