Skip to content

Upgrade PHPUnit configuration to version 10 #133

Upgrade PHPUnit configuration to version 10

Upgrade PHPUnit configuration to version 10 #133

Triggered via pull request March 20, 2026 12:01
Status Failure
Total duration 1m 3s
Artifacts

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 6 warnings
build (8.3, lowest)
Process completed with exit code 1.
build (8.3, lowest): src/Normalizer/AbsoluteDateNormalizer.php#L53
Method AssoConnect\PHPDateBundle\Normalizer\AbsoluteDateNormalizer::denormalize() has parameter $context with no value type specified in iterable type array.
build (8.3, lowest): src/Normalizer/AbsoluteDateNormalizer.php#L45
Method AssoConnect\PHPDateBundle\Normalizer\AbsoluteDateNormalizer::supportsNormalization() has parameter $context with no value type specified in iterable type array.
build (8.3, lowest): src/Normalizer/AbsoluteDateNormalizer.php#L0
Ignored error pattern #^Return type \(AssoConnect\\PHPDate\\AbsoluteDate\) of method AssoConnect\\PHPDateBundle\\Normalizer\\AbsoluteDateNormalizer\:\:denormalize\(\) should be covariant with return type \(\(\$type is class\-string\<object\> \? object \: mixed\)\) of method Symfony\\Component\\Serializer\\Normalizer\\DenormalizerInterface\:\:denormalize\(\)$# (method.childReturnType) in path /home/runner/work/php-date-bundle/php-date-bundle/src/Normalizer/AbsoluteDateNormalizer.php was not matched in reported errors.
build (8.4, lowest)
Process completed with exit code 1.
build (8.4, lowest): src/Normalizer/AbsoluteDateNormalizer.php#L53
Method AssoConnect\PHPDateBundle\Normalizer\AbsoluteDateNormalizer::denormalize() has parameter $context with no value type specified in iterable type array.
build (8.4, lowest): src/Normalizer/AbsoluteDateNormalizer.php#L45
Method AssoConnect\PHPDateBundle\Normalizer\AbsoluteDateNormalizer::supportsNormalization() has parameter $context with no value type specified in iterable type array.
build (8.4, lowest): src/Normalizer/AbsoluteDateNormalizer.php#L0
Ignored error pattern #^Return type \(AssoConnect\\PHPDate\\AbsoluteDate\) of method AssoConnect\\PHPDateBundle\\Normalizer\\AbsoluteDateNormalizer\:\:denormalize\(\) should be covariant with return type \(\(\$type is class\-string\<object\> \? object \: mixed\)\) of method Symfony\\Component\\Serializer\\Normalizer\\DenormalizerInterface\:\:denormalize\(\)$# (method.childReturnType) in path /home/runner/work/php-date-bundle/php-date-bundle/src/Normalizer/AbsoluteDateNormalizer.php was not matched in reported errors.
build (8.3, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. 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/
build (8.4, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. 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/
build (8.3, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4. 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/
SonarScanner
This action is deprecated and will be removed in a future release. Please use the sonarqube-scan-action action instead. The sonarqube-scan-action is a drop-in replacement for this action.
build (8.4, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4. 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/
SonarScanner
This action is deprecated and will be removed in a future release. Please use the sonarqube-scan-action action instead. The sonarqube-scan-action is a drop-in replacement for this action.