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
..
deno_json	fix(outdated): error when there are no config files (#27306)	2024-12-10 23:25:29 +00:00
external_import_map	fix(outdated): support updating dependencies in external import maps (#27339)	2024-12-13 12:25:05 -08:00
mixed_workspace	fix(outdated): error when there are no config files (#27306)	2024-12-10 23:25:29 +00:00
no_config_file	fix(outdated): error when there are no config files (#27306)	2024-12-10 23:25:29 +00:00
package_json	fix(outdated): error when there are no config files (#27306)	2024-12-10 23:25:29 +00:00
pre_release	fix(outdated): ensure "Latest" version is greater than "Update" version (#27390)	2024-12-17 23:56:03 +00:00