Update dependency phpstan/phpstan to v1.10.13

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
phpstan/phpstan	require-dev	patch	1.10.11 -> 1.10.13

---

Release Notes

phpstan/phpstan

v1.10.13

Compare Source

• Fix internal error: FilterVarArrayDynamicReturnTypeExtension for mixed input (#​2338), #​9178, thanks @​zonuexe!

v1.10.12

Compare Source

Major new features 🚀

• Object shapes, #​2923
  • Documentation
  • Twitter thread about implementing it
  • phpdoc-parser implementation

Bleeding edge 🔪

• Stricter function signature map (phpstan/phpstan-src@06b746d, #​2163), #​7239, thanks @​staabm!
• Specify Imagick parameter types (#​2334), thanks @​zonuexe!

If you want to see the shape of things to come and adopt bleeding edge features early, you can include this config file in your project's phpstan.neon:

includes:
	- vendor/phpstan/phpstan/conf/bleedingEdge.neon

Of course, there are no backwards compatibility guarantees when you include this file. The behaviour and reported errors can change in minor versions with this file included. Learn more

Improvements 🔧

• Improve filter_* array handling, support FILTER_REQUIRE_ARRAY (#​2318), thanks @​herndlm!
• Asymmetric @property types (#​2327, #​2328, #​2329), #​9062, thanks @​jtojnar!
• Specify return type for filter_input() (#​2010), #​6261, thanks @​herndlm!
• Improve return type precision of filter_input with invalid first args (#​2333), thanks @​herndlm!
• Allow @property and @method to override above the same class (phpstan/phpstan-src@3467a21)
• Add FilterVarArrayDynamicReturnTypeExtension (#​2257), thanks @​zonuexe!

Bugfixes 🐛

• Fix usage of TypeSpecifierContext::truthy() (#​2230), #​3013, #​7686, thanks @​VincentLanglet!
• Parent template type should respect child class bound when unspecified (phpstan/phpstan-src@1017dc7), https://github.com/phpstan/phpstan-doctrine/issues/333
• Fix bug with match expression and treatPhpDocTypesAsCertain (#​2250), #​8937, thanks @​VincentLanglet!
• Generics: fix position variance of readonly-by-phpdoc properties (#​2337), #​9153, thanks @​jiripudil!
• PHPStan Pro - show errors from CollectedData (phpstan/phpstan-src@b85a961)
• Fix methods in IntersectionTypePropertyReflection (phpstan/phpstan-src@d1c4c6d)

Function signature fixes 🤖

• Improve Imagick method types (#​2325), thanks @​zonuexe!

Internals 🔍

• Switch to cweagans/composer-patches (#​2307), thanks @​herndlm!
• WritingToReadOnlyPropertiesRule - hook on better node (phpstan/phpstan-src@bddf573)
• Validate usages of assert* functions in TypeInferenceTestCase (#​2326), thanks @​staabm!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (fbdf565) 8.65% compared to head (9357f6a) 8.65%.

Additional details and impacted files

@@           Coverage Diff           @@
##              main    #647   +/-   ##
=======================================
  Coverage     8.65%   8.65%           
  Complexity      58      58           
=======================================
  Files           18      18           
  Lines          208     208           
=======================================
  Hits            18      18           
  Misses         190     190           

Flag	Coverage Δ
unittests	8.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.