Update dependency @astrojs/vercel to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/vercel (source)	^7.8.2 -> ^8.0.0

---

Release Notes

withastro/adapters (@​astrojs/vercel)

v8.0.0

Compare Source

Major Changes

• #​375 e7881f7 Thanks @​Princesseuh! - Updates internal code to works with Astro 5 changes to hybrid rendering. No changes are necessary to your project, apart from using Astro 5

• #​397 776a266 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

  Starting from this release, no breaking changes will be introduced unless absolutely necessary.

  To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

• #​377 b77f99c Thanks @​alexanderniebuhr! - Updates the adapter to use new IntegrationRouteData type

• #​451 f248546 Thanks @​ematipico! - Updates esbuild dependency to v0.24.0

• #​384 7d83f60 Thanks @​bluwy! - Removes deprecated speedInsights option in favor of Vercel's direct support: https://vercel.com/docs/speed-insights/quickstart

• #​392 3a49eb7 Thanks @​Princesseuh! - Updates internal code for Astro 5 changes. No changes is required to your project, apart from using Astro 5

Minor Changes

• #​424 3351348 Thanks @​ematipico! - Deprecates the entrypoints @astrojs/vercel/serverless and @astrojs/vercel/static. These will continue to work but are no longer documented and will be removed in a future version. We recommend updating to the @astrojs/vercel entrypoint as soon as you are able:

  -import vercel from "@​astrojs/vercel/static"
  +import vercel from "@​astrojs/vercel"

  -import vercel from "@​astrojs/vercel/serverless"
  +import vercel from "@​astrojs/vercel"

• #​447 7d9835f Thanks @​laymonage! - Add support for Node 22 on Vercel serverless

• #​385 bb725b7 Thanks @​florian-lefebvre! - Cleans up astro:env support

Patch Changes

• #​437 b725b49 Thanks @​ematipico! - Fixes a regression where the @astrojs/vercel single entry point for the adapter was causing some regressions in users projects.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
rawr51919-portfolio	❌ Failed (Inspect)			Jan 20, 2025 10:47pm

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/astro
npm error   astro@"^4.16.13" from the root project
npm error
npm error Could not resolve dependency:
npm error peer astro@"^5.0.0" from @astrojs/[email protected]
npm error node_modules/@astrojs/vercel
npm error   @astrojs/vercel@"^8.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-20T22_46_55_169Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-20T22_46_55_169Z-debug-0.log