Released: 12 October, 2023
Breaking Change for Conan Repositories
From Artifactory version 7.71.x and forward, when using the CLI to perform actions on a Conan package that does not exist in the upstream repository, Artifactory will return a 404 error instead of returning a 200 message and creating an empty folder.
New Features
Federation Recovery and Auto-Healing
Artifactory now features an auto-healing mechanism that can recover automatically from error exhaustion and reduce the need to perform full sync operations on Federated repositories.
Auto-healing checks Federated repositories at regular intervals for exhausted queues (queues that have exceeded the maximum number of attempts to send events to other Federation members). This mechanism resets the failed events automatically and tries again to sync with the target mirror. For more information, see Federation Recovery and Auto-Healing.
There is also a new Federation Recovery API that enables administrators to perform recovery manually as an alternative to performing a full sync.
Hide SSO Providers
You can now hide the SSO providers that you configured in the JPD from the login screen. If you hide the providers, the users need to type in the SSO providers to log in to the JFrog Platform UI. For more information, see Hide SSO Providers.
Feature Enhancements
Improved Trash Can functionality
Trash Can functionality has been improved such that if you select an artifact to be deleted to the Trash Can, and there is already an artifact in the Trash Can with the same path as the artifact that you selected for deletion, a pop-up appears and informs the user that if they continue with the deletion, the artifact currently in the Trash Can will be permanently deleted. The user can click Cancel in the pop-up if they decide that the artifact currently in the Trash Can should not be permanently deleted.
Package Archiving Improvement
Prior to this release, when archiving a package to cold storage, if a package already existed in cold storage with the same name, type, version, and repository path, the older package would be overridden by the newer package. In this release, cold storage archiving of packages has been modified such that if a package already exists in cold storage with the same name, type, version, and repository path, the older package in cold storage remains there and the newer package is not archived in cold storage. When this happens, an info-level log message is written to the log to inform the user that the newer package was not archived.
Resolved Issues
JIRA Issue | Description |
|---|---|
Fixed an issue whereby, when using the CLI to perform actions on a Conan package that does not exist in the upstream repository, Artifactory returned a 200 message and created an empty folder. | |
Fixed an issue related to npm whereby, when installing packages through Artifactory, the client downloaded all flavors of the package, instead of downloading only the specific flavor (OS and CPU architecture) of the requested package. | |
Fixed an issue related to Chef whereby, when trying to resolve a package from a Smart Remote repository using the JFrog Platform WebUI, Artifactory returned an error. | |
Fixed an issue whereby, when trying to resolve an RPM package from a remote repository, Artifactory returned a 'Metadata file does not match checksum' error. | |
Fixed an issue whereby, when upgrading from Artifactory version 7.59.9 to 7.63.5, the filter section was missing from the repository list of replications in the JFrog Platform WebUI. | |
RTDEV-34149 | Fixed an issue whereby, when pushing a multi-architecture layer that already exists in the system, Artifactory created a redundant appearance of the layer with its architecture name |
RTDEV-35001 | Fixed an issue related to Maven whereby, under some circumstances, when deploying artifacts using a Maven client in version 3.9.x, the maven-metdata.xml file was not updated as expected. |
RTDEV-35969 | Fixed an issue whereby, when pulling a common blob that appears over 500 times in the nodes table under local and remote repositories, Artifactory might return a blob not found error |
RTDEV-35586 | Fixed an issue whereby, when attempting to import the artifactory.config.import.yml file, Artifactory returned an error. |
RTDEV-36014 | Fixed an issue whereby the Federation event mechanism would not resume after disabling and re-enabling the Federated member. |