search

ecosyste-ms / packages

An open API service providing package, version and dependency metadata of many open source software ecosystems and registries.
https://packages.ecosyste.ms
GNU Affero General Public License v3.0
25 stars 4 forks source link

Should the "latest release" be the latest stable version? #648

Closed jamietanna closed 7 months ago

jamietanna commented 7 months ago

(I thought I'd seen a discussion about this elsewhere but can't seem to find the issue)

For instance, looking up the npm package resolve shows that the latest version is 2.0.0-next.5.

Opening up https://www.npmjs.com/package/resolve prioritises 1.22.8 in the UI as the latest, and https://www.npmjs.com/package/resolve?activeTab=versions notes that the 2.0.0-next.5 is also available.

It would be ideal if we could rely on the "latest release" as the latest stable version, but I realise that this is ecosystem specific, so maybe it's up to the caller to determine this logic for themselves?

Upvote & Fund

Fund with Polar

andrew commented 7 months ago

Related: https://github.com/ecosyste-ms/packages/issues/190

andrew commented 7 months ago

Implemented a fix here: https://github.com/ecosyste-ms/packages/commit/bbb7286148bbf89806d54816746d25fd182072e5 need to regenerate all the latest version numbers, may take a little while