What is the Bug
Seems that the backend is incorrectly returning a tarball version 4.0.2 of linter-stylelint-pulsar even though Pulsar has requested the latest 4.6.0.
In this particular circumstance this has the unfortunate side effect of giving users a version of the package that still says it's linter-stylelint which interestingly PPM then believes and will update to the latest for that particular package.
Further investigation will need to be done to see the actual structures the backend is working with, but this error likely occurs during the GitHub data collection step, with an incorrect ordering of the versions.
What is the Bug Seems that the backend is incorrectly returning a tarball version
4.0.2oflinter-stylelint-pulsareven though Pulsar has requested the latest4.6.0.In this particular circumstance this has the unfortunate side effect of giving users a version of the package that still says it's
linter-stylelintwhich interestingly PPM then believes and will update to the latest for that particular package.Further investigation will need to be done to see the actual structures the backend is working with, but this error likely occurs during the GitHub data collection step, with an incorrect ordering of the versions.