Update tscircuit dependencies and disable Bun lockfile#246
Open
hz19880404-tech wants to merge 2 commits into
Open
Update tscircuit dependencies and disable Bun lockfile#246hz19880404-tech wants to merge 2 commits into
hz19880404-tech wants to merge 2 commits into
Conversation
|
@hz19880404-tech is attempting to deploy a commit to the tscircuit Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or 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
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.
Summary
/claim #79
bun.lockas requested.bunfig.tomlconfiguration with[install.lockfile] save = false, so Bun does not save a new lockfile during install.Notes
The change is intentionally scoped to dependency refresh plus lockfile handling for the Vercel deployment issue described in #79.
Verification
package.jsonand removesbun.lock.tscircuit:mainand 0 commits behind before opening this PR.I do not have Vercel project access from this environment, so I cannot directly confirm the production Vercel deployment, but the repository-side changes requested in the issue are included.