Skip to content

[GPCAPIM-305]: Create common Pydantic FHIR types #1769

[GPCAPIM-305]: Create common Pydantic FHIR types

[GPCAPIM-305]: Create common Pydantic FHIR types #1769

Triggered via pull request March 12, 2026 10:13
Status Failure
Total duration 1m 27s
Artifacts 3

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
5s
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
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
13s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
16s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
7s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
46s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
3s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
19s
Test stage / Unit tests
Test stage  /  Contract tests
26s
Test stage / Contract tests
Test stage  /  Schema validation tests
23s
Test stage / Schema validation tests
Test stage  /  Integration tests
21s
Test stage / Integration tests
Test stage  /  Acceptance tests
26s
Test stage / Acceptance tests
Test stage  /  Merge test coverage
Test stage / Merge test coverage
Test stage  /  SonarCloud Analysis
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

10 errors and 13 warnings
Test stage / Unit tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/unit-tests.xml'
Test stage / Unit tests
Process completed with exit code 2.
Test stage / Integration tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/integration-tests.xml'
Test stage / Integration tests
Process completed with exit code 2.
Test stage / Schema validation tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/schema-tests.xml'
Test stage / Schema validation tests
Process completed with exit code 2.
Test stage / Contract tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/contract-tests.xml'
Test stage / Contract tests
Process completed with exit code 2.
Test stage / Acceptance tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/acceptance-tests.xml'
Test stage / Acceptance tests
Process completed with exit code 2.
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Commit stage / Check Python format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 / Unit tests
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.
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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.
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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.
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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.
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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size Digest
lines-of-code-report.json.zip Expired
867 Bytes
sha256:4ef34f3a8b7a33cd375e60fb80e43cf8283fdae3bc681669e297fda36bb210d1
sbom-repository-report.json.zip Expired
28.1 KB
sha256:9024ffaa24c881c50eafd10995c7c3e900d34c2432bca9f48e98ca141ff1ef1d
vulnerabilities-repository-report.json.zip Expired
2.38 KB
sha256:8543d317ea19399c663259c30870ebfa3b0e3ca4cc7ae71b610c686111f06254