Skip to content

[GPCAPIM-419]-[Required Missing Header Not Rejected (Content-Type)]-[RP] #2970

[GPCAPIM-419]-[Required Missing Header Not Rejected (Content-Type)]-[RP]

[GPCAPIM-419]-[Required Missing Header Not Rejected (Content-Type)]-[RP] #2970

Triggered via pull request April 29, 2026 13:46
Status Failure
Total duration 2m 28s
Artifacts 8

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
10s
Commit stage / Scan secrets
Commit stage  /  Check file format
7s
Commit stage / Check file format
Commit stage  /  Check Python format
8s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
12s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
16s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
10s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
51s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
6s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
48s
Test stage / Unit tests
Test stage  /  Contract tests
1m 9s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 11s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 16s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 10s
Test stage / Acceptance tests
Test stage  /  Merge test coverage
0s
Test stage / Merge test coverage
Test stage  /  SonarCloud Analysis
0s
Test stage / SonarCloud Analysis
Build stage  /  Artefact 1
Build stage / Artefact 1
Build stage  /  Artefact 2
Build stage / Artefact 2
Acceptance stage  /  Environment set up
Acceptance stage / Environment set up
Acceptance stage  /  Load test
Acceptance stage / Load test
Acceptance stage  /  Security test
Acceptance stage / Security test
Acceptance stage  /  UI performance test
Acceptance stage / UI performance test
Acceptance stage  /  UI test
Acceptance stage / UI test
Acceptance stage  /  Environment tear down
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
Test stage / Unit tests
Process completed with exit code 2.
Test stage / Schema validation tests
Process completed with exit code 2.
Test stage / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Test stage / Contract tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Test stage / Acceptance tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Test stage / Schema validation tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Test stage / Integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
acceptance-test-results
113 KB
sha256:f6d3768b50a8a4106b2469dfafe3b0d9fffacbee1c56207e8f64d58759776510
contract-test-results
117 KB
sha256:92d5340342f658eb8bfbb70f02b5239ec7641ea070fbadd402113eee85fefbed
integration-test-results
115 KB
sha256:7f4439a5299a6f0e16fbfeb3035b46ed7cd5aa2b64da54148bb501f00423ac34
lines-of-code-report.json.zip
862 Bytes
sha256:f1d955947d8e599a6d91566c8093de0963cf19f3677f1c565777f5790cd63951
sbom-repository-report.json.zip
96.8 KB
sha256:25a87b607bfa3c39ac7495aee79a50c447ff57558bb760a17e6aecb01de19b61
schema-test-results
113 KB
sha256:91a17992f7e0d5bf540dad858d60e7f41daaf35e3b55f10cb56a178681b2c9fa
unit-test-results
235 KB
sha256:89353c285dc634785c762affc3f9c6705274b29b604ef06651e278ee047634ee
vulnerabilities-repository-report.json.zip
4.03 KB
sha256:70be7d550eb030bfb516b7f90439217c0ab327201071cc296dc32a662231299d