Skip to content

Move from @vercel/postgres to postgres (provider-agnostic) #597

Move from @vercel/postgres to postgres (provider-agnostic)

Move from @vercel/postgres to postgres (provider-agnostic) #597

Triggered via pull request January 27, 2025 13:58
@leerobleerob
synchronize #989
postgres
Status Failure
Total duration 29s
Artifacts

test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
test
Process completed with exit code 1.
test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test: basics/assets-metadata-css-starter/pages/index.js#L60
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
test: basics/basics-final/pages/api/hello.js#L1
Assign arrow function to a variable before exporting as module default
test: basics/demo/pages/api/hello.js#L1
Assign arrow function to a variable before exporting as module default
test: basics/learn-starter/pages/index.js#L59
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
test: basics/navigate-between-pages-starter/pages/index.js#L59
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
test: basics/typescript-final/pages/api/hello.ts#L3
Assign arrow function to a variable before exporting as module default
test: seo/demo/pages/index.js#L23
A font-display parameter is missing (adding `&display=optional` is recommended). See: https://nextjs.org/docs/messages/google-font-display
test: seo/demo/pages/index.js#L23
Custom fonts not added in `pages/_document.js` will only load for a single page. This is discouraged. See: https://nextjs.org/docs/messages/no-page-custom-font
test: seo/pages/index.js#L25
A font-display parameter is missing (adding `&display=optional` is recommended). See: https://nextjs.org/docs/messages/google-font-display
test: seo/pages/index.js#L25
Custom fonts not added in `pages/_document.js` will only load for a single page. This is discouraged. See: https://nextjs.org/docs/messages/no-page-custom-font