fix: missing bun.lock
#9958
Merged
fix: missing bun.lock
#9958
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
chris-olszewski
approved these changes
Feb 13, 2025
dimitropoulos
added a commit
that referenced
this pull request
Feb 13, 2025
joshnuss
pushed a commit
to joshnuss/turborepo
that referenced
this pull request
Feb 15, 2025
### Description In vercel#9950 (comment) it was observed that `bun.lock` is missing from this list. I started by exposing and then consuming the constants right from the source (d9ea60f) and then added `bun.lock` to the list in (c5840db) ### Testing Instructions `bun.lock` should now invalidate. With vercel#9783 being released, this is expected behavior.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
In #9950 (comment) it was observed that
bun.lockis missing from this list.I started by exposing and then consuming the constants right from the source (d9ea60f) and then added
bun.lockto the list in (c5840db)Testing Instructions
bun.lockshould now invalidate. With #9783 being released, this is expected behavior.