The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

The action ruby/setup-ruby@v1 is not allowed in SocketDev/socket-patch because all actions must be pinned to a full-length commit SHA.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/