chore: bump serializer library, for https://github.com/pinojs/pino-std…

[Mechanicalkeyboard]

see pinojs/pino-std-serializers#88

[jsumners]

This would incur a major bump for Pino. We will do that at some point, but I'm not sure we are ready for it yet. You can use the newer version of pino-std-serializers by providing them as serializers when creating your Pino instance -- https://getpino.io/#/docs/api?id=serializers-object

[voxpelli]

I would have hoped this would get part of Fastify v4 as a bump in Pino major would have to wait for a Fastify major to be included there and that will I guess take a while before that happens

[mcollina]

CI is failing, could you update it?

@voxpelli I cannot delay Fastify v4 further to do another pino major bump :(. We'll likely do a Fastify v5 / pino v8 combo once we are ready.

[voxpelli]

@mcollina I totally understand, I should have caught this earlier if I wanted to push it :)

On a sidenote: Why didn't Dependabot suggest this update?

[kibertoad]

@mcollina How much work would bump entail? I can contribute some effort if that helps

[mcollina]

@mcollina How much work would bump entail? I can contribute some effort if that helps

Check out https://github.com/pinojs/pino/milestone/4. The most important change that need to be finished is #1249

[kibertoad]

@mcollina #1249 only needs conflicts resolved and CI passing, right? Will attempt that tonight.

[kibertoad]

@voxpelli Meanwhile, will you be able to fix this PR?

[voxpelli]

@kibertoad I can try, but since it’s not mine and I’m not a maintainer I can only open a new one that replaces this one

[kibertoad]

@voxpelli that also works

[kibertoad]

@voxpelli fastify v4 lands next Tuesday, so we need pino 8 this week. is it feasible to create a new PR by EOD tomorrow?

[mcollina]

Superseded by #1449

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.