Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 'curGa4' logical expression could make the dependencies of useMemo Hook (at line 280) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'curGa4' in its own useMemo() Hook

The 'baseGa4' logical expression could make the dependencies of useMemo Hook (at line 280) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'baseGa4' in its own useMemo() Hook

The 'curGsc' logical expression could make the dependencies of useMemo Hook (at line 276) change on every render. To fix this, wrap the initialization of 'curGsc' in its own useMemo() Hook

The 'curGsc' logical expression could make the dependencies of useMemo Hook (at line 272) change on every render. To fix this, wrap the initialization of 'curGsc' in its own useMemo() Hook

The 'baseGsc' logical expression could make the dependencies of useMemo Hook (at line 276) change on every render. To fix this, wrap the initialization of 'baseGsc' in its own useMemo() Hook

The 'baseGsc' logical expression could make the dependencies of useMemo Hook (at line 272) change on every render. To fix this, wrap the initialization of 'baseGsc' in its own useMemo() Hook

The 'links' logical expression could make the dependencies of useMemo Hook (at line 75) change on every render. To fix this, wrap the initialization of 'links' in its own useMemo() Hook

The 'links' logical expression could make the dependencies of useMemo Hook (at line 70) change on every render. To fix this, wrap the initialization of 'links' in its own useMemo() Hook

React Hook useCallback has unnecessary dependencies: 's.gscLinksUploadFailed' and 's.gscLinksUploadSuccess'. Either exclude them or remove the dependency array. Outer scope values like 's.gscLinksUploadFailed' aren't valid dependencies because mutating them doesn't re-render the component

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/