3.0.1

[iobrado]

Description

Changed

• Updated dependencies. PHPUnit had a security vulnerability that needed to be addressed. More recent versions of PHPUnit (v10+) introduced breaking changes that would require a major version bump. Priority of this release was to fix the security vulnerability.
• Added exclude to deprecated ruleset since WordPressCS v3.3.0. Covered by PHPCompatibilityWP.
• Renamed tests.

[goranalkovic-infinum]

L(e)G(i)T(i)M(no)

[piqusy]

Nice work 👏🏼

Left a question, and I have a concern with this PR about coding standards not passing linter tests (coding standards 🙈 😄 )

[piqusy]

How come this is broken in to multiple lines?

[iobrado]

For style ✨ joking aside, no idea why was it broken like that, but I'll fix it.

[dingo-d]

It's Claude (or any other AI tool), they have the tendency to limit line length when writing comments...

[dingo-d]

This will literally break EightshiftCS 🙈

WPCS still hasn't worked on the issue this branch fixed, there were talk about taking this up, but I reckon this will happen somewhere in the middle or at the end of the year hopefully...

[iobrado]

Well, that complicates stuff. We have a high vulnerability in repo, so while at it, I (cough Claude) tried to update some other dependencies as well. Then I guess the only option here is to just update PHPUnit to minimum version that fixes the vulnerability and leave the rest for later.

[dingo-d]

If you are worried about this: GHSA-vvj3-c3rp-c85p it's only happening when code coverage for PHPT files is being parsed. This repo isn't using phpt files (it's used for testing PHP internally usually), so I'm not sure this repo is at risk 🤷🏼‍♂️

[iobrado]

That's the one, yeah. Good to know, but I'd still prefer to fix it, so that Dependabot doesn't scream at us 😂

I already opened a PR that only updates PHPUnit to mentioned version, hopefully that one doesn't break CS.