Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU and memory utilization are below 50% of available resources; it might be worth using a different resource class if possible.

Peak CPU utilization: 1.31 cores (32.81% of 4.00) at 5s Peak memory utilization: 8.0 GB (46.61% of 17 GB) at 15s

Peak CPU utilization: 0.58 cores (3.64% of 16.00) at 10s Peak memory utilization: 267 MB (0.53% of 50 GB) at 17s

Peak CPU utilization: 0.49 cores (12.17% of 4.00) at 3s Peak memory utilization: 6.7 GB (39.15% of 17 GB) at 8s

Peak CPU utilization: 0.77 cores (4.82% of 16.00) at 9s Peak memory utilization: 243 MB (0.48% of 50 GB) at 14s

Peak CPU utilization: 0.76 cores (19.11% of 4.00) at 10s Peak memory utilization: 7.0 GB (40.53% of 17 GB) at 8s

Peak CPU utilization: 0.71 cores (17.63% of 4.00) at 8s Peak memory utilization: 8.9 GB (51.95% of 17 GB) at 9s

Peak CPU utilization: 3.69 cores (92.21% of 4.00) at 1s Peak memory utilization: 6.7 GB (38.93% of 17 GB) at 41s

Peak CPU utilization: 0.64 cores (4.03% of 16.00) at 10s Peak memory utilization: 291 MB (0.58% of 50 GB) at 17s

Peak CPU utilization: 0.76 cores (4.76% of 16.00) at 9s Peak memory utilization: 284 MB (0.56% of 50 GB) at 16s

Peak CPU utilization: 0.98 cores (24.52% of 4.00) at 9s Peak memory utilization: 7.7 GB (44.91% of 17 GB) at 11s

Peak CPU utilization: 1.11 cores (27.71% of 4.00) at 13s Peak memory utilization: 6.9 GB (40.40% of 17 GB) at 10s

Peak CPU utilization: 0.69 cores (4.32% of 16.00) at 11s Peak memory utilization: 333 MB (0.66% of 50 GB) at 21s

Peak CPU utilization: 0.49 cores (3.03% of 16.00) at 11s Peak memory utilization: 296 MB (0.59% of 50 GB) at 20s

Peak CPU utilization: 0.64 cores (3.99% of 16.00) at 11s Peak memory utilization: 248 MB (0.49% of 50 GB) at 20s

Peak CPU utilization: 1.56 cores (38.98% of 4.00) at 28s Peak memory utilization: 6.7 GB (38.76% of 17 GB) at 32s

Peak CPU utilization: 0.80 cores (19.98% of 4.00) at 10s Peak memory utilization: 6.7 GB (39.07% of 17 GB) at 12s