Bump aws-actions/configure-aws-credentials from 4c2b9cc816c86555b61460789ac95da17d7e829b to 33712a4c0caf8975a042ff72b30d5ae67cb67255 #1685
dependabot[bot]cicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
5s
Commit stage
/
Scan secrets
11s
Commit stage
/
Check file format
7s
Commit stage
/
Check Python format
8s
Commit stage
/
Check Markdown format
4s
Commit stage
/
Check English usage
11s
Commit stage
/
Lint Terraform
15s
Commit stage
/
Count lines of code
8s
Commit stage
/
Scan dependencies
49s
Test stage
/
Unit tests
39s
Test stage
/
Contract tests
1m 5s
Test stage
/
Schema validation tests
1m 19s
Test stage
/
Integration tests
53s
Test stage
/
Acceptance tests
58s
Build stage
/
Artefact 1
5s
Build stage
/
Artefact 2
3s
Acceptance stage
/
Security test
4s
Acceptance stage
/
UI test
4s
Acceptance stage
/
UI performance test
7s
Acceptance stage
/
Load test
6s
Acceptance stage
/
Environment tear down
6s
Annotations
9 warnings
|
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 / 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 / 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 / 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 / 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 / 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 / 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 / Merge test coverage
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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
acceptance-test-results
Expired
|
107 KB |
sha256:8c0811572c3ef0032657f13306fbd9c51704b383cae3db9b6fb39b30d5642f52
|
|
|
contract-test-results
Expired
|
107 KB |
sha256:2a7f9366931bcdc680fc802eeb9dfe5663b48633e2e7284164761fdee6a12d3d
|
|
|
coverage-dependabot-github_actions-aws-actions-configure-aws-credentials-33712a4c0caf8975a042ff72b30d5ae67cb67255-1685
Expired
|
659 KB |
sha256:fb396f39db000f670b00e5badd30439b3510e45c8d5aa87eb8f9aa353b008b20
|
|
|
integration-test-results
Expired
|
108 KB |
sha256:1545b4869d80045d9b6bd1b7ec6d21353a19db00b377ce2f352d1430bd513890
|
|
|
lines-of-code-report.json.zip
Expired
|
865 Bytes |
sha256:50f7bb29d87e74a4ebf5dad42e28150152144c871dbfa149a3e1276290f1af7e
|
|
|
sbom-repository-report.json.zip
Expired
|
42.1 KB |
sha256:32a546117b9d969951b1c64e6bec2392817bd5c20823da75d6f9cf16dcb57c2a
|
|
|
schema-test-results
Expired
|
108 KB |
sha256:e326f10954b7a9a2f7f605cc3d818e0280460be46b380d9cb4fceb0a33c2ce8c
|
|
|
unit-test-results
Expired
|
184 KB |
sha256:c32d2fd016c5fccae0b4d1673da070eb401236602d4df7803b6835e0a078533a
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
2.38 KB |
sha256:6598ea0ff54f94fdddeff1997037a202626d2812deb27bf9076f72fb5fdd5d81
|
|