You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@nathanwhit Thanks for answering. I guess my confusion was that I expected the --latest flag to always bump the version to the very latest version in deno.json. deno outdated --help shows: --latest Update to the latest version, regardless of semver constraints
Clsoing the issue.
Version: Deno 2.1.4
Using
deno outdated
ordeno outdated --latest
in various projects, it sometimes gives me a result, sometimes not.Here, in a clean project, I have a deno.json file:
I expect the
deno outdated
ordeno outdated --latest
command to suggest upgrading to 0.224.12.I also tried:
deno outdated --update --latest "@std/*"
The text was updated successfully, but these errors were encountered: