Artifactory 7.106.2 Cloud

Released: 30 January, 2025

Feature Enhancements

Release Bundle v2 version creation using artifacts in virtual repositories
You can now create a Release Bundle v2 version using artifacts located in a virtual repository, provided the source path of the artifacts points to a local repository (not a remote repository) aggregated by the virtual repository. This feature is relevant when creating a Release Bundle version from a list of artifacts.Virtual RepositoriesSource Type - Artifacts
Move artifacts during Release Bundle v2 promotion
When promoting a Release Bundle v2 version using the REST API, you can optionally move the contents of the Release Bundle from the source to the destination instead of copying them (the behavior until now). For example, if you promote a Release Bundle v2 version from the DEV environment to the QA environment and set the operation to Move, the artifacts are removed from the repositories associated with DEV and moved to the repositories associated with QA. For more information, see Promote Release Bundle v2 Version.Promote Release Bundle v2 Version
New API for finding Release Bundle v2 promotions with a specified artifact
A new REST API endpoint is available that returns promoted Release Bundle v2 versions containing a specified artifact. For more information, see Get Release Bundle v2 Version Promotions with a Specific Artifact.
Added Support for the PyPI JSON API in Remote Repositories
Artifactory now supports PyPI’s JSON API in remote repositories.
Added Tags for RPM local repositories
Added support for the Recommends and Suggests dependency tags in the primary.xml metadata of RPM local repositories enhancing package management for clients like dnf and yum by recognizing optional dependencies.
Feature Flag Control: The inclusion of Recommends tags in primary.xml can now be configurable via a feature flag
yum.local.install.recommended.dependencies.enabled.
To learn more, refer to Install RPM Packages Using Yum.Install RPM Packages Using Yum

Resolved Issues

JIRA Issue	Component	Severity	Description
RTFACT-31017	Packages	Medium	Fixed an issue whereby missing Vagrant .box properties caused 500 internal server errors when resolving boxes.
RTFACT-30794	Release Lifecycle Management	Medium	Fixed an issue whereby when creating a Release Bundle v2 for an OCI Helm Image, SHA files for layers were missing.
RTDEV-53176	General	Medium	Fixed an issue whereby Artifactory could not retrieve an artifact from a remote repository if there were square brackets "[]" in the artifact name.
RTDEV-53064	Database	Medium	Fixed an issue whereby MariaDB JDBC driver 3.4.1 was not working with Artifactory 7.98.9 after upgrading from Artifactory 7.84.21.
RTDEV-52983	General	High	Fixed an issue whereby when upload to S3 storage failed for an aritfact, a 200 OK message was entered in the artifactory-request.log.
RTDEV-52844	Packages	Medium	Fixed an issue whereby all Docker image layers appeared as RUN layers.
RTDEV-52751	Storage	Medium	Fixed an issue whereby the cache-fs synchronization process was stopped prematurely if an entry in the cache folder was inaccessible and resulted in the actual cache size being larger than the displayed cache size.
RTDEV-50452	Packages	Medium	Fixed an issue whereby Debian virtual metadata requests were triggering extra metadata calculations even if the cache had not expired.