-
Notifications
You must be signed in to change notification settings - Fork 3k
chore: bump pino and pino pretty #14262
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
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
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.
Removing support for Node 18 would be a breaking change. Use the v9 fix.
Closing in favour of #14283 in order to not risk the node 18 version issue being a breaking change downstream |
Continuing from #14262 Bumping `pino` to `9.14.0` and `pino-pretty` to `10.1.2`, both minor version bumps
Bumping
pino
from v9 to v10 only has one breaking change dropping support for node 18pino-pretty
was also bumped but minor version that includes a lot of fixes and bumping of dependencies