Skip to content

Security

Security #330

Triggered via schedule July 7, 2024 00:07
Status Success
Total duration 1m 58s
Artifacts

security.yaml

on: schedule
Matrix: security
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 9 warnings
Security check (PHP 8.2)
Your requirements could not be resolved to an installable set of packages. Problem 1 - jane-php/automapper-bundle[v7.1.0, ..., v7.5.3] require jane-php/automapper ^7.0 -> satisfiable by jane-php/automapper[v7.0.0, ..., v7.5.3]. - jane-php/automapper[v7.0.0, ..., v7.1.2] require symfony/property-info ^5.2 -> found symfony/property-info[v5.2.0, ..., v5.4.41] but these were not loaded, likely because it conflicts with another require. - jane-php/automapper v7.1.3 requires symfony/property-info ^5.3 -> found symfony/property-info[v5.3.0, ..., v5.4.41] but these were not loaded, likely because it conflicts with another require. - jane-php/automapper[v7.1.4, ..., v7.5.3] require symfony/property-info ^5.3 || ^6.0 -> found symfony/property-info[v5.3.0, ..., v5.4.41, v6.0.0, ..., v6.4.9] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires jane-php/automapper-bundle ^7.1 -> satisfiable by jane-php/automapper-bundle[v7.1.0, ..., v7.5.3]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Security check (PHP 8.0)
Your requirements could not be resolved to an installable set of packages. Problem 1 - jane-php/automapper-bundle[v7.1.0, ..., v7.5.3] require jane-php/automapper ^7.0 -> satisfiable by jane-php/automapper[v7.0.0, ..., v7.5.3]. - jane-php/automapper[v7.0.0, ..., v7.1.2] require symfony/property-info ^5.2 -> found symfony/property-info[v5.2.0, ..., v5.4.41] but these were not loaded, likely because it conflicts with another require. - jane-php/automapper v7.1.3 requires symfony/property-info ^5.3 -> found symfony/property-info[v5.3.0, ..., v5.4.41] but these were not loaded, likely because it conflicts with another require. - jane-php/automapper[v7.1.4, ..., v7.5.3] require symfony/property-info ^5.3 || ^6.0 -> found symfony/property-info[v5.3.0, ..., v5.4.41, v6.0.0, ..., v6.4.9] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires jane-php/automapper-bundle ^7.1 -> satisfiable by jane-php/automapper-bundle[v7.1.0, ..., v7.5.3]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Security check (PHP 8.1)
Your requirements could not be resolved to an installable set of packages. Problem 1 - jane-php/automapper-bundle[v7.1.0, ..., v7.5.3] require jane-php/automapper ^7.0 -> satisfiable by jane-php/automapper[v7.0.0, ..., v7.5.3]. - jane-php/automapper[v7.0.0, ..., v7.1.2] require symfony/property-info ^5.2 -> found symfony/property-info[v5.2.0, ..., v5.4.41] but these were not loaded, likely because it conflicts with another require. - jane-php/automapper v7.1.3 requires symfony/property-info ^5.3 -> found symfony/property-info[v5.3.0, ..., v5.4.41] but these were not loaded, likely because it conflicts with another require. - jane-php/automapper[v7.1.4, ..., v7.5.3] require symfony/property-info ^5.3 || ^6.0 -> found symfony/property-info[v5.3.0, ..., v5.4.41, v6.0.0, ..., v6.4.9] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires jane-php/automapper-bundle ^7.1 -> satisfiable by jane-php/automapper-bundle[v7.1.0, ..., v7.5.3]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Security check (PHP 8.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Security check (PHP 8.2)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Security check (PHP 8.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/
Security check (PHP 8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Security check (PHP 8.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Security check (PHP 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/
Security check (PHP 8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Security check (PHP 8.1)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Security check (PHP 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/