Vercel deploy fails because of sentry's confusing instructions

[absolutegravitas]

See getsentry/sentry-cli#2137 (comment)

v1.run vercel deploy doesn't build and deploy onto vercel out of the box because of this confusing and inactionable message from sentry. I've attempted package updates on @sentry/nextjs to no effect.

Also general feedback for midday crew -- imo monitoring / logging env vars shouldnt be mandatory for example / template repos. Conditional checks should be added to test for null envs and bypass that feature in the v1 template.

[pontusab]

Thanks for your feedback! We have a nice change coming: #45 where you can init a bare project (nextjs + supabase) and a full example with sentry etc, or you can add services as you want with pre-made implementaitons + envs

[jaaneh]

For anyone looking at this in the future, the SENTRY_AUTH_TOKEN env var needs to be a token you create on this page. Once that's set up, re-deploy the app, and that should fix the "Invalid token" error.