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

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, dopplerhq/secrets-fetch-action@cd2efbf9a404504316435873eff298b82f7e0562, pnpm/action-setup@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/

Expected "import" statement instead of "require" call

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

React Hook "useEffect" is called in function "Anonymous" that is neither a React function component nor a custom React Hook function. React component names must start with an uppercase letter. React Hook names must start with the word "use".

Avoid multiple positional arguments. Prefer an options object instead, e.g., fn(options) or fn(arg, options).

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, dopplerhq/secrets-fetch-action@cd2efbf9a404504316435873eff298b82f7e0562, pnpm/action-setup@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/