Released: 18 January, 2024
Feature Enhancements
Federated repository support for projects
In versions before 7.78.1, new Federation members ignored the association of a Federated repository with a specific project. For example, if a Federated repository in existing members was associated with myProject, new Federation members would lack the project association.
Starting with version 7.78.1, Artifactory will check whether the associated project in existing members is defined in the site of the new Federation member. If the project exists, the new member will be associated with this project automatically. If the project does not exist, the new member will not be associated with the project.
Note
A current limitation of this feature is that if the project association later changes in one Federation member, this change is not synchronized with the other members.
Resolved Issues
JIRA Issue | Severity | Description |
|---|---|---|
Medium | Fixed an issue related to CocoaPods whereby, when configuring a remote repository using Cocoapods CDN, Artifactory did not support the 'pod repo update' command. | |
Medium | Fixed an issue that enabled users to Federate two repositories on the same Artifactory instance and to create a Federation with an Edge node as a target instance. | |
Medium | Fixed an issue related to NuGet whereby, Artifactory did not support searching for specific packages in a virtual repository using the PowerShell client. | |
Medium | Fixed an issue related to npm whereby, when copying a package to a different repository, after removing the package with the | |
RTDEV-37193 | High | Fixed an issue that caused fetch failures from deleted Federated repositories to persist indefinitely in the database. |
RTDEV-36586 | Medium | Fixed an issue whereby, virtual repositories containing remote repositories with no metadata were not visible to non-admin users. |