Deno outdated seems to be flaky

[tomas-zijdemans-vipps]

Version: Deno 2.1.4

Using deno outdated or deno outdated --latest in various projects, it sometimes gives me a result, sometimes not.

Here, in a clean project, I have a deno.json file:

{
  "imports": {
    "@std/log": "jsr:@std/log@^0.224.11"
  }
}

I expect the deno outdated or deno outdated --latest command to suggest upgrading to 0.224.12.

I also tried:

• Removing the version specifier
• Running with and without lock file
• Running deno outdated --update --latest "@std/*"

[nathanwhit]

I believe the reason for the apparent "flakiness" is that the specifier above already will resolve to the latest version (unless a lockfile has an older version).

The latest version of @std/log is 0.224.12 (at time of writing). The specifier jsr:@std/log@^0.224.11 is semver compatible with 0.224.12, so unless the lockfile points to an older version, we resolve the version to 0.224.12 and there's nothing to update.