wp-compatibility-test.yml
on: push
WP Plugin Check (PHP 8.3)
13s
PHPCS (PHP 8.3)
17s
WP VIP CS (PHP 8.3)
13s
PHPMD (PHP 8.3)
14s
Psalm Static Analysis (PHP 8.3)
12s
Security Scan (PHP 8.3)
16s
PHPStan for WP (PHP 8.3)
17s
Matrix: wp-version-test
Annotations
46 errors and 22 warnings
|
Psalm Static Analysis (PHP 8.3)
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
WP VIP CS (PHP 8.3)
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
WP Plugin Check (PHP 8.3)
Process completed with exit code 1.
|
|
WP Plugin Check (PHP 8.3)
WordPress Plugin Check failed. Created issue for tracking.
|
|
WP Plugin Check (PHP 8.3)
Process completed with exit code 1.
|
|
WP Plugin Check (PHP 8.3)
Could not parse version constraint ^9.*: Invalid version string "^9.*"
|
|
PHPMD (PHP 8.3)
Process completed with exit code 1.
|
|
PHPMD (PHP 8.3)
Could not parse version constraint ^9.*: Invalid version string "^9.*"
|
|
PHPCS (PHP 8.3)
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Security Scan (PHP 8.3)
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
PHPStan for WP (PHP 8.3)
Process completed with exit code 1.
|
|
PHPStan for WP (PHP 8.3)
Could not parse version constraint ^9.*: Invalid version string "^9.*"
|
|
Test WordPress 6.6 with PHP 8.1
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress nightly with PHP 8.4
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress nightly with PHP 8.1
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress 6.6 with PHP 8.2
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress latest with PHP 8.1
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress latest with PHP 8.5
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress 6.6 with PHP 8.3
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress 6.6 with PHP 8.5
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress latest with PHP 8.4
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress nightly with PHP 8.5
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress nightly with PHP 8.2
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress latest with PHP 8.2
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress 6.6 with PHP 8.4
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress latest with PHP 8.3
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Test WordPress nightly with PHP 8.3
Process completed with exit code 1.
|
|
Invalid composer.json
The composer.json file at './composer.json' does not validate; run 'composer validate' to check for errors
|
|
Psalm Static Analysis (PHP 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
WP VIP CS (PHP 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
WP Plugin Check (PHP 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
PHPMD (PHP 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
PHPCS (PHP 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Security Scan (PHP 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
PHPStan for WP (PHP 8.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress 6.6 with PHP 8.1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress nightly with PHP 8.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress nightly with PHP 8.1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress 6.6 with PHP 8.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress latest with PHP 8.1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress latest with PHP 8.5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress 6.6 with PHP 8.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress 6.6 with PHP 8.5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress latest with PHP 8.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress nightly with PHP 8.5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress nightly with PHP 8.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress latest with PHP 8.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress 6.6 with PHP 8.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress latest with PHP 8.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test WordPress nightly with PHP 8.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JasonEtco/create-an-issue@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|