-
Notifications
You must be signed in to change notification settings - Fork 28k
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
Bump packages version to match canary versions #57071
Conversation
Failing test suitesCommit: efb7a7b
Expand output● create next app › empty directory
● create next app › should fall back to default template
● create next app › should allow an example named default
● create next app › should create a project in the current directory
● create next app › should ask the user for a name for the project if none supplied
Read more about building and testing Next.js in contributing.md.
Expand output● should use npm as the package manager on supplying --use-npm
● should use Yarn as the package manager on supplying --use-yarn
● should use pnpm as the package manager on supplying --use-pnpm
● should use Bun as the package manager on supplying --use-bun
● should infer npm as the package manager
● should infer yarn as the package manager
● should infer pnpm as the package manager
● should infer Bun as the package manager
Read more about building and testing Next.js in contributing.md. |
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
|
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: next@13.5.6-canary.8 |
@huozhi @feedthejim This looks like it broke another test
https://github.com/vercel/next.js/actions/runs/6578876460/job/17873547337?pr=57071#step:28:166 |
We released 13.5.6 as stable patch, need to bump the canary version higher than stable to match the semantics