chore(1.x): release 1.10.0 #284
Annotations
5 warnings
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
🧪 Run tests:
vendor/symfony/var-dumper/Cloner/AbstractCloner.php#L222
Symfony\Component\VarDumper\Cloner\AbstractCloner::__construct(): Implicitly marking parameter $casters as nullable is deprecated, the explicit nullable type must be used instead
|
|
🧪 Run tests:
vendor/amphp/socket/src/Internal/functions.php#L191
Amp\Socket\Internal\normalizeBindToOption(): Implicitly marking parameter $bindTo as nullable is deprecated, the explicit nullable type must be used instead
|
|
🧪 Run tests:
vendor/amphp/dns/src/functions.php#L40
Amp\Dns\resolve(): Implicitly marking parameter $typeRestriction as nullable is deprecated, the explicit nullable type must be used instead
|
|
🧪 Run tests:
vendor/amphp/dns/src/functions.php#L14
Amp\Dns\dnsResolver(): Implicitly marking parameter $dnsResolver as nullable is deprecated, the explicit nullable type must be used instead
|
Loading