The GPG key expires every year - as per the recommendation, so a new key has been generated and uploaded to the openpgp database.

Ran into some issues while trying to do this earlier today. Documenting my findings to prevent the same issues when having to do it again next year.
I've also asked a question about key rotation in the PHIVE repo to get clarification on some things: phar-io/phar.io 147. This may result in a new PHIVE documentation page about this being available by next year 🤞

It is also the reason why I have not explicitly released the `3.13.1` tag yet as the README does not contain information about the updated GPG key yet.

By rights the new key should probably also be mentioned in the changelog, but tags should be immutable, so I'm going to leave that for now. Hopefully this change in the release checklist will prevent this snafu for next year.

Update for new GPG keys

This commit removes an if condition to maintain backwards compatibility
that is no longer needed. It was added via squizlabs/PHP_CodeSniffer@4982619
to preserve backwards compatibility back in a time when it was possible
to programmatically set ignore patterns using
`CodeSniffer::setIgnorePatterns()` (see https://pear.php.net/bugs/bug.php?id=19859).
This method was removed a long time ago via f61025c#diff-c36ecedca179eab0b3cd245e872a96ab26fa08e567437e167f4eda1779c15c89L431-L435,
and since then, there is no way for users to set the ignore pattern
array with numeric indices.

…filter-class

Filter/Filter: remove outdated code that is no longer needed

…tVis[i]bility` error code

The `SpacingAfterVis[i]bility` error code was introduced in v 3.12.0 (March this year) for constructor property promotion.
The `SpacingAfterSetVis[i]bility` error code was introduced in v 3.13.1 (few days ago) for constructor property promotion with asym visibility.

Both contained the same typo.

Now, changing an error code is a breaking change. However, with 3.13.1 only having been released a few days ago, it is my opinion that if released soon as 3.13.2, this is an acceptable bug fix.
But then, it would be really weird to not fix the other error code in the same version. Then again, as PHPCS 4.0.0 is around the corner and does allow for breaking changes, let's leave the older typo for 4.0.0, just to be on the safe side.

... picked up along the way.

…opyright

Licence: update copyright

…clarationargumentspacing-fix-errorcode

Squiz/FunctionDeclarationArgumentSpacing: fix typo in `SpacingAfterSetVis[i]bility` error code

Various minor fixes / typos

- Improve sniff description explicitly mentioning where the spaces are
checked and adding context as to when the `self` keyword is verified.
- Fix the code examples for checking `self` case and spaces around the
double colon to ensure they trigger the sniff (the sniff checks if the
call is made within a class).
- Improve the titles of the code examples related to spacing around
double colons.
- Remove unnecessary methods from the code examples related to using
`self` instead of the class name when referencing a static member.

Changelog for the 3.13.2 release