Bump requests in /docs/adr/assets/ADR-003/examples/python #360
dependabot[bot]cicd-1-pull-request.yaml
on: push
Set CI/CD metadata
6s
Commit stage
/
Scan secrets
9s
Commit stage
/
Check file format
7s
Commit stage
/
Check Markdown format
4s
Commit stage
/
Check English usage
11s
Commit stage
/
Check TODO usage
4s
Commit stage
/
Count lines of code
7s
Commit stage
/
Scan dependencies
44s
Commit stage
/
Check for changes to event schema package compared to main branch
5s
Commit stage
/
Check event schemas have been regenerated
0s
Commit stage
/
Check event schema version has been updated
0s
Commit stage
/
Run terraform-docs
Commit stage
/
Lint Terraform
Test stage
/
Check generated dependencies
43s
Test stage
/
Linting
1m 36s
Test stage
/
Typecheck
1m 14s
Test stage
/
Test coverage
5s
Test stage
/
Perform static analysis
8s
Build stage
/
Build Docs
35s
Build stage
/
Artefact 1
5s
Build stage
/
Artefact n
5s
Acceptance stage
/
Contract test
5s
Acceptance stage
/
Security test
6s
Acceptance stage
/
UI test
5s
Acceptance stage
/
UI performance test
4s
Acceptance stage
/
Integration test
5s
Acceptance stage
/
Accessibility test
4s
Acceptance stage
/
Load test
5s
Acceptance stage
/
Environment tear down
5s
Annotations
9 warnings
|
Commit stage / Check TODO usage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
Commit stage / Check for changes to event schema package compared to main branch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
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/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 / Perform static analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/
|
|
Build stage / Build Docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/configure-pages@v5, actions/setup-node@v4, actions/upload-artifact@v4, ruby/setup-ruby@v1.180.1. 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 Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0CD7FaQAAAADPPMsqoOH5TIlA8ETkVjSFQ0hJMzBFREdFMDExOQBFZGdl
|
|
Build stage / Build Docs
Failed to restore: Cache service responded with 400
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
code-coverage-report
|
190 Bytes |
sha256:12c5459321deb6c66158ff61cbb746e7cd7fc43d0d9b28f1dccefab2da2d8c63
|
|
|
jekyll-docs-1.0.0
Expired
|
1.16 MB |
sha256:1285cd54e2c6020283e743b1aa08ebdce327cce0103b5e9acf3871a33c1983c5
|
|
|
lines-of-code-report.json.zip
Expired
|
959 Bytes |
sha256:38ba25dea1ce0000c60d53057bb70a0b7a14d417c7100a7df05b64ee640c5443
|
|
|
sbom-repository-report.json.zip
Expired
|
51.4 KB |
sha256:cd37b5ec556606872fdf8da0a74239926932702a8290af0f6d6ac7fd3f471cb8
|
|
|
unit-tests
|
39.8 KB |
sha256:49cc69a123805e4fd5b1f404717a7f55bc6f7a03e55f81de7dd465398bff5c75
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
19.4 KB |
sha256:5d28decc36d3d942d1e0c6f5198457007c9216cc03db93adfba9489ecbfec06a
|
|