Released: 17 November, 2025
Feature Enhancements
New REST APIs for VCS Remote Repositories to Obtain Data from Subgroup Repositories
New REST APIs have been added for VCS remote repositories to obtain data from subgroup repositories. Four new APIs have been added that allow you to:
Also, the legacy APIs Get VCS Tags and Get VCS Branches can be used to obtain VCS tags and branches from subgroup repositories.
Currently, branches and tags can be downloaded only in the tar.gz format.
In this Artifactory version, these APIs can be used to obtain data from the Google Source Git Provider.
Google Source Git Provider for VCS Remote Repositories
Support has been added in the Artifactory user interface for the Google Source Git Provider for VCS remote repositories. For more information, see Use VCS To Proxy Git Providers.
Improvements in VCS Remote Repositories APIs
The user organization can now be used as the repository for downloading VCS tags, branches, files in a tag, and files in a branch. For more information, see Download a VCS Tag, Download a VCS Branch, Download File within a VCS Tag, and Download File within a VCS Branch.
Support for New SCIM REST API Endpoints
The JFrog Platform now supports getting more information about your SCIM configuration and schemas via REST API. For more information, see Get Resource Types, Get Service Provider Configuration, Get Schemas, and Get Schema by ID.
Support Added for Decompressing .xz and tar.xz Files
Artifactory now supports decompressing .xz and tar.xz files, similar to the already supported decompression for .zip, .tar, and .gz files.
RLM promotion rollback from platform UI
To improve the user experience, you can now roll back a Release Bundle v2 version promotion from the platform UI. For more information, see Promotion Rollback. Please note that the UI icon for deleting a promotion has been removed, as rollback replaces this functionality.
Improved the Builds page performance
The pagination performance of the Builds page has been improved significantly to enhance the user experience.
Retention Policies - Package Version Pattern Filtering
Cleanup and Smart Archiving retention policies now support Include and Exclude Package Version Patterns. For more information, see Cleanup Policies and Smart Archiving.
Resolved Issues
JIRA Issue | Component | Severity | Description |
|---|---|---|---|
RTDEV-65895 | Packages | High | Fixed an issue whereby a race condition in the Debian indexing code was causing automatic indexing to not occur, which resulted in packages missing from the metadata. |
RTDEV-64461 | General | Medium | Fixed an issue whereby Artifactory was not following the RFC 9110 standard regarding the precedence of the precondition headers If-None-Match and If-Modified-Since. |
RTDEV-64026 | Packages | Medium | Fixed an issue whereby the npm remote repository with Curation complain version selection enabled would sometimes return the uncurated metadata ETAG header, which caused the npm client to not fetch the curated metadata from the registry even though the metadata was curated and changed. |
RTDEV-61244 | General | Medium | Fixed an issue whereby there was unauthenticated access to a Docker API when anonymous access was disabled. |
RTDEV-59638 | Release Lifecycle Management | Medium | Fixed an issue whereby deleting the last version of a Release Bundle did not remove the empty folder from the Release Bundle repository. |
JA-18099 | User management | Low | Fixed an issue whereby, when using the create or update Groups REST API and providing a string exceeding the maximum length, the JFrog Platform returned an incorrect error message. |