Artifactory 7.55.6 Cloud Self-Hosted

JFrog Release Information


Released: March 7, 2023


New UI Functionality to Clean up Artifactory Edge Release Bundles

To help admins manage Release Bundles and to clean up older items, JFrog created an automated cleanup process for received Release Bundles, which enables deleting target Release Bundles that were distributed to a specific Artifactory Edge instance. The automated process is managed using retention policies, which are set up using REST APIsRETENTION.JFrog REST APIs

In addition, a new Cleanup Report for Received Release Bundles, has been added the Platform UI, which enables admins to manage and to delete Release Bundles. All cleanup actions that are performed through this functionality are then recorded in the new Cleanup History function. For more information, see Managing Release BundlesManage Release Bundle Retention and Cleanup.Distribute Release Bundles (v1)

Added Option to Block Deletion of Release Bundles Marked as Keep

Added a new REST API that sets an indicator to keep (indefinitely) or not keep (don't keep) Release Bundles. When set to keep, if a user tries to delete this bundle (from the UI or REST APIs) they will receive an error message saying that the Release Bundle is protected and cannot be deleted.

Features and Enhancements

Google Cloud Storage Direct Upload Mechanism

From Artifactory 7.55.6, you have the option to select the Direct Upload Mechanism, whereby the upload is not considered successful until it reaches Google storage. We recommend that you use direct upload mechanism in comparison with the existing default Eventual Upload mechanismGoogle Storage Binary Provider Native Client Template

Resolved Issues

JIRA Issue



Fixed an issue whereby, when deleting external plugin dependencies from the $JFROG_HOME/artifactory/var/etc/artifactory/plugins/lib directory and then restarting Artifactory, the .JAR files were recreated as corrupted.


Fixed an issue whereby, when downloading an artifact that is marked as a Filtered Resource using an access token, Artifactory populated the Password field in the downloaded file with the value ${INVALID.REF}.


Fixed an issue whereby, when replicating artifacts from a Federated repository to a target instance, Artifactory incorrectly displayed a checksum warning message.


Fixed an issue whereby, when creating a repository with a repository key containing a space and then restarting Artifactory, Artifactory returned an error.


Fixed an issue whereby using the UI to delete an Access Token in an Access Federation was not synced across target JPDs.