Skip to content

devops: upgrading tasks #284

devops: upgrading tasks

devops: upgrading tasks #284

Triggered via pull request April 17, 2026 17:32
Status Failure
Total duration 28s
Artifacts 2

pr-check.yml

on: pull_request
highflame-commit-check
4s
highflame-commit-check
highflame-lint-check
19s
highflame-lint-check
highflame-trivy-scan
23s
highflame-trivy-scan
highflame-build-check
11s
highflame-build-check
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
highflame-trivy-scan
Process completed with exit code 1.
highflame-trivy-scan
Process completed with exit code 1.
highflame-build-check
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. 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/
highflame-build-check
Cache paths are empty. Please check the previous logs and make sure that the python version is specified
highflame-build-check
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
highflame-trivy-scan
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. 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/

Artifacts

Produced during runtime
Name Size Digest
lint-report Expired
148 Bytes
sha256:04407801ae1440e790baa31338103d9015f9dfc7a1d07adecae978acb59916fd
trivy-scan-result Expired
1009 Bytes
sha256:7bcb83ffebae87edab82da37231788e0fb3837a75b9445e0ecd1e7565e7b8c93