Strange behavior of bun update --latest

[x4fingers]

I often use bun update --latest command to update packages to their latest version number.
But now when I use Bun v1.2.2 it changes all their version number to latest. I expected it to be the latest version number instead.

Did I miss any breaking changes on v1.2 or is it just an unwanted behavior?

[x4fingers]

I'm sorry, it was a mistake. I forgot that I'm looking to bun.lock file.

[RiskyMH]

It is a bug. You can run bun i after and it should put the proper versions though.

see #13388 (comment)

[x4fingers]

Wow, it was a bug. Thanks for your information.