Skip to content

Merge pull request #47 from robmachado/master #50

Merge pull request #47 from robmachado/master

Merge pull request #47 from robmachado/master #50

Triggered via push May 26, 2026 18:20
Status Failure
Total duration 20s
Artifacts

ci.yml

on: push
Matrix: Testes Automatizados
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 6 warnings
Testes Automatizados (7.4)
Process completed with exit code 2.
Testes Automatizados (7.4)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - psr/log is locked to version 3.0.2 and an update of this package was not requested. - psr/log 3.0.2 requires php >=8.0.0 -> your php version (7.4.33) does not satisfy that requirement. Problem 2 - doctrine/instantiator is locked to version 2.0.0 and an update of this package was not requested. - doctrine/instantiator 2.0.0 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement. Problem 3 - doctrine/lexer is locked to version 3.0.1 and an update of this package was not requested. - doctrine/lexer 3.0.1 requires php ^8.1 -> your php version (7.4.33) does not satisfy that requirement. Problem 4 - symfony/console is locked to version v6.4.20 and an update of this package was not requested. - symfony/console v6.4.20 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement. Problem 5 - symfony/deprecation-contracts is locked to version v3.5.1 and an update of this package was not requested. - symfony/deprecation-contracts v3.5.1 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement. Problem 6 - symfony/process is locked to version v6.4.20 and an update of this package was not requested. - symfony/process v6.4.20 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement. Problem 7 - symfony/service-contracts is locked to version v3.5.1 and an update of this package was not requested. - symfony/service-contracts v3.5.1 requires php >=8.1 -> your php version (7.4.33) does not satisfy that requirement. Problem 8 - symfony/string is locked to version v7.2.0 and an update of this package was not requested. - symfony/string v7.2.0 requires php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. Problem 9 - nfephp-org/sped-common is locked to version v5.1.16 and an update of this package was not requested. - nfephp-org/sped-common v5.1.16 requires psr/log ^1.0||^2.0||^3.0 -> satisfiable by psr/log[3.0.2]. - psr/log 3.0.2 requires php >=8.0.0 -> your php version (7.4.33) does not satisfy that requirement.
Testes Automatizados (8.1)
Process completed with exit code 2.
Testes Automatizados (8.1)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v7.2.0 and an update of this package was not requested. - symfony/string v7.2.0 requires php >=8.2 -> your php version (8.1.34) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v6.4.20 and an update of this package was not requested. - symfony/console v6.4.20 requires symfony/string ^5.4|^6.0|^7.0 -> satisfiable by symfony/string[v7.2.0]. - symfony/string v7.2.0 requires php >=8.2 -> your php version (8.1.34) does not satisfy that requirement.
Testes Automatizados (8.0)
Process completed with exit code 2.
Testes Automatizados (8.0)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - doctrine/instantiator is locked to version 2.0.0 and an update of this package was not requested. - doctrine/instantiator 2.0.0 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 2 - doctrine/lexer is locked to version 3.0.1 and an update of this package was not requested. - doctrine/lexer 3.0.1 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 3 - symfony/console is locked to version v6.4.20 and an update of this package was not requested. - symfony/console v6.4.20 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 4 - symfony/deprecation-contracts is locked to version v3.5.1 and an update of this package was not requested. - symfony/deprecation-contracts v3.5.1 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 5 - symfony/process is locked to version v6.4.20 and an update of this package was not requested. - symfony/process v6.4.20 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 6 - symfony/service-contracts is locked to version v3.5.1 and an update of this package was not requested. - symfony/service-contracts v3.5.1 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 7 - symfony/string is locked to version v7.2.0 and an update of this package was not requested. - symfony/string v7.2.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 8 - phpunit/phpunit is locked to version 9.6.22 and an update of this package was not requested. - doctrine/instantiator 2.0.0 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement. - phpunit/phpunit 9.6.22 requires doctrine/instantiator ^1.5.0 || ^2 -> satisfiable by doctrine/instantiator[2.0.0].
Testes Automatizados (7.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Testes Automatizados (8.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Testes Automatizados (8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Testes Automatizados (8.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Testes Automatizados (8.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Testes Automatizados (8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/