v0.47.0: @type with @container:@set stays an array in JSON-LD 1.1 (#t… #10
skydudieci.yml
on: push
W3C Conformance Report
16s
Matrix: test
Annotations
18 errors and 5 warnings
|
Unit · PHP 8.1
Process completed with exit code 2.
|
|
Unit · PHP 8.1
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires pestphp/pest ^2.14 -> satisfiable by pestphp/pest[v2.14.0, ..., v2.36.1].
- brianium/paratest[v7.9.0, ..., v7.11.2] require php ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement.
- brianium/paratest[v7.12.0, ..., v7.20.0] require php ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement.
- brianium/paratest[v7.21.0, ..., v7.23.0] require php ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement.
- brianium/paratest[v7.4.0, ..., v7.5.7] require php ~8.2.0 || ~8.3.0 -> your php version (8.1.34) does not satisfy that requirement.
- brianium/paratest[v7.4.8, ..., v7.8.4] require php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement.
- brianium/paratest v7.8.5 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement.
- pestphp/pest v2.14.0 conflicts with phpunit/phpunit 10.5.63.
- pestphp/pest v2.14.0 requires phpunit/phpunit ^10.3.1 -> satisfiable by phpunit/phpunit[10.5.62, 10.5.63].
- pestphp/pest v2.33.3 requires brianium/paratest ^7.4.0 -> satisfiable by brianium/paratest[v7.4.0, ..., v7.23.0].
- pestphp/pest v2.33.5 requires brianium/paratest ^7.4.1 -> satisfiable by brianium/paratest[v7.4.1, ..., v7.23.0].
- pestphp/pest v2.34.3 requires brianium/paratest ^7.4.3 -> satisfiable by brianium/paratest[v7.4.3, ..., v7.23.0].
- pestphp/pest v2.36.1 requires php ^8.2.0 -> your php version (8.1.34) does not satisfy that requirement.
- Conclusion: don't install pestphp/pest v2.15.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.16.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.17.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.18.1 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.19.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.19.1 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.20.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.22.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.22.1 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.23.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.23.1 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.23.2 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.24.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.24.1 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.26.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.27.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.28.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.28.1 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.29.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.30.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.31.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.32.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.33.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.33.4 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.34.0 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.34.1 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.34.2 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.34.4 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.34.5 (conflict analysis result)
- Conclusion: don't install pestphp/pest v2.34.6 (conflict analys
|
|
W3C Conformance Report
Process completed with exit code 2.
|
|
Unit · PHP 8.3
Process completed with exit code 1.
|
|
Unit · PHP 8.3:
src/Context/TermDefinitions.php#L601
Right side of && is always true.
|
|
Unit · PHP 8.3:
src/Context/TermDefinitions.php#L516
Right side of && is always true.
|
|
Unit · PHP 8.3:
src/Context/TermDefinitions.php#L500
Right side of && is always true.
|
|
Unit · PHP 8.3:
src/Context/TermDefinitions.php#L456
Right side of && is always true.
|
|
Unit · PHP 8.2
Process completed with exit code 1.
|
|
Unit · PHP 8.2:
src/Context/TermDefinitions.php#L601
Right side of && is always true.
|
|
Unit · PHP 8.2:
src/Context/TermDefinitions.php#L516
Right side of && is always true.
|
|
Unit · PHP 8.2:
src/Context/TermDefinitions.php#L500
Right side of && is always true.
|
|
Unit · PHP 8.2:
src/Context/TermDefinitions.php#L456
Right side of && is always true.
|
|
Unit · PHP 8.4
Process completed with exit code 1.
|
|
Unit · PHP 8.4:
src/Context/TermDefinitions.php#L601
Right side of && is always true.
|
|
Unit · PHP 8.4:
src/Context/TermDefinitions.php#L516
Right side of && is always true.
|
|
Unit · PHP 8.4:
src/Context/TermDefinitions.php#L500
Right side of && is always true.
|
|
Unit · PHP 8.4:
src/Context/TermDefinitions.php#L456
Right side of && is always true.
|
|
Unit · PHP 8.1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
W3C Conformance Report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit · PHP 8.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit · PHP 8.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit · PHP 8.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|