deno/tests/registry/npm/@denotest/has-pre-release/1.0.0/package.json

{
  "name": "@denotest/has-pre-release",
  "version": "1.0.0",
  "publishConfig": {
    "tag": "latest"
  }
}
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 15:56:03 -08:00			`{`
			`"name": "@denotest/has-pre-release",`
			`"version": "1.0.0",`
			`"publishConfig": {`
			`"tag": "latest"`
			`}`
			`}`