Released: 30 June, 2025
Breaking Change for Access REST APIs
From this version, Access REST API responses will be returned as compact JSON and not as pretty-printed JSON. Note that some automatic parsers that rely on the formatting will require an update.
New Features
New REST API: Get Projects List for a Global Role
The JFrog Platform now supports getting a paginated list of projects where a specific global role is used. For more information, see Get Project List for a Global Role.
Feature Enhancements
API Run Summary Reports for Cleanup and Smart Archiving
Added new API endpoints for cleanup and smart archiving that provide detailed run summary reports in JSON format. For more details, refer toView Package Cleanup Policy Run Summary Report API and View Smart Archiving Policy Run Summary Report API.
Smart Archiving Packages: Evidence
Added support for the archival of evidence associated with any packages. This enhancement ensures that relevant evidence is preserved as part of your archiving strategy, streamlining your package management process. For more information, refer to Smart Archiving.
Property-based Policy Condition - Smart Archiving Packages
Enhanced package-archivie functionality with the addition of a property-based policy condition. You can now include or exclude specific package versions from archive by applying a property-based policy condition. This allows for more granular control over which packages are retained or archived during archive actions. For more information, see Create Smart Archiving Policy.
Filter Users and Groups by Role Within a Repository Via REST API The JFrog Platform now supports filtering users and groups by role within a specific repository via REST API. For example, you can easily retrieve a list of admins for a specific repository to streamline permissions management. For more information, see Get User List and Get a List of Groups.
Allow Granting Manage Permissions in Permissions V2
The JFrog Platform now supports allowing users with
managepermissions to grantmanageand other permissions to other users in Permissions V2, although it is not recommended. For more information, see Permissions.Support for Reading Permissions Scoped Tokens
It is now possible for non-admin users to use the Get Repository Configuration REST API endpoint using a scoped token. For more information, see Create Scoped Token.
Add Unlimited Groups to a Reference Token in SAML The JFrog Platform now supports adding an unlimited number of groups in SAML user-scoped reference tokens, as the number of groups does not affect the payload. For more information, see Create Token.
Removal and Backup of Mission Control Plugins
The following Mission Control plugins, which were created during the initial days specifically for Mission Control, are no longer required by any JFrog products. As a result, these plugins will be removed in this version and backup files are created with a
.backupextension.internalUser.groovyldapSettingsConfig.groovyldapGroupsConfig.groovyhaClusterDump.groovyrepoLayoutsConfig.groovyproxiesConfig.groovypropertySetsConfig.groovyrequestRouting.groovyhttpSsoConfig.groovypluginsConfig.groovy
For more information, see User Plugins documentation.
Release Bundle v2 promotion rollback
You can now use the REST API to roll back the latest promotion of a Release Bundle v2 version. Rollback deletes the contents of the latest promotion (including its artifacts, properties, and evidence) and restores the version to its previous environment, including the properties and evidence it contained when the version was first created. For more information, see Promotion Rollback.
Assigning a tag when creating a Release Bundle v2 version
You can now assign a tag when creating a Release Bundle v2 version with the REST API. Use the tag to identify the version quickly. For example, you can create tags such as nightly-build, release-candidate, bugfix-2025-33124, and so on. The tag will appear on the card for the Release Bundle version on the Release Lifecycle stages board.
Note
You can continue using the Assign Tag REST API to tag existing Release Bundle versions.
Version counter on Release Lifecycle kanban board
The Release Lifecycle kanban board now includes a counter so that you can see at a glance how many versions of the selected Release Bundle currently exist.
Improved error codes during Release Bundle v2 creation
Artifactory will now return 404 when an artifact or package is missing from the defined artifact or package list during Release Bundle v2 creation. In addition, Artifactory will return 403 when an artifact or package is filtered out due to a user permissions issue.
Evidence provider logo displayed on kanban board
Each evidence item displayed on the Release Lifecycle kanban board now includes a logo to indicate the provider of that evidence, whether it is evidence provided by the JFrog platform or evidence originating from other providers, such as GitHub or Sonar. The logo is also displayed prominently when the contents of the evidence item are opened.
Improvement in Promoting Docker Images
Starting from this Artifactory version, when Docker image promotion overrides an existing image tag in the target repository, shared layers from other tags of the same image will not be deleted. In versions prior to 7.117.1, these shared layers may be deleted.
CocoaPods Smart Repositories
The CocoaPods Settings section has been removed from the smart repository creation page. Smart repositories automatically inherit configuration from their source repository, making manual settings unnecessary.
Improved Robustness of Binary Uploads to Google Cloud Storage (GCS)
The robustness of binary uploads to GCS has been improved by enhancing recovery mechanisms.
Cocoapods CDN Smart Repository Support
Added smart repositories support for CocoaPods CDN.
Resolved Issues
JIRA Issue | Component | Severity | Description |
|---|---|---|---|
RTDEV-57859 | Packages | Medium | Fixed an issue whereby, the SAX parser failed when parsing filtered XML resources. |
RTDEV-57293 | General | Medium | Fixed an issue whereby an AQL transitive query on a virtual repository failed and returned a HTTP 500 response when the query was performed on a virtual repository that had an offline remote repository. |
RTDEV-57265 | Evidence Management | High | Fixed an issue that prevented users from deleting a repository containing evidence files. |
RTDEV-57055 | Release Lifecycle Management | Medium | Fixed an issue that caused the build cleanup procedure to fail after the associated project was deleted. |
RTDEV-56440 | General | Medium | Fixed an issue whereby the internal repository jfrog-usage-logs was included by default in the system backup, and was excluded from export/import repositories and export/import system flows. |
RTDEV-54817 | Release Lifecycle Management | Medium | Fixed an issue that prevented webhook notifications from being triggered for each artifact in a Release Bundle v2 promotion. After the fix, users who have configured artifact copy/move webhook notifications (and include |
RTDEV-45715 | Release Lifecycle Management | Medium | Fixed an issue whereby a build rename failed (because the build was not found in the defined project), but the operation was still reported as successful. After the fix, an error message is returned if a build with the specified name is not found in the defined project. |
RPG-1799 | General | High | Fixed an issue whereby when upgrading Artifactory in Windows to newer versions, Xray was unavailable. |
JA-18312 | Repositories | Medium | Fixed an issue related to repositories whereby, under certain circumstances, an extra '0' character appeared incorrectly next to the repository counter in the project tab in the JFrog Platform WebUI. |
JA-7684 | Archiving/Cold Storage | Medium | Fixed an issue whereby SaaS customers were able to execute the Access Export API. |
JA-16404 | Repositories | Medium | Fixed an issue related to Generic Repository Set-Me-Up whereby, when creating an identity token, the JFrog Platform did not include all required scopes. |
INST-9279 | Installation | Medium | Fixed an issue where the serviceName in the artifactory-statefulset.yaml and the artifactory-service.yaml files were not identical, causing DNS resolution failures. |