Currently, 'latest version' metric is only available via the experimental/package/ endpoint when using the new-style namespace and packageName inputs.
Automating against this endpoint is ill-advised as it is experimental - subject to change, deprecation, removal.
For the sake of such automated tasks it would be great if the 'latest version' metric could be made available via a stable v1 endpoint, e.g. it would be appropriate to include this metric in the v1/package-metrics/ response payload.
Currently, 'latest version' metric is only available via the
experimental/package/
endpoint when using the new-stylenamespace
andpackageName
inputs.Automating against this endpoint is ill-advised as it is
experimental
- subject to change, deprecation, removal.For the sake of such automated tasks it would be great if the 'latest version' metric could be made available via a stable
v1
endpoint, e.g. it would be appropriate to include this metric in thev1/package-metrics/
response payload.