Skip to content

Bump pyjwt from 2.10.1 to 2.12.0 #3263

Bump pyjwt from 2.10.1 to 2.12.0

Bump pyjwt from 2.10.1 to 2.12.0 #3263

Triggered via pull request March 20, 2026 09:51
Status Success
Total duration 6m 38s
Artifacts 6

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
10s
Commit stage / Scan secrets
Commit stage  /  Check file format
10s
Commit stage / Check file format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
11s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
5s
Commit stage / Lint Terraform
Commit stage  /  Checkov Terraform
33s
Commit stage / Checkov Terraform
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
52s
Commit stage / Scan dependencies
Commit stage  /  OWASP Dependency Scan
32s
Commit stage / OWASP Dependency Scan
Commit stage  /  Check for dead code
35s
Commit stage / Check for dead code
Test stage  /  Linting
44s
Test stage / Linting
Test stage  /  Unit tests
59s
Test stage / Unit tests
Test stage  /  Perform static analysis
6s
Test stage / Perform static analysis
Build stage  /  Lambda Artefact
1m 34s
Build stage / Lambda Artefact
Acceptance stage  /  Environment set up
3s
Acceptance stage / Environment set up
Acceptance stage  /  Contract test
4s
Acceptance stage / Contract test
Acceptance stage  /  Security test
4s
Acceptance stage / Security test
Acceptance stage  /  UI test
4s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
6s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
2m 29s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
4s
Acceptance stage / Accessibility test
Acceptance stage  /  Load test
5s
Acceptance stage / Load test
Acceptance stage  /  Environment tear down
7s
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

5 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 / OWASP Dependency Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/codeql-action/upload-sarif@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/
Commit stage / OWASP Dependency Scan
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
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/
Acceptance stage / Integration test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: phoenix-actions/test-reporting@v15. 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
coverage.xml
7.18 KB
sha256:3ec9a0de9af132823ed5fba60fc18dfc24e4490cc1fedee91e80efaa0ec70f31
integration-test-results
2.35 KB
sha256:9f674c1f047d31ffaef98cb5e7bd43506578f8e614ac7502300801ca06e8a370
lambda
18.9 MB
sha256:9606f2680559b64a8a4b77364c192830cdfc8854b1c00aa025f0f80bb1a2df9e
lines-of-code-report-.json.zip Expired
846 Bytes
sha256:d66e3485d865eb79acf7ed26621f6a0e32ce17b9139562ff0a28f1eb0558f01d
sbom-repository-report.json.zip Expired
58.7 KB
sha256:0d57e16bb126a646bbf362587ce437b24755f506983932f647687b047c116ca2
vulnerabilities-repository-report-.json.zip Expired
3.99 KB
sha256:2cc450796d1a6461869e2aec3b6e40d8f7b0cd3e83a4a663ddfee2d04882d26f