Skip to content

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

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

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

Triggered via pull request April 29, 2026 10:32
Status Failure
Total duration 2m 21s
Artifacts 8

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
8s
Commit stage / Scan secrets
Commit stage  /  Check file format
9s
Commit stage / Check file format
Commit stage  /  Check Python format
9s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
11s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
19s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
10s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
42s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
5s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
45s
Test stage / Unit tests
Test stage  /  Contract tests
1m 17s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 17s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 11s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 5s
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 / 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 / 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 / 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:5389e591460d4ce408377f3815245ffe5796067a40a82901c49b640635ed7323
contract-test-results
117 KB
sha256:43510500f566b04ffe4ff212d9b506bd72e8beeececbfb39241bd3316d0fe90b
integration-test-results
115 KB
sha256:3873dec9cf7a27d6f8242fc46561467dceffb62dbcf8d6547e856dbbe3bd4aba
lines-of-code-report.json.zip
854 Bytes
sha256:69a93a439dc776ebb3321988c5a051a2d89adff0af61b10f236613ee578e4b28
sbom-repository-report.json.zip
96.8 KB
sha256:c916ee2ba944b8e9d6b77ae97830e13e2e47f02e7e7bafca1feec2de26cc8eef
schema-test-results
113 KB
sha256:5f96d03b0290b2cd69b400aa909e9600d309d44ac5a87497e920c42f38f8d374
unit-test-results
236 KB
sha256:d363cc02cbf8b35ed0fe356da496933b904a189615e32137a485a0dd8a3f6abc
vulnerabilities-repository-report.json.zip
4.03 KB
sha256:8afeb203771cbc04c4f92934f66bf68a0f35b7cc397abbf27d39a7686dc6d64c