Released: 16 December, 2024
New Features
New REST API for Checking Repository Existence
A new REST API has been added to check whether a repository exists based on the project key and repository type. For more information, click here.
Feature Enhancements
Converting Federated repositories back to local
You can now convert a Federated repository back to a local repository using a REST API, provided it is not part of a Federation containing additional members. For more information, see Convert Federated Repository to a Local Repository.
Supported Worker Events
Storage: After Copy event is now supported.
Storage: After Property Delete event is now supported.
Replication: Before Directory Replication event is now supported.
Storage: After Property Create event is now supported.
Added Clients for PyPI Repositories
PyPI repositories now support Poetry and Twine clients. For more information, click here.
Support for Terraform BE Packages in Cleanup and Archive
Terraform BE packages are now supported in Cleanup and Archive.
Resolved Issues
JIRA Issue | Component | Severity | Description |
---|---|---|---|
Repositories | Medium | Fixed an issue whereby there was no option in the UI to disable the “List Remote Artifacts” option for Maven remote repositories. | |
Release Lifecycle Management | Medium | Fixed an issue whereby, the REST API Promote Release Bundle v2 Version was missing the included repositories validation. | |
RTDEV-51199 | General | Medium | Fixed an issue whereby when viewing a virtual repository in a tree browser, the message This item is not cached. appeared for an artifact in that repository even though it was cached. |
RTDEV-50995 | General | Medium | Fixed an issue whereby Artifactory was sending an empty project key instead of the default project key. |
RTDEV-49625 | General | Medium | Fixed an issue whereby internal users with “Disable Internal Password” enabled were getting password expiration emails. |
RTDEV-50824 | Release Lifecycle Management | High | Background: Since a Release Bundle v2 cannot resolve dependencies located in a remote cache repository, users must first copy the dependency artifacts to a local repository. Fixed an issue during Release Bundle creation that prevented Artifactory from giving preference to the local repository that contains the dependencies instead of the remote cache repository. |
Known Issue with Pull Replications
There is a known issue whereby properties generated locally by Artifactory are deleted during pull replications when the properties are unchanged from the previous replication execution. The current workaround is to add a custom property to the package. This is sufficient to prevent the locally-generated properties from being deleted.