Bump geekyeggo/delete-artifact from 5 to 6 #3991
dependabot[bot]cicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
7s
Commit stage
/
Scan secrets
11s
Commit stage
/
Check file format
6s
Commit stage
/
Check Markdown format
6s
Commit stage
/
Check English usage
10s
Commit stage
/
Lint Terraform
1m 28s
Commit stage
/
Count lines of code
7s
Commit stage
/
Scan dependencies
42s
Commit stage
/
Lint, style and type check code
49s
Test stage
/
Validate Campaign Config (All Envs)
45s
Acceptance stage (main only)
/
...
/
run-vita-int-tests
Acceptance stage (main only)
/
test-contract
Acceptance stage (main only)
/
test-e2e
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 / 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/
|
|
Commit stage / Lint, style and type check code:
src/utils/auth/get-jwt-token.ts#L10
Object.fromEntries() is not supported in Safari 11, iOS Safari 11.0-11.2, Chrome 66
|
|
Commit stage / Lint, style and type check code:
src/utils/auth/get-jwt-token.ts#L9
Object.fromEntries() is not supported in Safari 11, iOS Safari 11.0-11.2, Chrome 66
|
|
Commit stage / Lint, style and type check code:
src/utils/auth/generate-auth-payload.ts#L23
Crypto.randomUUID() is not supported in Safari 11, iOS Safari 11.0-11.2, Chrome 66
|
|
Commit stage / Lint, style and type check code:
src/utils/auth/apim/fetch-apim-access-token.ts#L72
Crypto.randomUUID() is not supported in Safari 11, iOS Safari 11.0-11.2, Chrome 66
|
|
Commit stage / Lint, style and type check code:
src/app/api/sso/route.ts#L20
Crypto.randomUUID() is not supported in Safari 11, iOS Safari 11.0-11.2, Chrome 66
|
|
Commit stage / Lint Terraform
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/setup-terraform@v3. 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/
|
|
Build stage / Build and upload artefacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@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 | |
|---|---|---|---|
|
code-coverage-report
Expired
|
24.4 KB |
sha256:4c5cc11a09a8760e746e2945e221d6bcbc01e05732836f296dffbfa01e37ec74
|
|
|
lines-of-code-report.json.zip
Expired
|
889 Bytes |
sha256:60cccabbc01be5d621eef4225009c169ff3f5fc30dd9f76e8531bc747768077e
|
|
|
sbom-repository-report.json.zip
Expired
|
110 KB |
sha256:7620aed2e64eb406183024f4335f7802d06ccd73b36b8ec9ea092bfbdcf81ebd
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
3.2 KB |
sha256:83bd1c3068b401ad3abab08ab3aa6a798117eeb76c47d31d63d82065a003812f
|
|