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

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

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

The import of ‘guard’ from module ‘Control.Monad’ is redundant

Pattern match(es) are non-exhaustive

This binding for ‘err’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘sockAddr’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

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

Pattern match(es) are non-exhaustive

In the use of ‘head’

In the use of ‘tail’

In the use of ‘head’

In the use of ‘tail’

In the use of ‘head’

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

The import of ‘Data.List’ is redundant

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

The import of ‘guard’ from module ‘Control.Monad’ is redundant

Pattern match(es) are non-exhaustive

This binding for ‘err’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘sockAddr’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

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

This binding for ‘sock’ shadows the existing binding

Pattern match(es) are non-exhaustive

In the use of ‘head’

In the use of ‘tail’

In the use of ‘head’

In the use of ‘tail’

In the use of ‘head’

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

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

The import of ‘guard’ from module ‘Control.Monad’ is redundant

This binding for ‘err’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘sockAddr’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

Pattern match(es) are non-exhaustive

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

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

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable

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

The import of ‘guard’ from module ‘Control.Monad’ is redundant

Pattern match(es) are non-exhaustive

This binding for ‘err’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘sockAddr’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

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

The import of ‘guard’ from module ‘Control.Monad’ is redundant

Pattern match(es) are non-exhaustive

This binding for ‘err’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘act’ shadows the existing binding

This binding for ‘sockAddr’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding

This binding for ‘sock’ shadows the existing binding