Skip to content

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

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

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

Triggered via pull request April 29, 2026 09:12
Status Failure
Total duration 2m 26s
Artifacts 8

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
7s
Set CI/CD metadata
Commit stage  /  Scan secrets
7s
Commit stage / Scan secrets
Commit stage  /  Check file format
5s
Commit stage / Check file format
Commit stage  /  Check Python format
11s
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
14s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
11s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
48s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
3s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
42s
Test stage / Unit tests
Test stage  /  Contract tests
1m 19s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 20s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 18s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 12s
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

1 error and 5 warnings
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 / 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 / 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 / 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:0fdb198b09672d5eab04f458af3ec43c09629706165cf97efed13a7765ee2088
contract-test-results
117 KB
sha256:d6a40fa501648d33253c50addfa896e5e2440f936e16faa97b174522943aeab4
integration-test-results
114 KB
sha256:96107ea50944c5707df4364f97fdbf1837bafb7f1902e6b9b5fda168d83a4efa
lines-of-code-report.json.zip
858 Bytes
sha256:5f241740d3494c1db817ac0db84a5de164a8f50dfa1d95985ea1fe4d4c5bab4b
sbom-repository-report.json.zip
96.8 KB
sha256:a2d01c08333a4cd99381421fef5c75c7e9b3aac510a6a0c28bb080727b891097
schema-test-results
113 KB
sha256:1220540599328569a8003667b3aa70ac9b1570d253a9b538e8dae0a431f1d7bf
unit-test-results
236 KB
sha256:3b5defcc9a83ce6acc6038171ff34b91f9952b74a09b454aeb8c6380ed3d99e0
vulnerabilities-repository-report.json.zip
4.03 KB
sha256:cf9352c51eb94d6194425fce0e793ce0b322b114383946b2a813c62031899c42