Skip to content

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

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

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

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

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
8s
Commit stage / Scan secrets
Commit stage  /  Check file format
5s
Commit stage / Check file format
Commit stage  /  Check Python format
8s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
11s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
17s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
49s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
5s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
46s
Test stage / Unit tests
Test stage  /  Contract tests
1m 9s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 9s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 11s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 6s
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 / 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/
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/

Artifacts

Produced during runtime
Name Size Digest
acceptance-test-results
113 KB
sha256:62d229a4c9dbec93ff63d00b83d173bee27cf977424926f976d0e60adee2e786
contract-test-results
117 KB
sha256:29a3c6c300379fae3da2856bf11e168c07d5c39ea2e3554df479ae510713aab6
integration-test-results
115 KB
sha256:3619da30230e761856850d812f0fcfdf6eeb781038bf3c2e2182e964bd3e0b10
lines-of-code-report.json.zip
858 Bytes
sha256:ac9dcb370e85e446de5c1ff565e501ae616de6488a1e17c12d70b1cdd3ffa31c
sbom-repository-report.json.zip
96.8 KB
sha256:a17f918580129d1f61e6b61c61eeed14ca3010a7a7dad72c32cf2d2049ea5720
schema-test-results
113 KB
sha256:c2b52d20a99f65757807b9ff6bc3d721c102ec6167e752ae23b26ffd0d53408c
unit-test-results
235 KB
sha256:4a9099db320900176b1e876e15ddd1e32ab0e5f9bd3f68dce5851add4d9dcdd7
vulnerabilities-repository-report.json.zip
4.02 KB
sha256:8f8064f4ff2ab93fc903c8840d824b4350e176970f716b2a2f5aecfd31c9ae84