chore(deps): Update php deps #87
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/php-deps
branch
from
bb4b0c5
to
58f3926
Compare
renovate
bot
changed the title
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Signed-off-by: Oğuzhan Durgun <oguzhandurgun95@gmail.com>
oguzhand95
force-pushed
the
renovate/php-deps
branch
from
58f3926
to
1f7e7f0
Compare
oguzhand95
approved these changes
May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.10.67->1.11.05.23.1->5.24.0Release Notes
phpstan/phpstan (phpstan/phpstan)
v1.11.0Compare Source
Read the article about PHPStan 1.11 on phpstan.org »
Major new features 🚀
@phpstan-ignorecomment (uses current or next line automatically)ignoreErrorssection of your configuration file (phpstan.neon)-v@phpstan-ignore-lineand@phpstan-ignore-next-lineto the new@phpstan-ignorecomment style with error identifiers. The old comment style is dangerous because it ignores all errors, current and future, on that line.ignoreErrors, from your baseline and also ignored locally in source code using comments--proCLI option@param-immediately-invoked-callable,@param-later-invoked-callable@phpstan-pure@param-closure-thisto describe what$thisis bound to in a passed closurereportPossiblyNonexistentGeneralArrayOffsetreportPossiblyNonexistentConstantArrayOffsetBleeding edge 🔪
@phpstan-pureabove functions and methodsnew/function call/method call/static method call on a separate line without any side effects even without@phpstan-purePHPDoc tag on the declaration side@param-out(phpstan/phpstan-src@56b2002)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: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 🔧
checkMissingIterableValueType: falseandcheckGenericClassInNonGenericObjectType: falsein favour of ignoring via identifiers (phpstan/phpstan-src@a649981)newtype (#3050), #9704, thanks @ruudk!RuleErrorBuilder::file()- file path needs to exist (phpstan/phpstan-src@c453f29)$thisand used variables after invoking closure (#2980)@phan-prefixes on recognized PHPDoc tags (#3000), thanks @anomiex!pure-callableandpure-ClosurePHPDoc types (phpstan/phpstan-src@cdaff5f)highlight_string()flips side-effects depending on $return (#3021), thanks @staabm!Bugfixes 🐛
AccessoryNonFalsyStringType::toInteger()returnIntegerTypeinstead of non-zero (#3018), #10893, thanks @zonuexe!polluteScopeWithAlwaysIterableForeach(#3029), #10922, thanks @VincentLanglet!count($x) > $n === truenegation (#3037), #10952, thanks @rvanvelzen!newwith wrong name case (phpstan/phpstan-src@59ac31a)preg_match_allbehaviour with no flags (phpstan/phpstan-src@a856ec7)file_get_contentsis an impure function (phpstan/phpstan-src@2b5b317)ClosureType::equals()(phpstan/phpstan-src@29c35b5)exceptions.implicitThrows: false(#3016), thanks @janedbal!ConstantArrayType::hasOffsetValueType()for offset union type where all types are valid (phpstan/phpstan-src@26e949b)non-empty-listalways has offset 0 (phpstan/phpstan-src@f4d1d48)non-empty-string/non-falsey-stringaftermb_strlen()(#3038), thanks @staabm!Type::isOffsetAccessLegal()to detect offset access that crashes even inisset()(#3045), #8393, #10926, thanks @rajyan!match()condition correctly (#3053), #10974, #9694, thanks @rvanvelzen!json_decodewith force array flag: subtract all objects, not just stdClass (#3052), thanks @rajyan!strlen($x) > $n === truenegation (#3040), thanks @staabm!Continue_points should not be used forwhile (true)(#3057), #10980, thanks @greew!Function signature fixes 🤖
stream_get_meta_data()optional (#3024), #10887, thanks @hirokinoue!Closure::bind$newScopeparam (#2817), thanks @mvorisek!Imagick::identifyImage()return type (#3017), thanks @SVillette!Internals 🔍
ClassReflection::getClassTypeDescription()(phpstan/phpstan-src@dec9e43)RuleErrorBuilder::treatPhpDocTypesAsCertainTip()for a bit more DRYness (#3035), thanks @axlon!vimeo/psalm (vimeo/psalm)
v5.24.0Compare Source
What's Changed
Features
callableby @weirdan in https://github.com/vimeo/psalm/pull/10805parentbeing used in callable context when the class does not extend anything by @kkmuffme in https://github.com/vimeo/psalm/pull/10838Fixes
getmxrr()by @ThomasLandauer in https://github.com/vimeo/psalm/pull/10847mailto impure functions list by @smaddock in https://github.com/vimeo/psalm/pull/10923Docs
Internal changes
Other changes
New Contributors
Full Changelog: vimeo/psalm@5.23.1...5.24.0
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.