ci: publish v3 with npm trusted publishing - #2270

Thank you for fixing that! I had some trouble with it before as well back with Yarn Berry, I thought it was simply because our Yarn version was too old, so I was hoping migrating to pnpm would've solved it. :/

On the side, I've noticed you've backported to v3, but not to v2. I know it was a bit overkill of me anyway to have backported anything to v2 anyway. 😅

Do you have thoughts on that?

Shall we consider SVGO v2 completely dead and deprecated, or shall we continue to backport the security fixes?

If you think we shouldn't give it security fixes either, I vote we deprecate v2 in npm too, similarly to what we (well, someone in the org!) already did for SVGO v1.

If we do deprecate it, the message could include a link to the SVGO v2 to v3 Migration Guide.

Already running an agent to backport to v2 as well though yeah we may deprecate it later. Maybe once v5 is ready.