Repository navigation
fix(deps): update all non-major dependencies - #58
renovate-appwrite[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Code review
The PR updates the MongoDB image, Composer and PHP base images, and the Composer dependency set. It also raises the Note Not approving while a bug finding is open: Pint bump prevents PHP 8.2 development installs Fix with agent prompt### Issue 1
composer.lock:364
**Pint bump prevents PHP 8.2 development installs**
Pint v1.32.3 requires PHP ^8.3, so a normal `composer install` now fails on PHP 8.2 even though this project declares PHP >=8.0 and the previous lock supported PHP 8.2. Contributors on that supported runtime can no longer install the development dependencies to run the project checks; please retain a PHP 8.2-compatible Pint version or update the project's supported PHP floor intentionally.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Walkthrough (4)
Still open from earlier reviews (1)
Reviewed Tip Comment |
673833e to
64f3137
Compare
| { | ||
| "name": "laravel/pint", | ||
| "version": "v1.25.1", | ||
| "version": "v1.32.3", |
There was a problem hiding this comment.
Pint bump prevents PHP 8.2 development installs
Pint v1.32.3 requires PHP ^8.3, so a normal composer install now fails on PHP 8.2 even though this project declares PHP >=8.0 and the previous lock supported PHP 8.2. Contributors on that supported runtime can no longer install the development dependencies to run the project checks; please retain a PHP 8.2-compatible Pint version or update the project's supported PHP floor intentionally.
Prompt To Fix With AI
This is a comment left during a code review.
Path: composer.lock
Line: 364
Comment:
**Pint bump prevents PHP 8.2 development installs**
Pint v1.32.3 requires PHP ^8.3, so a normal `composer install` now fails on PHP 8.2 even though this project declares PHP >=8.0 and the previous lock supported PHP 8.2. Contributors on that supported runtime can no longer install the development dependencies to run the project checks; please retain a PHP 8.2-compatible Pint version or update the project's supported PHP floor intentionally.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟡 Minor · bug · Reply if this doesn't apply.
64f3137 to
4240afd
Compare

This PR contains the following updates:
php-8.3-0.1.0→php-8.3-0.2.12.0→2.102.111.25.1→1.32.38.2→8.32.1.29→2.3.52.3.7(+1)9.6.33→9.6.394.9.*→4.10.*Release Notes
laravel/pint
v1.32.3Compare Source
Full Changelog: laravel/pint@v1.32.2...v1.32.3
v1.32.2Compare Source
What's Changed
New Contributors
Full Changelog: laravel/pint@v1.32.1...v1.32.2
v1.32.1Compare Source
Full Changelog: laravel/pint@v1.32.0...v1.32.1
v1.32.0Compare Source
Full Changelog: laravel/pint@v1.31.1...v1.32.0
v1.31.1Compare Source
What's Changed
Full Changelog: laravel/pint@v1.31.0...v1.31.1
v1.31.0Compare Source
Full Changelog: laravel/pint@v1.30.6...v1.31.0
v1.30.6Compare Source
v1.30.5Compare Source
What's Changed
Full Changelog: laravel/pint@v1.30.4...v1.30.5
v1.30.4Compare Source
What's Changed
New Contributors
Full Changelog: laravel/pint@v1.30.3...v1.30.4
v1.30.3Compare Source
Full Changelog: laravel/pint@v1.30.2...v1.30.3
v1.30.2Compare Source
Full Changelog: laravel/pint@v1.30.1...v1.30.2
v1.30.1Compare Source
Full Changelog: laravel/pint@v1.30.0...v1.30.1
v1.30.0Compare Source
What's Changed
into pint.json by @cosmastech in #454New Contributors
Full Changelog: laravel/pint@v1.29.3...v1.30.0
v1.29.3Compare Source
Full Changelog: laravel/pint@v1.29.2...v1.29.3
v1.29.2Compare Source
httplaravel/agent-detectorv1.29.1Compare Source
v1.29.0Compare Source
Pint/phpdoc_type_annotations_onlycustom rule.v1.28.0Compare Source
fully_qualified_strict_typesrulev1.27.1Compare Source
--paralleloption alongside--configby @kkunjas in #418v1.27.0Compare Source
agentformat, which is automatically selected when Pint is executed via Claude Code or OpenCode by @nunomaduro in #415v1.26.0Compare Source
stdinsupport with explicit opt-in flag by @A909M in #403pintas non "dev" dependency by @SamAsEnd in #407phpstan/phpstan-phar-composer-source (phpstan/phpstan)
v2.3.5Compare Source
v2.3.4Compare Source
v2.3.3Compare Source
v2.3.2Compare Source
v2.3.1Compare Source
v2.3.0Compare Source
v2.2.17Compare Source
v2.2.16Compare Source
v2.2.15Compare Source
v2.2.14Compare Source
v2.2.13Compare Source
v2.2.12Compare Source
v2.2.11Compare Source
v2.2.10Compare Source
v2.2.9Compare Source
v2.2.8Compare Source
v2.2.7Compare Source
v2.2.6Compare Source
v2.2.5Compare Source
v2.2.4Compare Source
v2.2.3Compare Source
v2.2.2Compare Source
v2.2.1Compare Source
v2.2.0Compare Source
v2.1.56Compare Source
v2.1.55Compare Source
v2.1.54Compare Source
v2.1.53Compare Source
v2.1.52Compare Source
v2.1.51Compare Source
v2.1.50Compare Source
v2.1.49Compare Source
v2.1.48Compare Source
v2.1.47Compare Source
v2.1.46Compare Source
v2.1.45Compare Source
v2.1.44Compare Source
v2.1.43Compare Source
v2.1.42Compare Source
v2.1.41Compare Source
v2.1.40Compare Source
v2.1.39Compare Source
v2.1.38Compare Source
v2.1.37Compare Source
v2.1.36Compare Source
v2.1.35Compare Source
v2.1.34Compare Source
v2.1.33Compare Source
v2.1.32Compare Source
v2.1.31Compare Source
v2.1.30Compare Source
sebastianbergmann/phpunit (phpunit/phpunit)
v9.6.39: PHPUnit 9.6.39Compare Source
Changed
Removed
phpunit-library-X.Y.Z.phar) is no longer built, it could not be loaded since PHPUnit 9.5.8Learn how to install or update PHPUnit 9.6 in the documentation.
Keep up to date with PHPUnit:
v9.6.38: PHPUnit 9.6.38Compare Source
Changed
Learn how to install or update PHPUnit 9.6 in the documentation.
Keep up to date with PHPUnit:
v9.6.37: PHPUnit 9.6.37Compare Source
Changed
unserialize()(which emits a warning for an empty string as of PHP 8.6)Learn how to install or update PHPUnit 9.6 in the documentation.
Keep up to date with PHPUnit:
v9.6.36: PHPUnit 9.6.36Compare Source
Changed
spl_object_id()instead ofspl_object_hash()(which will be deprecated in PHP 8.6)@) when callingDeepCopy\DeepCopy::copy()because it usesspl_object_hash()(which will be deprecated in PHP 8.6)Learn how to install or update PHPUnit 9.6 in the documentation.
Keep up to date with PHPUnit:
v9.6.35: PHPUnit 9.6.35Compare Source
Changed
Learn how to install or update PHPUnit 9.6 in the documentation.
Keep up to date with PHPUnit:
v9.6.34: PHPUnit 9.6.34Compare Source
Fixed
Learn how to install or update PHPUnit 9.6 in the documentation.
Keep up to date with PHPUnit:
ramsey/uuid
v4.10.0Compare Source
Changed
GenericTimeConverter::convertTime()andPhpTimeConverter::convertTime()now return the seconds rounded down, with microseconds that count forward from them. For example, 1.5 seconds before the epoch is now -2 seconds and 500000 microseconds, where it was -1 seconds and 500000 microseconds. The microseconds are added to the seconds, so -2 seconds plus 0.5 seconds is -1.5 seconds.Time::toString()returns-1.500000for this time. ThegetDateTime()methods read the time from anyTimeConverterInterfaceimplementation in the same way.Uuid::fromString(), the string codecs, and the validators now accept only the standard forms of a UUID string: 32 hexadecimal digits with hyphens in all four standard positions or with no hyphens, optionally in one pair of braces, optionally after oneurn:prefix, oneuuid:prefix, or both in that order. Before, they removed these prefixes, braces, and (in the codecs) hyphens from anywhere in the string, so strings such as{{6ba7b8109dad-11d180b400c04fd430c8uuid:were read as UUIDs.Uuid::uuid7()now throwsInvalidArgumentExceptionfor a date before 1970-01-01 00:00:00 UTC or after 10889-08-02 05:31:50.655 UTC. Before, it returned a UUID with a wrong timestamp.Uuid::fromDateTime(),GenericTimeConverter::calculateTime(), andPhpTimeConverter::calculateTime()now throwInvalidArgumentExceptionfor a time before the Gregorian calendar epoch, 1582-10-15 00:00:00 UTC. Before,PhpTimeConverterreturned a wrong timestamp.Uuid::fromDateTime(),GenericTimeConverter::calculateTime(), andPhpTimeConverter::calculateTime()now throwInvalidArgumentExceptionfor a time after 5236-03-31 21:21:00.684697 UTC, the last time that fits in the 60-bit timestamp of a version 1, 2, or 6 UUID. Before, the timestamp lost its highest bits, so the UUID's date started again from 1582.Uuid::uuid7()now stores the fraction of the millisecond in the 12 bits after the version, using method 3 of RFC 9562 section 6.2. Version 7 UUIDs now sort by creation time to about a microsecond, even when different processes created them. They have 62 random bits, where they had 74, and the UUID for a given date and time has different bits after the timestamp than before.UnixTimeGeneratornow asks its random generator for 8 bytes for each new counter and 16 bytes for a seed, where it asked for 16 bytes at first and 10 bytes after that.Uuid::uuid7()now throwsTimeSourceExceptionwhen the system clock is before 1970-01-01 00:00:00 UTC or after 10889-08-02 05:31:50.655 UTC, the first and last times a version 7 UUID can have. Before, it returned a UUID with a wrong timestamp. It throws the same exception when calls for the last of those times have used every timestamp that is left.Uuid::uuid7()now throwsRandomSourceExceptionwhen a custom random generator returns a different number of bytes thanUnixTimeGeneratorasked it for. Before, PHP raised a warning or the UUID had wrong bits.Uuid::uuid8()now throwsInvalidArgumentExceptionunless it receives exactly 16 bytes. Before, shorter input raised aTypeError, and the default factory used the first 16 bytes of longer input. The other factory methods throw the same exception when a custom generator returns the wrong number of bytes.Deprecated
BinaryUtils::applyVariant()andBinaryUtils::applyVersion()are deprecated. ramsey/uuid no longer uses them.Fixed
Uuid::uuid7()no longer changes the UUIDs that later calls without a date return. Before, after a call with a future date, every later call returned a UUID with that date until the clock passed it.PhpTimeConverter::convertTime()no longer returns wrong microseconds, such as dropping a leading zero, depending on theprecisionini setting. It now uses integer math; fixed in #653.getDateTime()no longer throwsInvalidArgumentExceptionfor version 1 and version 6 UUIDs whose time is just before the Unix epoch, such as1969-12-31 23:59:59.999999; fixed in #645.getDateTime()no longer returns a time after the Unix epoch for UUIDs whose time is less than one second before it.GenericTimeConverter::convertTime()andPhpTimeConverter::convertTime()no longer return a wrong time for times before the Unix epoch. For times less than one second before the epoch, the minus sign was lost. For earlier times,calculateTime()read the returned seconds and microseconds as a different time, so a timestamp 1.5 seconds before the epoch converted back as 0.5 seconds before it.new FeatureSet(useGuids: true)now generate valid GUIDs. Before,uuid1()always threwUnableToBuildUuidException, other methods threw for some values, and the GUIDs they returned had the wrong version. Because of this fix,uuid3()anduuid5()on such a factory now return different GUIDs than before for the same namespace and name, so GUIDs stored from earlier versions will not match; fixed in #651.FeatureSet::setTimeProvider()andFeatureSet::setNodeProvider()now also apply to version 2 (DCE Security) UUIDs, andFeatureSet::setCalculator()now also rebuilds the builder and codec so they use the new calculator. As a result,FeatureSet::getBuilder()andFeatureSet::getCodec()return new objects aftersetCalculator()is called; fixed in #652.Hexadecimal,Integer, and the$nodeparameter ofUuid::uuid1()no longer accept a value that ends with a newline character. Before,Uuid::uuid1()returned a malformed UUID for such a node.BuilderCollection::unserialize()andNodeProviderCollection::unserialize()now throwUnsupportedOperationExceptionfor a value that is not a serialized array, instead of raising aTypeError.InvalidUuidStringExceptionwhen the serialized value is not a UUID string. Before, a changed serialized value produced aUuidInterfaceobject whosetoString()method returned that value as it was.UuidV2::getLocalDomainName()now throwsDceSecurityExceptionfor a version 2 UUID whose local domain is not the person, group, or org domain. Before, it raised aTypeError.BrickMathCalculator::divide()now throwsInvalidArgumentExceptionfor a divisor of zero. Before, it let the brick/math exception through.toUuidV1()ortoUuidV6()on a UUID of another version, such as one returned byUuid::uuid4(), now throwsUnsupportedOperationException. Before, it raised aTypeError, anError, or anAssertionError, depending on the method and thezend.assertionssetting.Decimalnow removes the whitespace around a numeric string. Before, it kept the whitespace,isNegative()returnedfalsefor a negative number with whitespace before it, andBrickMathCalculatorcould not read the value.Decimalno longer changes a number too small for a float, such as1e-400, to0.Decimal,Hexadecimal,Integer, orTimewhose serialized value has the wrong type, such as an array, now throwsValueError, andTime::unserialize()throwsUnsupportedOperationException. Before, these raised aTypeError.v4.9.4Compare Source
Fixed
^0.19,^0.20, and^1.0; fixed in #642.v4.9.3Compare Source
Fixed
^0.14to^0.17; fixed in #638.^0.18.v4.9.2Compare Source
Fixed
(int)cast to avoid float-string cast warnings in PHP 8.5.^0.8.16from^0.8.8. ramsey/uuid had been usingBigInteger::toBytes()inUnixTimeGenerator(for version 7 UUIDs) since v4.6.0, but it wasn't added to brick/math until v0.8.16.Configuration
📅 Schedule: (UTC)
* * * * 1)🚦 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 CLI.