-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Sync Cargo.lock with Next.js #8246
Conversation
Updates socket2, tokio, and tokio-macros
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Ignored Deployments
|
🟢 Turbopack Benchmark CI successful 🟢Thanks |
|
For whatever reason This is something I want to get to the bottom of, but don't have the time to dedicate right now to figuring it out. Is the latest |
Looks like the reason it was update was to match turbo's, which isn't the case: vercel/next.js@99fff19 @bgw was this a mistake? |
Turbo was on 1.37.0 until yesterday: 7875ab2f67 |
This reverts commit 99fff19. See vercel/turborepo#8246 for context.
Closing in favor of vercel/next.js#66391 |
This reverts commit 99fff19. See vercel/turborepo#8246 for context.
Updates socket2, tokio, and tokio-macros