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/

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Possibly undefined array key `string('error')` accessed on `array<string, mixed>`. >Key `string('error')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('error') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Possibly undefined array key `string('error')` accessed on `array<string, mixed>`. >Key `string('error')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('error') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('message')` accessed on `array<array-key, mixed>`. >Key `string('message')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('message') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('error')` accessed on `array<array-key, mixed>`. >Key `string('error')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('error') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('X-Rate-Limit-Remaining')` accessed on `array<string, list<string>>`. >Key `string('X-Rate-Limit-Remaining')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('X-Rate-Limit-Remaining') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('X-Request-ID')` accessed on `array<string, list<string>>`. >Key `string('X-Request-ID')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('X-Request-ID') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('Content-Length')` accessed on `array<string, list<string>>`. >Key `string('Content-Length')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('Content-Length') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('Content-Type')` accessed on `array<string, list<string>>`. >Key `string('Content-Type')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('Content-Type') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

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/

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Possibly undefined array key `string('error')` accessed on `array<string, mixed>`. >Key `string('error')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('error') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Possibly undefined array key `string('error')` accessed on `array<string, mixed>`. >Key `string('error')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('error') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('message')` accessed on `array<array-key, mixed>`. >Key `string('message')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('message') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('error')` accessed on `array<array-key, mixed>`. >Key `string('error')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('error') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('X-Rate-Limit-Remaining')` accessed on `array<string, list<string>>`. >Key `string('X-Rate-Limit-Remaining')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('X-Rate-Limit-Remaining') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('X-Request-ID')` accessed on `array<string, list<string>>`. >Key `string('X-Request-ID')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('X-Request-ID') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.

Possibly undefined array key `string('Content-Length')` accessed on `array<string, list<string>>`. >Key `string('Content-Length')` might not exist. The analysis indicates this specific key might not be set when this access occurs. Help: Ensure the key string('Content-Length') is always set before accessing it, or use `isset()` or the null coalesce operator (`??`) to handle potential missing keys.