Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, astral-sh/setup-uv@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, astral-sh/setup-uv@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

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

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

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

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

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

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

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

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

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