deno

b365d544 - fix(outdated): use dist-tags.latest for Latest column, matching npm/pnpm/bun (#32939)

fix(outdated): use dist-tags.latest for Latest column, matching npm/pnpm/bun (#32939) ## Summary - Use `dist-tags.latest` directly for the "Latest" column in `deno outdated`, matching npm/pnpm/bun behavior - Prevent `--update --latest` from downgrading packages when the latest dist-tag is lower than the current pre-release version ### Problem When the `latest` dist-tag doesn't satisfy the version requirement (e.g., `latest=0.45.1` but `req=^1.0.0-beta.13`), Deno fell back to computing a max across all published versions. This incorrectly picked versions with commit-hash pre-release identifiers because per the semver spec, alphanumeric identifiers sort higher than numeric ones: ``` 1.0.0-beta.9-commit.d91dfb5 > 1.0.0-beta.13 ↑ "9-commit" is alphanumeric ↑ "13" is numeric (sorts lower) ``` All other package managers (npm, pnpm, bun) avoid this by using `dist-tags.latest` directly for the "Latest" column — they never compute a max across all versions. Closes #29647 --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>