Skip to content

feat: enhance metadata and add sitemap and robots files for SEO optim… #4

feat: enhance metadata and add sitemap and robots files for SEO optim…

feat: enhance metadata and add sitemap and robots files for SEO optim… #4

Triggered via push March 16, 2026 15:09
Status Success
Total duration 39s
Artifacts

ci.yml

on: push
lint-and-build
35s
lint-and-build
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
lint-and-build
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 2nd, 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/
lint-and-build: src/app/video-remover/page.tsx#L66
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
lint-and-build: src/app/page.tsx#L62
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