GeezerVison

Why: The default setCommits only meant to associate commits on Vercel production builds, as the existing comment says: on previews the previous commit is the PR's stem commit, which makes Sentry noisy. But only the manual --commit branch was gated on production. Preview and custom-environment builds fell through to { auto: true }. Vercel builds have no .git, so that set-commits --auto call always failed. The plugin swallowed 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. These builds now skip commit association, so they stop making an API call that can't succeed.

Production detection now uses getVercelEnv() (VERCEL_TARGET_ENV, falling back to VERCEL_ENV), the same check the deploy detection below it already uses. An explicit user setCommits still wins, and non-Vercel builds keep the --auto default.

Unsure about: vercel build run outside Vercel (for example vercel deploy --prebuilt from GitHub Actions) sets VERCEL=1 and does have a .git, so preview builds there used to get commits through --auto. They no longer do. That matches the stated intent, and anyone who wants it back can set release.setCommits: { auto: true }.

via @betegon.

--

View Session [Sentry]