Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
This PR adds the updater for
bun.lock
files. A later PR will add support for legacybun.lockb
files.We are currently limiting fetching the bun files with the experiment
bun_updates
as an experimental feature.bun
#6528Anything you want to highlight for special attention from reviewers?
bun.lock
files is currently guarded byExperiments.enabled?(:bun_updates)
For wider context you can check #11209 or #11248
The ultimate plan is to use a new structure for multiple Javascript ecosystems similar to #1862.
This PR was put together before the change in approach. It was decided that we proceed with these PR's as-is.
We will then follow-up with a PR migrating to the new structure. This migration PR will then serve as an example for the migration of the other Javascript ecosystems.
How will you know you've accomplished your goal?
The new specs should pass and the existing specs should be unimpacted.
c/o @Electroid, here is a random sample of repositories using bun.lock that you can try with the dry-run scripts:
Checklist