The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The hosted runner encountered an error while running your job. (Error Type: Disconnect).

The hosted runner: GitHub Actions 13 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The operation was canceled.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/