CI #3658
php.yml
on: workflow_dispatch
Matrix: PHP-Linter
Linter
/
ecmascript-linter
Linter
/
json-linter
Linter
/
style-linter
Linter
/
yaml-linter
Quality control
18s
Security checks
13s
Matrix: unit-tests-linux
Matrix: unit-tests-windows
Cleanup artifacts
0s
Annotations
19 errors and 15 warnings
|
Security checks
Process completed with exit code 2.
|
|
Security checks
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires simplesamlphp/simplesamlphp ~2.3.0 | ~2.4.0 -> satisfiable by simplesamlphp/simplesamlphp[v2.4.7, v2.4.8].
- simplesamlphp/saml2-legacy v4.20.3 requires php ^8.3 -> your php version (8.1.34) does not satisfy that requirement.
- simplesamlphp/simplesamlphp v2.4.7 requires simplesamlphp/saml2-legacy ^4.18.1 -> satisfiable by simplesamlphp/saml2-legacy[v4.20.3].
- simplesamlphp/simplesamlphp v2.4.8 requires simplesamlphp/saml2-legacy ~4.19.0 -> found simplesamlphp/saml2-legacy[v4.19.0, v4.19.1, v4.19.2, v4.19.3] but these were not loaded, because they are affected by security advisories ("PKSA-11bv-m3wk-h9sn", "PKSA-4y26-97zb-p98g"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
|
|
Quality control
Process completed with exit code 2.
|
|
Quality control
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires simplesamlphp/simplesamlphp ~2.3.0 | ~2.4.0 -> satisfiable by simplesamlphp/simplesamlphp[v2.4.7, v2.4.8].
- simplesamlphp/saml2-legacy v4.20.3 requires simplesamlphp/xml-common ^2.7 -> found simplesamlphp/xml-common[v2.7.0, ..., v2.8.1] but it conflicts with your root composer.json require (~1.25.0).
- simplesamlphp/simplesamlphp v2.4.7 requires simplesamlphp/saml2-legacy ^4.18.1 -> satisfiable by simplesamlphp/saml2-legacy[v4.20.3].
- simplesamlphp/simplesamlphp v2.4.8 requires simplesamlphp/saml2-legacy ~4.19.0 -> found simplesamlphp/saml2-legacy[v4.19.0, v4.19.1, v4.19.2, v4.19.3] but these were not loaded, because they are affected by security advisories ("PKSA-11bv-m3wk-h9sn", "PKSA-4y26-97zb-p98g"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
|
|
Unit tests, PHP 8.4, ubuntu-latest
Process completed with exit code 2.
|
|
Unit tests, PHP 8.4, ubuntu-latest
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires simplesamlphp/simplesamlphp ~2.3.0 | ~2.4.0 -> satisfiable by simplesamlphp/simplesamlphp[v2.4.7, v2.4.8].
- simplesamlphp/saml2-legacy v4.20.3 requires simplesamlphp/xml-common ^2.7 -> found simplesamlphp/xml-common[v2.7.0, ..., v2.8.1] but it conflicts with your root composer.json require (~1.25.0).
- simplesamlphp/simplesamlphp v2.4.7 requires simplesamlphp/saml2-legacy ^4.18.1 -> satisfiable by simplesamlphp/saml2-legacy[v4.20.3].
- simplesamlphp/simplesamlphp v2.4.8 requires simplesamlphp/saml2-legacy ~4.19.0 -> found simplesamlphp/saml2-legacy[v4.19.0, v4.19.1, v4.19.2, v4.19.3] but these were not loaded, because they are affected by security advisories ("PKSA-11bv-m3wk-h9sn", "PKSA-4y26-97zb-p98g"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
|
|
Unit tests, PHP 8.3, ubuntu-latest
Process completed with exit code 2.
|
|
Unit tests, PHP 8.3, ubuntu-latest
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires simplesamlphp/simplesamlphp ~2.3.0 | ~2.4.0 -> satisfiable by simplesamlphp/simplesamlphp[v2.4.7, v2.4.8].
- simplesamlphp/saml2-legacy v4.20.3 requires simplesamlphp/xml-common ^2.7 -> found simplesamlphp/xml-common[v2.7.0, ..., v2.8.1] but it conflicts with your root composer.json require (~1.25.0).
- simplesamlphp/simplesamlphp v2.4.7 requires simplesamlphp/saml2-legacy ^4.18.1 -> satisfiable by simplesamlphp/saml2-legacy[v4.20.3].
- simplesamlphp/simplesamlphp v2.4.8 requires simplesamlphp/saml2-legacy ~4.19.0 -> found simplesamlphp/saml2-legacy[v4.19.0, v4.19.1, v4.19.2, v4.19.3] but these were not loaded, because they are affected by security advisories ("PKSA-11bv-m3wk-h9sn", "PKSA-4y26-97zb-p98g"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
|
|
Unit tests, PHP 8.2, ubuntu-latest
Process completed with exit code 2.
|
|
Unit tests, PHP 8.2, ubuntu-latest
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires simplesamlphp/simplesamlphp ~2.3.0 | ~2.4.0 -> satisfiable by simplesamlphp/simplesamlphp[v2.4.7, v2.4.8].
- simplesamlphp/saml2-legacy v4.20.3 requires php ^8.3 -> your php version (8.2.32) does not satisfy that requirement.
- simplesamlphp/simplesamlphp v2.4.7 requires simplesamlphp/saml2-legacy ^4.18.1 -> satisfiable by simplesamlphp/saml2-legacy[v4.20.3].
- simplesamlphp/simplesamlphp v2.4.8 requires simplesamlphp/saml2-legacy ~4.19.0 -> found simplesamlphp/saml2-legacy[v4.19.0, v4.19.1, v4.19.2, v4.19.3] but these were not loaded, because they are affected by security advisories ("PKSA-11bv-m3wk-h9sn", "PKSA-4y26-97zb-p98g"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
|
|
Unit tests, PHP 8.1, ubuntu-latest
Process completed with exit code 2.
|
|
Unit tests, PHP 8.1, ubuntu-latest
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires simplesamlphp/simplesamlphp ~2.3.0 | ~2.4.0 -> satisfiable by simplesamlphp/simplesamlphp[v2.4.7, v2.4.8].
- simplesamlphp/saml2-legacy v4.20.3 requires php ^8.3 -> your php version (8.1.34) does not satisfy that requirement.
- simplesamlphp/simplesamlphp v2.4.7 requires simplesamlphp/saml2-legacy ^4.18.1 -> satisfiable by simplesamlphp/saml2-legacy[v4.20.3].
- simplesamlphp/simplesamlphp v2.4.8 requires simplesamlphp/saml2-legacy ~4.19.0 -> found simplesamlphp/saml2-legacy[v4.19.0, v4.19.1, v4.19.2, v4.19.3] but these were not loaded, because they are affected by security advisories ("PKSA-11bv-m3wk-h9sn", "PKSA-4y26-97zb-p98g"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
|
|
Unit tests, PHP 8.1, windows-latest
Process completed with exit code 1.
|
|
Unit tests, PHP 8.3, windows-latest
The strategy configuration was canceled because "unit-tests-windows.windows-latest_8_1" failed
|
|
Unit tests, PHP 8.3, windows-latest
The operation was canceled.
|
|
Unit tests, PHP 8.4, windows-latest
The strategy configuration was canceled because "unit-tests-windows.windows-latest_8_1" failed
|
|
Unit tests, PHP 8.4, windows-latest
Process completed with exit code 1.
|
|
Unit tests, PHP 8.2, windows-latest
The strategy configuration was canceled because "unit-tests-windows.windows-latest_8_1" failed
|
|
Unit tests, PHP 8.2, windows-latest
The operation was canceled.
|
|
Linter / yaml-linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PHP-Linter (8.4) / linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Security checks
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PHP-Linter (8.3) / linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Quality control
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PHP-Linter (8.2) / linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PHP-Linter (8.1) / linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Linter / json-linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests, PHP 8.4, ubuntu-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests, PHP 8.3, ubuntu-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests, PHP 8.2, ubuntu-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests, PHP 8.1, ubuntu-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests, PHP 8.1, windows-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests, PHP 8.4, windows-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests, PHP 8.2, windows-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|