`bun update --latest` doesn't follow exact versions syntax of `npm update --save`

[deadcoder0904]

What version of Bun is running?

1.2.10+db2e7d7f7

What platform is your computer?

Darwin 24.4.0 arm64 arm

What steps can reproduce the bug?

1. Create new repo & do bun add -D @biomejs/biome@beta
2. Change the biome dependency to be exact now: "@biomejs/biome": "2.0.0-beta.1" without ^
3. Try bun update --latest and see it'll update the beta dependency to latest like 1.9.4 when it technically shouldn't. This is how npm update --save works.

bun update v1.2.10 (db2e7d7f)

↑ @biomejs/biome 2.0.0-beta.1 → 1.9.4

2 packages installed [5.31s]

Blocked 1 postinstall. Run `bun pm untrusted` for details.

What is the expected behavior?

Use the exact version if I specify exact version in package.json

What do you see instead?

Updated to latest

Additional information

Its annoying since biome@beta has a feature that makes my VSCode go bonkers otherwise if I used biome@latest & I have a habit of updating packages daily on personal projects so I have to perform bun add -D @biomejs/biome@beta every time I do bun update --latest

[RiskyMH]

Is your issue #16569 where you expect --latest to be latest of current tag and not the @latest version of the package? Otherwise if you omit --latest it should follow semver and ^.

[deadcoder0904]

Yeah it does look similar except I want beta instead of canary.

Here's what I want:

biome@beta is kept as is even if I do --update latest

Now I tried putting @beta in package.json or just fixed package number but both didn't work.

At least npm version worked with fixed package number.