Skip to content

Update dependencies

Update dependencies #5

Triggered via pull request September 15, 2023 09:30
Status Failure
Total duration 30s
Artifacts

ci.yaml

on: pull_request
Coding style
14s
Coding style
Matrix: Unit tests
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 14 warnings
Unit tests (^4.4, 7.3)
symfony/flex (installed globally) contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer global config --no-plugins allow-plugins.symfony/flex [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins
Unit tests (^4.4, 7.3)
Process completed with exit code 1.
Unit tests (^5.4, 7.3)
symfony/flex (installed globally) contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer global config --no-plugins allow-plugins.symfony/flex [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins
Unit tests (^5.4, 7.3)
Process completed with exit code 1.
Unit tests (^6.3, 8.1)
The job was canceled because "_5_4_7_3" failed.
Unit tests (^6.3, 8.1)
symfony/flex (installed globally) contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer global config --no-plugins allow-plugins.symfony/flex [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins
Unit tests (^6.3, 8.1)
Process completed with exit code 1.
Unit tests (^5.4, 8.1)
symfony/flex (installed globally) contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer global config --no-plugins allow-plugins.symfony/flex [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins
Unit tests (^5.4, 8.1)
Process completed with exit code 1.
Unit tests (^5.4, 8.0)
The job was canceled because "_5_4_7_3" failed.
Unit tests (^5.4, 8.0)
symfony/flex (installed globally) contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer global config --no-plugins allow-plugins.symfony/flex [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins
Unit tests (^5.4, 8.0)
Process completed with exit code 1.
Unit tests (^6.3, 8.2)
The job was canceled because "_5_4_7_3" failed.
Unit tests (^6.3, 8.2)
The operation was canceled.
Unit tests (^4.4, 7.4)
The job was canceled because "_5_4_7_3" failed.
Unit tests (^4.4, 7.4)
The operation was canceled.
Unit tests (^5.4, 8.2)
The job was canceled because "_5_4_7_3" failed.
Unit tests (^5.4, 8.2)
The operation was canceled.
Unit tests (^5.4, 7.4)
The job was canceled because "_5_4_7_3" failed.
Unit tests (^5.4, 7.4)
The operation was canceled.
Unit tests (^5.4, 7.2)
symfony/flex (installed globally) contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer global config --no-plugins allow-plugins.symfony/flex [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins
Unit tests (^5.4, 7.2)
The operation was canceled.
Unit tests (^4.4, 7.2)
symfony/flex (installed globally) contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer global config --no-plugins allow-plugins.symfony/flex [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins
Unit tests (^4.4, 7.2)
The operation was canceled.
Unit tests (^4.4, 7.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests (^4.4, 7.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests (^5.4, 7.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests (^5.4, 7.3)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests (^6.3, 8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests (^6.3, 8.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests (^5.4, 8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests (^5.4, 8.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests (^5.4, 8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests (^5.4, 8.0)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests (^5.4, 7.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests (^5.4, 7.2)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests (^4.4, 7.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests (^4.4, 7.2)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/