Skip to content

fix(bundler-plugins): Skip default commit association on Vercel builds that --auto can't resolve - #26320

Merged
betegon merged 4 commits into
developfrom
fix/bundler-plugins-skip-auto-commits-vercel-preview
Nov 16, 2026
Merged

betegon merged 4 commits into
developfrom
fix/bundler-plugins-skip-auto-commits-vercel-preview

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Why: With no setCommits set, non-production Vercel builds fall back to { auto: true }. Vercel's own builders have no origin remote and no other CI variables, and the CLI only reads VERCEL_GIT_* on production builds, so that set-commits --auto call always fails there. The plugin swallows the error, but the new CLI reports each failure to its own telemetry, where Vercel builds make up about 40% of the "no repository for --auto" errors. Those builds now skip commit association.

The skip only happens when --auto has nothing to read: no origin remote and none of the CI repository variables the CLI falls back to (GITHUB_REPOSITORY, CI_PROJECT_PATH, ...). Builds that have either, such as vercel build / vercel deploy --prebuilt in GitHub Actions, keep --auto exactly as before, so a build that associated commits today still does. The VERCEL_GIT_* branch stays production-only, as the existing comment says, and production detection now uses getVercelEnv() (VERCEL_TARGET_ENV, falling back to VERCEL_ENV), the same check deploy detection below it uses. An explicit user setCommits still wins.

Before / after: No user has to change anything. The only builds that behave differently are ones where --auto was already failing quietly.

Setup Before (CLI 0.49) After Action needed
Vercel production (VERCEL_TARGET_ENV=production) Commits from VERCEL_GIT_* Same None
Vercel production with only VERCEL_ENV=production --auto fails on Vercel's builders, so no commits Commits from VERCEL_GIT_* None (this gets better)
Vercel preview / custom env on Vercel's builders --auto fails quietly, no commits Skipped, no commits (no failing call) None, unless you want preview commits (see below)
Vercel preview with a git remote or CI variables (vercel build / --prebuilt in GitHub Actions) --auto works Same None
Not on Vercel, with a git checkout --auto works Same None
Not on Vercel, no .git (Docker), CI variables set --auto uses CI variables Same None
Not on Vercel, no .git, no CI variables --auto fails quietly Same (this PR only touches Vercel) Pass the commit in
release.setCommits set explicitly User config wins Same None

Preview commits stay opt-in, because a preview's previous commit is the PR's stem commit and Sentry would notify the authors of unrelated PRs. Users who want them anyway can set:

release: {
  setCommits: {
    repo: `${process.env.VERCEL_GIT_REPO_OWNER}/${process.env.VERCEL_GIT_REPO_SLUG}`,
    commit: process.env.VERCEL_GIT_COMMIT_SHA,
  },
}

Unsure about: The CI variable list copies the CLI's --auto fallback (packages/cli/src/lib/ci.ts in getsentry/toolkit), so it has to stay in sync when that list grows. This adds at most one git call per build, and only on non-production Vercel builds.

via @betegon.

--

View Session [Sentry]

…on Vercel builds

On Vercel builds that are not production, the default `setCommits` fell
through to `{ auto: true }`. Vercel builds have no `.git`, so the CLI call
always failed and was swallowed. Skip commit association there instead,
which is what the existing production-only comment intended.

Production detection now uses `getVercelEnv()`, the same as deploy
detection.

Co-Authored-By: bete <28983162+betegon@users.noreply.github.com>
@github-actions

github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

size-limit report 📦

Compared: 43297d1 (PR test merge using develop at f49009b)

Against: f49009b (develop) · base run #65866

✅ Baseline matches: this diff contains only this PR's changes.

Path Size % Change Change
@sentry/browser 30.04 kB - -
@sentry/browser - with treeshaking flags 28.23 kB - -
@sentry/browser - with treeshaking flags tracing without tracing 28.12 kB - -
@sentry/browser (incl. Tracing) 52.2 kB - -
@sentry/browser (incl. Tracing + Span Streaming) 52.2 kB - -
@sentry/browser (incl. Tracing, Profiling) 55.17 kB - -
@sentry/browser (incl. Tracing, Replay) 92.73 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 81.52 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 97.08 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 110.51 kB - -
@sentry/browser (incl. Feedback) 47.66 kB - -
@sentry/browser (incl. sendFeedback) 30.62 kB - -
@sentry/browser (incl. FeedbackAsync) 35.62 kB - -
@sentry/browser (incl. Metrics) 31.36 kB - -
@sentry/browser (incl. Logs) 31.64 kB - -
@sentry/browser (incl. Metrics & Logs) 32.3 kB - -
@sentry/react 32.04 kB - -
@sentry/react (incl. Tracing) 54.86 kB - -
@sentry/vue 38.21 kB - -
@sentry/vue (incl. Tracing) 55.14 kB - -
@sentry/svelte 30.05 kB - -
@sentry/remix (Remix 3 client bundle) 57.96 kB - -
CDN Bundle 31.79 kB - -
CDN Bundle (incl. Tracing) 52.58 kB - -
CDN Bundle (incl. Logs, Metrics) 34.58 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 55.14 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 75.61 kB - -
CDN Bundle (incl. Tracing, Replay) 90.63 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 93.25 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 96 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 98.6 kB - -
CDN Bundle - uncompressed 92.69 kB - -
CDN Bundle (incl. Tracing) - uncompressed 155.13 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 101.03 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 162.76 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 231.11 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 275.27 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 282.9 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 287.07 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 294.69 kB - -
@sentry/nextjs (client) 58.23 kB - -
@sentry/sveltekit (client) 53.26 kB - -
@sentry/core/server 44.53 kB - -
@sentry/core/browser 13.99 kB - -
@sentry/node 149.35 kB -0.01% -4 B 🔽
@sentry/node/import (ESM hook with diagnostics-channel injection) 83.18 kB - -
@sentry/node - without tracing 88.27 kB -0.01% -4 B 🔽
@sentry/node - without channel injection 138.45 kB -0.01% -2 B 🔽
@sentry/aws-serverless 97.19 kB -0.01% -6 B 🔽
@sentry/cloudflare (withSentry) - minified 204.35 kB - -
@sentry/cloudflare (withSentry) 474.32 kB - -
@sentry/nextjs/cloudflare (withSentry) - minified 229.66 kB - -

View base workflow run

@github-actions

github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Optional E2E tests

Some optional checks were not successful. They do not block the merge. 4 not successful, 56 successful. See the run.

Check Status
❌ CI: Optional E2E Tests / E2E node-eve Test (optional) Failing after 2m Details
❌ CI: Optional E2E Tests / E2E nextjs-16-cacheComponents (cloudflare) Test (optional) Failing after 10m Details
❌ CI: Optional E2E Tests / E2E node-eve (latest) Test (optional) Failing after 2m Details
❌ CI: Optional E2E Tests / E2E node-eve (orchestrion) Test (optional) Failing after 2m Details
Successful checks
Check Status
✅ CI: Optional E2E Tests / E2E cloudflare-flue-send-to-sentry Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nextjs-16 (deno) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nextjs-15 (latest) Test (optional) Successful in 3m Details
✅ CI: Optional E2E Tests / E2E cloudflare-agent Test (optional) Successful in 46s Details
✅ CI: Optional E2E Tests / E2E cloudflare-pi-durable Test (optional) Successful in 53s Details
✅ CI: Optional E2E Tests / E2E deno (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E cloudflare-think Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-flue Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (cloudflare) Test (optional) Successful in 44s Details
✅ CI: Optional E2E Tests / E2E nextjs-15 (turbo) Test (optional) Successful in 3m Details
✅ CI: Optional E2E Tests / E2E cloudflare-workers-send-to-sentry Test (optional) Successful in 3m Details
✅ CI: Optional E2E Tests / E2E gen-ai-libraries (cloudflare) Test (optional) Successful in 39s Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (latest) Test (optional) Successful in 53s Details
✅ CI: Optional E2E Tests / E2E cloudflare-think (ai v6) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (bun) Test (optional) Successful in 53s Details
✅ CI: Optional E2E Tests / E2E cloudflare-mastra Test (optional) Successful in 50s Details
✅ CI: Optional E2E Tests / E2E gen-ai-libraries Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E astro-7 Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E gen-ai-libraries (latest) Test (optional) Successful in 55s Details
✅ CI: Optional E2E Tests / E2E nextjs-16 (vinext, bun) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E astro-7-static Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (deno) Test (optional) Successful in 53s Details
✅ CI: Optional E2E Tests / E2E nextjs-16 (cloudflare, latest) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E node-openai-decisions Test (optional) Successful in 28s Details
✅ CI: Optional E2E Tests / E2E node-express-mcp-v2 Test (optional) Successful in 35s Details
✅ CI: Optional E2E Tests / E2E node-fastify-6 (tracer provider) Test (optional) Successful in 52s Details
✅ CI: Optional E2E Tests / E2E debug-id-sourcemaps Test (optional) Successful in 33s Details
✅ CI: Optional E2E Tests / E2E nextjs-14 (latest) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E node-flue (latest) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nuxt-5 (tunnel-dev) Test (optional) Successful in 51s Details
✅ CI: Optional E2E Tests / E2E node-express-mcp-v1 Test (optional) Successful in 35s Details
✅ CI: Optional E2E Tests / E2E nextjs-16-tunnel (cloudflare) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-mastra (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-pi-durable Test (optional) Successful in 45s Details
✅ CI: Optional E2E Tests / E2E vue-3 (no Options API) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-express-send-to-sentry-static Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E tanstackstart-react (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E solidstart-2 Test (optional) Successful in 59s Details
✅ CI: Optional E2E Tests / E2E react-send-to-sentry Test (optional) Successful in 3m Details
✅ CI: Optional E2E Tests / E2E node-openai-decisions (latest) Test (optional) Successful in 34s Details
✅ CI: Optional E2E Tests / E2E node-fastify-6 Test (optional) Successful in 34s Details
✅ CI: Optional E2E Tests / E2E supabase-nextjs Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nextjs-16 (vinext) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nextjs-orpc Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E react-router-7-framework-instrumentation Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nuxt-5-sourcemaps (static / nuxt generate) Test (optional) Successful in 35s Details
✅ CI: Optional E2E Tests / E2E nuxt-5-cloudflare Test (optional) Successful in 45s Details
✅ CI: Optional E2E Tests / E2E tanstackstart-react-cloudflare Test (optional) Successful in 37s Details
✅ CI: Optional E2E Tests / E2E cloudflare-pi-durable (latest) Test (optional) Successful in 45s Details
✅ CI: Optional E2E Tests / E2E node-pi-durable (latest) Test (optional) Successful in 34s Details
✅ CI: Optional E2E Tests / E2E nuxt-5-sourcemaps Test (optional) Successful in 33s Details
✅ CI: Optional E2E Tests / E2E nuxt-5-sourcemaps (client source maps kept) Test (optional) Successful in 35s Details
✅ CI: Optional E2E Tests / E2E node-mastra Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E tanstackstart-react-sourcemaps Test (optional) Successful in 35s Details
✅ CI: Optional E2E Tests / E2E nuxt-5 Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E node-express-send-to-sentry Test (optional) Successful in 1m Details

…remote

Only skip the default commit association on non-production Vercel builds
when there is no `origin` remote. Vercel's own builders have none, so
`--auto` always failed there. Builds that do have one, such as
`vercel build` / `vercel deploy --prebuilt` in GitHub Actions, keep
`--auto` as before.

Restore the production gate on the `VERCEL_GIT_*` branch so preview
builds with a remote never associate the PR's stem commits.

Co-Authored-By: bete <28983162+betegon@users.noreply.github.com>
@sentry-junior sentry-junior Bot changed the title fix(bundler-plugins): Skip default commit association on non-production Vercel builds fix(bundler-plugins): Skip default commit association on Vercel builds without a git remote Nov 12, 2026
…ository variables

Since CLI 0.48, `set-commits --auto` also resolves the repository from CI
variables such as GITHUB_REPOSITORY when there is no `origin` remote.
Only skip the default on non-production Vercel builds when neither is
available, so `vercel build` in another CI without a git checkout keeps
associating commits.

Co-Authored-By: bete <28983162+betegon@users.noreply.github.com>
@sentry-junior sentry-junior Bot changed the title fix(bundler-plugins): Skip default commit association on Vercel builds without a git remote fix(bundler-plugins): Skip default commit association on Vercel builds that --auto can't resolve Nov 12, 2026
@betegon
betegon marked this pull request as ready for review November 12, 2026 20:51
@betegon
betegon requested a review from a team November 12, 2026 20:51

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit a4768c4. Configure here.

In GitHub Actions GITHUB_REPOSITORY is set, so the preview test with a
git remote passed from CI variables without running the origin check.
@mydea
mydea requested a review from timfish November 13, 2026 12:39
@betegon
betegon merged commit a36dd15 into develop Nov 16, 2026
814 of 825 checks passed
@betegon
betegon deleted the fix/bundler-plugins-skip-auto-commits-vercel-preview branch November 16, 2026 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants