feat: upgrade @typescript-eslint/utils to v6

[SimenB]

There are so many breaking changes in v6 I don't think we'll be able to properly support v5 and v6 at the same time...

I started here and just ended up frustrated 😛 @G-Rath I dunno if you wanna give it a whack?

[G-Rath]

@SimenB just to check, do we need to support both or move to v6 right now? I'm still triaging the new major and so far it looks like everything still works fine from a consumer POV but want to double check I've not missed something.

[SimenB]

I'd prefer to have CI verify it works with both, but there is no rush at all. It's totally fine to stay on the old version for now

[quantizor]

ooc if this linter plugin isn't updated to the new version and @typescript-eslint/*@6 is used in a linting setup, will that cause problems with both versions being installed and potentially used simultaneously?

I ask because the newer version has some desirable stuff in it like code to leverage the TS projects service... would be very helpful for larger repos.

[SimenB]

You can use v6 of the plugin already

[quantizor]

You can use v6 of the plugin already

Oh, what is this PR doing then?

[github-actions]

🎉 This issue has been resolved in version 28.0.0-next.3 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 28.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀