Skip to content

Update signature tests for the protected-header "alg" requirement (#651) #693

Update signature tests for the protected-header "alg" requirement (#651)

Update signature tests for the protected-header "alg" requirement (#651) #693

Triggered via push June 6, 2026 17:41
Status Failure
Total duration 1d 0h 0m 24s
Artifacts

integrate.yml

on: push
0️⃣ Byte-level
6s
0️⃣ Byte-level
1️⃣ Syntax errors
19s
1️⃣ Syntax errors
3️⃣ Static Analysis
28s
3️⃣ Static Analysis
4️⃣ Coding Standards
32s
4️⃣ Coding Standards
6️⃣ Rector Checkstyle
1m 3s
6️⃣ Rector Checkstyle
7️⃣ Exported files
1d 0h
7️⃣ Exported files
Matrix: 2️⃣ Unit and functional tests
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 10 warnings
3️⃣ Static Analysis: src/Library/Console/EcKeyGeneratorCommand.php#L0
Ignored error pattern #^Property Jose\\Component\\Console\\EcKeyGeneratorCommand\:\:\$defaultDescription has no type specified\.$# in path /home/runner/work/jwt-framework/jwt-framework/src/Library/Console/EcKeyGeneratorCommand.php was not matched in reported errors.
3️⃣ Static Analysis: src/Library/Console/AddKeyIntoKeysetCommand.php#L0
Ignored error pattern #^Property Jose\\Component\\Console\\AddKeyIntoKeysetCommand\:\:\$defaultName has no type specified\.$# in path /home/runner/work/jwt-framework/jwt-framework/src/Library/Console/AddKeyIntoKeysetCommand.php was not matched in reported errors.
3️⃣ Static Analysis: src/Library/Console/AddKeyIntoKeysetCommand.php#L0
Ignored error pattern #^Property Jose\\Component\\Console\\AddKeyIntoKeysetCommand\:\:\$defaultDescription has no type specified\.$# in path /home/runner/work/jwt-framework/jwt-framework/src/Library/Console/AddKeyIntoKeysetCommand.php was not matched in reported errors.
3️⃣ Static Analysis: src/Experimental/KeyEncryption/Chacha20Poly1305.php#L51
Unreachable statement - code above always terminates.
3️⃣ Static Analysis: src/Experimental/KeyEncryption/Chacha20Poly1305.php#L47
Call to function is_string() with null will always evaluate to false.
3️⃣ Static Analysis: src/Bundle/Serializer/JWSSerializer.php#L29
Method Jose\Bundle\JoseFramework\Serializer\JWSSerializer::getSupportedTypes() return type has no value type specified in iterable type array.
3️⃣ Static Analysis: src/Bundle/Serializer/JWESerializer.php#L29
Method Jose\Bundle\JoseFramework\Serializer\JWESerializer::getSupportedTypes() return type has no value type specified in iterable type array.
3️⃣ Static Analysis: src/Bundle/DataCollector/JWECollector.php#L0
Ignored error pattern #^Cannot call method list\(\) on Jose\\Component\\Encryption\\Compression\\CompressionMethodManager\|null\.$# in path /home/runner/work/jwt-framework/jwt-framework/src/Bundle/DataCollector/JWECollector.php was not matched in reported errors.
2️⃣ Unit and functional tests (ubuntu-latest, 8.1, lowest)
Process completed with exit code 2.
2️⃣ Unit and functional tests (ubuntu-latest, 8.2, highest)
The strategy configuration was canceled because "unit_tests.ubuntu-latest_8_1_lowest" failed
2️⃣ Unit and functional tests (ubuntu-latest, 8.2, highest)
The operation was canceled.
4️⃣ Coding Standards
Process completed with exit code 2.
2️⃣ Unit and functional tests (ubuntu-latest, 8.1, highest)
The strategy configuration was canceled because "unit_tests.ubuntu-latest_8_1_lowest" failed
2️⃣ Unit and functional tests (ubuntu-latest, 8.1, highest)
The operation was canceled.
6️⃣ Rector Checkstyle
Process completed with exit code 2.
7️⃣ Exported files
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
0️⃣ Byte-level
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/
1️⃣ Syntax errors
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
2️⃣ Unit and functional tests (ubuntu-latest, 8.3, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
2️⃣ Unit and functional tests (ubuntu-latest, 8.3, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
3️⃣ Static Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
2️⃣ Unit and functional tests (ubuntu-latest, 8.2, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
2️⃣ Unit and functional tests (ubuntu-latest, 8.1, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
4️⃣ Coding Standards
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
2️⃣ Unit and functional tests (ubuntu-latest, 8.1, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/
6️⃣ Rector Checkstyle
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, 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/