Edge runtime regions not working when integrating with Sentry

[Cow258]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.3.0: Thu Jan  5 20:48:54 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T6000
Binaries:
  Node: 18.14.0
  npm: 9.3.1
  Yarn: 1.22.19
  pnpm: 8.2.0
Relevant packages:
  next: 13.3.1-canary.6
  eslint-config-next: 13.3.0
  react: 18.2.0
  react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue

https://github.com/Cow258/edge-bug-demo

To Reproduce

1. Deploy to Vercel
2. Goto https://****.vercel/api/hello
3. Open DevTool for the response headers
4. You will find the region is different from 'sin1'

https://edge-bug-demo.vercel.app/api/hello

Describe the Bug

I set the regions to ['sin1'], but it still global after deployed to Vercel and integrating with Sentry

export const config = {
  runtime: 'edge',
  regions: ['sin1'],
}

Expected Behavior

The region should be as same as the config when integrating with Sentry

Which browser are you using? (if relevant)

Chrome 111.0.5563.146

How are you deploying your application? (if relevant)

Vercel (https://edge-bug-demo.vercel.app)

[Cow258]

Sentry are tracking things related to it in this GH issue: getsentry/sentry-javascript#7450, so closing this issue since it's duplicate.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.