Nathan Whitaker 9d7174e434 fix(outdated): ensure "Latest" version is greater than "Update" version (#27390) ... Fixes #27038. Previously, for NPM packages the latest version was the version with the "latest" tag. For JSR packages, the latest version was the greatest version that matched a `*` version requirement. Unfortunately, that doesn't work well with pre-release versions. This PR changes it so that the latest version is always > the currently requested version. For NPM: if "latest" tag > current then "latest" tag; otherwise the greatest version that is >= current For JSR: greatest version >= current This is the most reasonable behavior I could come up with. For example, ``` versions: 2.0.0-beta.2 2.0.0-beta.1 1.0.0 => "latest" tag with a version req `^2.0.0-beta.1` previously: "Update" column => 2.0.0-beta.2 "Latest" column => 1.0.0 now: "Update" column => 2.0.0-beta.2 "Latest" column => 2.0.0-beta.2 ```		2024-12-17 23:56:03 +00:00
..
jsr	fix(outdated): ensure "Latest" version is greater than "Update" version (#27390)	2024-12-17 23:56:03 +00:00
npm	fix(outdated): ensure "Latest" version is greater than "Update" version (#27390)	2024-12-17 23:56:03 +00:00
npm-private/@denotest	fix(npm): use configured auth for tarball urls instead of scope auth (#24111)	2024-06-05 21:24:52 +00:00
npm-private2	fix(npm): use configured auth for tarball urls instead of scope auth (#24111)	2024-06-05 21:24:52 +00:00
npm-private3/@denotest3/basic/1.0.0	fix: .npmrc settings not being passed to install/add command (#26473)	2024-10-24 20:03:56 +02:00