Released: 27 February, 2024
Cargo Git Indexing Deprecation
Starting at the end of Q2, 2024, Cargo indexing will only be enabled using Sparse indexing, and the use of Git indexing will be discontinued. For more information, see Deprecations in Process.
New Features
Oracle RAC support for Federated repositories
Customers who use Oracle Real Application Clusters (RAC) must configure the following Artifactory system property to support Federated repositories:
artifactory.oracle.node.events.sequence.is.no.cacheSetting this property to
trueenables a converter that fixes the Oracle node events sequence definition for RAC instances.Note
For additional prerequisites, see Setup Prerequisites for Federated Repositories.
Feature Enhancements
Display List Manifest Content on the Artifacts Page
Artifactory now displays the manifests under a
list.manifestfile directly in the Artifacts page in the JFrog Platform WebUI. For more information, see List Manifest Content.Storage Improvements
This release contains the following storage improvements:
When using Azure Blob storage with a SAS token, the SAS token is now encrypted at rest in the the binarystore.xml file.
When using the state-aware-s3 binary provider, sensitive properties are now encrypted in the same manner as they are for the s3-storage-v3 binary provider.
Full Sync improvements for Federated repositories
This release contains an option for generating the file list for a Full Sync operation using multiple SQL queries (paging) instead of a single AQL query. Dividing the database query into pages helps prevent the operation from crashing when retrieving a large file list (by default, more than 400000 artifacts). In addition, several new system properties have been introduced for managing this paging feature. For more information, see System Properties for Full Sync File List Queries. For more information about Full Sync, see Perform Full Sync on Federated Repositories.
Resolved Issues
JIRA Issue | Severity | Description |
|---|---|---|
High | Fixed an issue related to RPM whereby, when trying to resolve artifacts from an upstream repository through a virtual repository, Artifactory did not work as expected at first attempt. | |
Medium | Fixed an issue whereby, when trying to remove an SSH key from Artifactory, the key was not completely removed. | |
Medium | Fixed an issue related to Conda whereby, when trying to deploy an artifact with an empty | |
RTDEV-39105 | Medium | Fixed an issue related to Maven whereby, Artifactory did not force authentication for unavailable artifacts in virtual repositories in the native JFrog Platform WebUI even when the Force Authentication checkbox was selected. |
RTDEV-39036 | Medium | Fixed an issue related to npm whereby, Artifactory did not support installing external dependencies with URLs containing question marks (?). |
RTDEV-38815 | Medium | Fixed an issue related to Go and PyPI whereby, when resolving artifacts from remote repository using a plugin that uses the |
RTDEV-38116 | Medium | Fixed an issue that prevented sites using Oracle RAC from supporting Federated repositories. For more information, see Oracle RAC support for Federated repositories. |
RTDEV-38815 | Medium | Fixed an issue related to Go and PyPI whereby, when resolving artifacts from remote repository using a plugin that uses the org.artifactory.exception.CancelException class, Artifactory returns an incorrect error. |
RTDEV-38849 | Medium | Fixed an issue that caused an unexpected server error when deleting a Release Bundle v2. |