[landsman]

Next steps:

1. Get your DSN — Sentry project → Settings → Client Keys → copy the DSN
2. Create an Auth Token — Sentry → Settings → Auth Tokens → create token with scopes: project:releases, org:read
3. Note your org slug and project slug — visible in Sentry URLs: sentry.io/organizations//projects//

GitHub — Secrets

Settings → Secrets and variables → Actions → Secrets:

• SENTRY_AUTH_TOKEN — the token from step 2 above

GitHub — Variables

Settings → Secrets and variables → Actions → Variables:

• SENTRY_ORG — your org slug
• SENTRY_PROJECT — your project slug
• VITE_SENTRY_DSN — the DSN from step 1

Local .env

Fill in the blank you currently have:
VITE_SENTRY_DSN=https://xxxx@xxxx.ingest.sentry.io/xxxx

Supabase — Secrets (one-time manual set)

The deploy workflow will keep SENTRY_RELEASE up to date automatically going forward, but you may also want to set SENTRY_DSN as a Supabase secret if it isn't already:
supabase secrets set SENTRY_DSN=https://xxxx@xxxx.ingest.sentry.io/xxxx

---

Once those are in place, the next push to dev will create releases in Sentry for both the web app and Edge Functions automatically.

[github-actions]

Deno Outdated - Supabase

none

[github-actions]

Deno Outdated - Web

none