Support the new text-based lockfile of bun.

[CodesDoWork]

Tell us more.

With v1.2, the package manager Bun changed its default lockfile from binary bun.lockb to text-based format bun.lock. With this update, renovate is no longer able to update the lockfile and merge requests fail in CI pipelines. It would be nice to have an update here!

More information about bun's lockfile:

• https://bun.sh/blog/bun-lock-text-lockfile
• https://bun.sh/docs/install/lockfile

[github-actions[bot]]

Hi there,

Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[seveibar]

Hey guys just want to chime in, the renovate update of the text based lock files bun.lock in our project caused a lot of confusion today- although it looks like it updated the lock file, it actually forgets to edit one line

Relevant PR: tscircuit/eval#123

[rarkins]

Renovate doesn't update lock files directly - it uses bun to do that. If there's an incorrect lock file then it's created by a bun command.