Ensure that NuGet releases that don't have "deprecation" field but have "published=1900" are not saved with "published_at: 1900"

librariesio / libraries.io

:books: The Open Source Discovery Service

https://libraries.io

GNU Affero General Public License v3.0

1.1k stars 206 forks source link

Ensure that NuGet releases that don't have "deprecation" field but have "published=1900" are not saved with "published_at: 1900" #3406

Closed tiegz closed 2 weeks ago

tiegz commented 2 weeks ago

It turns out that a release on NuGet can be "unlisted" but not "deprecated" on their side, e.g. "RestSharp@105.2.0", and it's not clear why.

But we consider both "unlisted" and "deprecated" on the NuGet side as "status: 'Deprecated'" on our side. This fix ensures we don't save the 1900 "published" date on these cases.