Artifactory 7.111.1 Cloud

Released: 09 April, 2025

New Features

Retention Policies: Smart Archiving
The Smart Archiving Retention Policies feature is designed to streamline the management of stale artifacts in Artifactory. This new functionality facilitates the seamless movement of inactive or less frequently accessed packages from an active Artifactory instance to an archive instance connected to a low-cost, cost-effective storage solution. For more information, see Archive.Archive

Feature Enhancements

New Machine Learning Layout for Hugging Face Repositories
All new Hugging Face repositories are now created with the new unified Machine Learning layout. Users can also migrate legacy Hugging Face repositories to the new Machine Learning layout on a manual basis. The Hugging Face repositories legacy layout will be deprecated in September 2025 when all repositories with the legacy layout will be automatically upgraded to the Machine Learning layout. For more information, click here.
Docker Repository Key Length Limitation on Cloud Platforms
Artifactory cloud customers using the Docker Subdomain method will now receive a warning when creating a repository if their repository key is too long for DNS record creation. This could lead to accessibility issues if DNS is not managed internally. However, exceeding the character count does not prevent creating the repository. For more information, click here.
Release Bundle v2 auto-creation enhancements
The following enhancements are now available for the Release Bundle v2 auto-creation feature introduced in Artifactory 7.107.1:Release Bundle v2 Auto-Creation
- Creating project-specific environments during build promotion
  When promoting a build, if the target repository (targetRepo) is part of a project, a project-specific environment is created for the auto-created Release Bundle v2. The environment is named after the status value of the build.Promote a BuildProjectsEnvironmentsRelease Bundle v2 Auto-Creation
- Giving build status priority over an existing target environment during build promotion
  If the status is defined for a build, the environment represented by that status is always given priority during promotion. For example, if an environment assigned to the targetRepo matches the status, the auto-created Release Bundle v2 is promoted to that environment. (That is, it is given priority over other environments that might also be assigned to the targetRepo.) If no environment exists for the status, a new environment is created for the promoted Release Bundle v2 with the name of the status, even when other environments are available.EnvironmentsPromote a BuildRelease Bundle v2 Auto-Creation
Increased limits for Release Bundle v2 names and versions
The maximum length of the name (release_bundle_name), version (release_bundle_version), and creator (created_by) of a Release Bundle v2 has been increased to 255 characters when working with the REST API.Create Release Bundle v2 Version
Get Release Bundle v2 Versions API returns tag information
The Get Release Bundle v2 Versions REST API now returns the descriptive tag assigned to a Release Bundle version. For more information about tagging, see Assign Tag to Release Bundle v2 Version.Get Release Bundle v2 VersionsAssign Tag to Release Bundle v2 Version
Support for SemVer sorting in Release Bundle v2 APIs
SemVer sorting support has been added to the Get Release Bundle v2 Versions and Get Release Bundle v2 Versions in a Specific Environment APIs. This support is limited to the 1000 latest records and does not support pagination. This option pulls the latest 1000 records only and does not support pagination. Versions that do not conform to SemVer rules are sorted afterward lexicographically.Get Release Bundle v2 Versions
New Worker Event: Before Token Expiry
JFrog now supports creating event-driven workers to trigger before a token expires. Learn moreBefore Token Expiry Worker Code Sample
Properties Tab for RPM Remote Packages
Added functionality to calculate and display the properties of an RPM package after it is downloaded from a remote RPM repository. The package properties are now shown in the Properties tab on the UI. For more information, see View and Search for Properties in the UI
Policy Conditions - Cleanup Packages
- Adding Property-based Policy Condition
  Enhanced package-cleanup functionality with the addition of a property-based policy condition. You can now include or exclude specific package versions from cleanup by applying a property-based policy condition. This allows for more granular control over which packages are retained or removed during cleanup actions. For more information, see Create Cleanup Policy - Package.Create Cleanup Policy - Package
- Adding days/weeks selection for Time-based Policy Condition
  Enhanced package-cleanup functionality with the addition of days/weeks selection for Time-based policy condition. You can now configure by specifying Time-based cleanup conditions based on days/weeks for the packages. For more information, see Create Cleanup Policy - Package.Create Cleanup Policy - Package
Improved Performance of the Repository Selection Field in Set-Me-Up
The performance of the repository selection field in Set-Me-Up has been improved by promoting a search-first approach.
Improved Access for Go Remote Repositories
Go remote repositories now support the ability to access subgroups in GitLab. For more information, click here.Proxy GitLab with Go
Added Support for Chocolatey and PowerShell Clients in Nuget Repositories
- Added support for PowerShell (minimum version 1.0.5) to interact with NuGet repositories.
- Added support for Chocolatey (minimum version 1.2.0) to interact with Nuget repositories.
For more information, see NuGet Repositories.NuGet Repositories
Added Support for Listing Folder Items in Conan Smart Remote Repositories
- A new setting, List Folder Items, is now available for Conan Smart Remote Repositories.
- Enabling the List Remote Artifacts checkbox during repository creation allows folder items to be listed.
Hex Repositories
Artifactory now supports Hex Virtual Repository. A Hex virtual repository aggregates Hex local and remote repositories, enabling more efficient package management. To learn more, see Hex Repositories.Hex Repositories
Easier Configuration of the NimModel Redirect Download Form
The NimModel redirect download form can now be configured through the User Interface.

Resolved Issues

JIRA Issue	Component	Severity	Description
RTFACT-31075	Repositories	Low	Fixed the following two issues related to using Delete Content on a repository: When a user with delete permissions on a repository attempted to use Delete Content on the repository, the user was denied permission to delete. When a project admin attempted to use Delete Content on a repository shared into a project, the project admin was denied permission to delete.
RTFACT-31012	Packages	Medium	Fixed an issue whereby when switching from Recently Viewed packages to a packages custom view, the custom view was not applied and instead all packages were listed.
RTFE-1637	Packages	Medium	The Graph view was removed from the Packages tab.
RTDEV-55696	Packages	High	Fixed an issue whereby triggering indexing in a nested virtual Debian repository also triggered indexing in all parent virtual repositories.
RTDEV-55754	Packages	High	Fixed an issue whereby when trying to override an image with the exact same image, by a user without delete permission, a 403 error was encountered.
RTDEV-55692	Release LIfecycle Management	Medium	Fixed an issue whereby the Xray scan of a Release Bundle v2 version would fail if any item in the Release Bundle contained a property whose value included a surrogate pair (a way to represent special characters in UTF-16, such as an emoji). Artifactory now normalizes the surrogate pair into a string that Xray can process.
RTDEV-55463	Archiving/Cold Storage	Medium	Fixed an issue whereby Artifacts that were never downloaded from Artifactory were not deleted by Time-Based Cleanup Policies.
RTDEV-55450	Packages	Medium	Fixed an issue whereby the Promote Docker Image API renamed sub-manifest tags according to their architectures.
RTDEV-55270	Packages	Medium	Fixed an issue where maven set-me-up generated settings.xml did not support OIDC integration for use with Github actions.
RTDEV-55266	General	Medium	Fixed an issue whereby when trying to retrieve a package from a remote Maven repository, a 404 Forbidden error was encountered.
RTDEV-55208	General	Low	Fixed an issue whereby the Artifact count temporarily displayed '0' while the HQC was being refreshed.
RTDEV-54891	Packages	Medium	Fixed an issue whereby ‘symbols.nupkg’ was getting indexed post calling reindex endpoint and then restarting the Artifactory instance.
RTDEV-54831	Storage	Low	Fixed an issue whereby when attempting to perform multipart upload with the wrong repository key, the upload would get stuck when getting the upload URLs and would not complete.
RTDEV-54283	Builds	High	Fixed an issue that caused Build Uploaded and Build Deleted webhook notifications to be sent when these operations began instead of waiting for the operations to complete. This meant that if the operations failed and were rolled back, the rollback occurred after the notification indicating completion was already sent.
RTDEV-53825	Storage	Medium	Fixed an issue whereby when using Artifactory with S3 storage, enabling redirect download in the binarystore.xml file and setting signedUrlExpirySeconds to 0 or a negative value sometimes resulted in download failure.
JA-16710	Projects	Medium	Fixed an issue whereby when calling the Update Existing Project Properties REST API, the project storage quota was set to 0 and the project description was removed.