-
Notifications
You must be signed in to change notification settings - Fork 2k
chore(turborepo-wax): remove lockfile #9817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@ognevny is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not believe this lockfile actually gets used since turborepo-wax
is a member of the Cargo workspace and should use the same crate versions as the root Cargo.lock
.
Could you delete this lockfile instead of updating it?
6b40477
to
56e31be
Compare
done |
Description
the same reason as for #9805, but for turborepo-wax. the package update fully removes winapi from lockfile. also cargo updated many packages for unknown reason (I've runcargo update -p winapi-util
)as asked in review lockfile is deleted
Testing Instructions