Skip to content

chore(deps): bump next from 16.0.7 to 16.0.9 in /templates/nextjs-pages #3370

chore(deps): bump next from 16.0.7 to 16.0.9 in /templates/nextjs-pages

chore(deps): bump next from 16.0.7 to 16.0.9 in /templates/nextjs-pages #3370

Triggered via pull request December 12, 2025 00:48
Status Success
Total duration 1m 14s
Artifacts

examples.yml

on: pull_request
Matrix: examples
Matrix: patterns
Matrix: templates
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
examples (nextjs-pages): examples/nextjs-pages/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
templates (nextjs-pages): templates/nextjs-pages/pages/index.tsx#L9
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
templates (nextjs-pages): templates/nextjs-pages/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
examples (nextjs-app): examples/nextjs-app/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
templates (nextjs-app): templates/nextjs-app/eslint.config.mjs#L8
'__dirname' is assigned a value but never used
templates (nextjs-app): templates/nextjs-app/app/page.tsx#L9
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