Bump aws-actions/amazon-ecr-login from 2.0.1 to 2.0.2 #2040
cicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
7s
Commit stage
/
Scan secrets
6s
Commit stage
/
Check file format
8s
Commit stage
/
Check Python format
9s
Commit stage
/
Check Markdown format
5s
Commit stage
/
Check English usage
11s
Commit stage
/
Lint Terraform
14s
Commit stage
/
Count lines of code
7s
Commit stage
/
Scan dependencies
51s
Test stage
/
Unit tests
39s
Test stage
/
Contract tests
1m 17s
Test stage
/
Schema validation tests
1m 50s
Test stage
/
Integration tests
1m 45s
Test stage
/
Acceptance tests
1m 7s
Build stage
/
Artefact 1
4s
Build stage
/
Artefact 2
6s
Acceptance stage
/
Security test
3s
Acceptance stage
/
UI test
4s
Acceptance stage
/
UI performance test
5s
Acceptance stage
/
Load test
4s
Acceptance stage
/
Environment tear down
5s
Annotations
9 warnings
|
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 / 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 / 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 / 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:3ed6d0a9e73fb8370a49acf12cfaa6281a7cd308ae5dcb2f9a18e0f5cf0a2343
|
|
|
contract-test-results
Expired
|
107 KB |
sha256:8af680f2d1c139625d0daad83bdc93d4aa9ca8611c988456aed7661014e8d8bf
|
|
|
coverage-dependabot-github_actions-aws-actions-amazon-ecr-login-2-0-2-2040
Expired
|
658 KB |
sha256:aab78c57ff4052e12c58b35da9c8742438f4318bd140caa1611575d3c1c3e373
|
|
|
integration-test-results
Expired
|
108 KB |
sha256:76b3f6bdb7977dbc882392067f77e13c9c84c1641f401f2942a04d02c7d6eec0
|
|
|
lines-of-code-report.json.zip
Expired
|
864 Bytes |
sha256:105c372554019b9f3b537f7c655766565c8e7c0123d7ea5a5677edc5c4c3b8de
|
|
|
sbom-repository-report.json.zip
Expired
|
41.7 KB |
sha256:1f0ecce32c5f74416a9cc51228d297378904839b3c30bf47fac411eed5fe6302
|
|
|
schema-test-results
Expired
|
107 KB |
sha256:bf1aa2bb1c70e2b531665ac55b1dc0f1b28a6da0b7780f901dcf07912bb5ddc1
|
|
|
unit-test-results
Expired
|
183 KB |
sha256:cb138d44d479c64f44e1154830fe5efac88d2d22fb10f9c2d86a69f063cec7a1
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
2.37 KB |
sha256:8daaf131217570d8337c6d32dc047fc98618344439b7fc301f1aeade0c6207cd
|
|