Skip to content

sdk.functions

sdk.functions #122

Re-run triggered March 12, 2026 14:48
Status Success
Total duration 43m 5s
Artifacts

sdk.functions.yml

on: schedule
Matrix: pod_lib_lint / pod-lib-lint
spm-unit  /  spm-package-resolved
1m 19s
spm-unit / spm-package-resolved
Matrix: spm-integration
Matrix: functions-cron-only / cron-job
Matrix: spm-unit / spm
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
pod_lib_lint / pod-lib-lint (macos-26, Xcode_26.2, iOS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08, ruby/setup-ruby@354a1ad156761f5ee2b7b13fa8e09943a5e8d252. 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/
pod_lib_lint / pod-lib-lint (macos-26, Xcode_26.2, iOS)
Attempt 1 failed. Reason: Timeout of 1200000ms hit
functions-cron-only / cron-job (macos, --use-static-frameworks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08, ruby/setup-ruby@354a1ad156761f5ee2b7b13fa8e09943a5e8d252. 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/
functions-cron-only / cron-job (tvos, --use-static-frameworks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08, ruby/setup-ruby@354a1ad156761f5ee2b7b13fa8e09943a5e8d252. 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/
functions-cron-only / cron-job (ios, --use-static-frameworks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08, ruby/setup-ruby@354a1ad156761f5ee2b7b13fa8e09943a5e8d252. 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/