Affects Version/s: 6.1.0, 6.2.0, 6.3.0
Fix Version/s: None
Currently, the order of priority in our virtual repo for fetching the package requested by the client is
- remote cache
The use case, for example, assume the customer is working on an opensource project where their developers from around the globe are using the same package type with different versions that they published to local repo but when the latest final version eventually makes it to the remote repo, NPM download request through Artifactory still fetches the older version from the local repo because local takes precedent.
I think Artifactory should be able to run the version check against all repos in the virtual for the latest package to allow the client to resolve the latest package version.