Artifactory 7.39.4 Cloud | Self-Hosted

JFrog Release Information


Released: 14 June, 2022


Swift Registry Support

Artifactory now natively supports a dedicated Swift registry, giving you full control of your deployment and resolution process of your Swift packages and their dependencies. Today Swift is most widely used as the go-to language for iOS and all the other Apple OS-app development. With the introduction of Swift support by Artifactory, you can create secure and private local Swift repositories, remote Swift repositories to proxy remote Swift dependencies and cache downloaded Swift packages. Virtual Swift repositories give you a single URL through which to manage the resolution and deployment of all your Swift packages. To learn more, see Swift Registry.Swift Registry

Feature Enhancements

Storage Summary Improvements

The default threshold for updating the Storage Summary page update has been modified from 1 hour to 6 hours. This change is done in order to minimize the load. This value continues to be configurable as before by setting '' value.

Detected Known Issues

This release contains an issue that was initially fixed in 7.38.10 whereby reference tokens expired earlier than expected. For Cloud customers, this issue can be resolved by upgrading to a newer release (7.39.6 and above). Self-hosted customers will need to upgrade to release 7.41.4 and above.

Resolved Issue

JIRA Issue



Fixed an issue whereby, an incorrect message and response status from the Conan Server in case of missing permissions.


Fixed an issue whereby, publishing an artifact to a Cargo registry with the explicit name_in_toml field failed.


Fixed an issue whereby, running an AQL query with an Asterix failed to return results.


Fixed an issue whereby, an SSL/TLS certificate could not be created for an existing remote repository.


Fixed an issue whereby, resolving packages from a remote NuGet repository pointing to the remote registry failed.


Fixed an issue whereby, instances with a context prefix other than artifactory, incorrectly returned a 401 in the OAuth2 requests that pointed to /artifactory/api/oauth2/loginRequest.


Fixed an issue, whereby the Helm virtual repository resolution order was not applied when multiple local/virtual repositories had the same artifact.


Fixed an issue, whereby resolving a NuGet package located in a local repository opposite a virtual repository, routes the request to the remote repository, and provides a 404 response error.


Fixed an issue whereby, PHP Composer packages failed to download files with the Dev version from virtual repositories.


Fixed an issue whereby, more than one HELP text line appeared for a number of HTTP connection metrics.


Fixed an issue whereby, folders downloaded as tar.gz or tar files, containing files larger than 8 GB, failed to download.

Fixed an issue whereby, Alpine version 3.16 may have caused a 'package file format error' when resolving from an Artifactory Alpine repository.

Fixed an issue whereby, accessing for a dist-tag on a virtual repository displayed results for a remote repository instead of the local repository.

Fixed an issue whereby, an internal Cargo token was exposed in the Token Admin page, and thus could be accidentally be revoked.

Fixed an issue whereby, empty folders of a Release Bundle were not deleted as part of its deletion from both target Repositories and Release Bundles Repository. A new parameter has been added to the Artifactory system.yaml file called releasebundle.cleanup.deleteEmptyFolder, which is set to true by default.

Fixed an issue whereby, after registering a new instance (Register JPD) and binding it using Cold Storage binding, it would take several minutes for the new instance to be identified in the JFrog Platform as a Cold instance target and not as a source.

Fixed an issue in the JFrog Platform UI, whereby the Show option in the Trash was not functional.