[sentry-junior]

Part of the CLI-2SK work. The branch is based on main after #1902. #1903 was closed and is not part of this change.

Sentry matches --commit repository names exactly (Release.set_refs, name__in). A name that refers to the same repository but is written differently, for example in a different case, fails with Invalid repository names. On Vercel production builds, @sentry/bundler-plugins passes VERCEL_GIT_REPO_OWNER/VERCEL_GIT_REPO_SLUG as-is, which is one way to end up with such a name.

Change. When the server rejects --commit refs as invalid repository names, the CLI now looks up each rejected name with the same matching --auto uses (findSentryRepository: case-insensitive name, URL path, GitLab display names). If every rejected name matches a Sentry repository, the CLI retries once with Sentry's names and prints a warning for each name it replaced. If any rejected name has no match, or the lookup fails, the command fails with #1902's error and next steps, unchanged. The commit range (PREV..SHA) the caller passed is kept.

Before / after

The CLI was run from source against a local stand-in for the Sentry API that rejects names the way Release.set_refs does. "Before" is main at 08fac06c (#1902), "after" is this branch.

Same repository, different case (org acme has acme/web)

Before

$ sentry release set-commits acme/1.0.0 --commit 'Acme/Web@abc1234..def5678'
Error: Sentry organization 'acme' has no repository named 'Acme/Web'. It has 'acme/web'. --commit needs the repository name exactly as Sentry shows it.

Try:
  sentry release set-commits acme/1.0.0 --commit 'acme/web@abc1234..def5678'
# exit 21

After

$ sentry release set-commits acme/1.0.0 --commit 'Acme/Web@abc1234..def5678'
[warn] [api.releases] Sentry organization 'acme' has no repository named 'Acme/Web'. Using 'acme/web', the same repository in Sentry.
Commits Set: 1.0.0
━━━━━━━━━━━━━━━━━━

╭─────────┬───────╮
│ Version │ 1.0.0 │
│ Commits │ 3     │
╰─────────┴───────╯
# exit 0

The retry sends acme/web with the same abc1234..def5678 range.

One name matches, another has no match (org acme has only acme/web)

Before and after are the same. No retry runs, and no "Using ..." warning is printed:

$ sentry release set-commits acme/1.0.0 --commit 'Acme/Web@abc1234..def5678,Acme/Api@def5678'
Error: Sentry organization 'acme' has no repository named 'Acme/Web'. It has 'acme/web'. --commit needs the repository name exactly as Sentry shows it.

Try:
  sentry release set-commits acme/1.0.0 --commit 'acme/web@abc1234..def5678'
# exit 21

Org has no repositories

Before and after are the same:

$ sentry release set-commits acme/1.0.0 --commit 'Acme/Web@abc1234..def5678'
Error: Sentry organization 'acme' has no repository named 'Acme/Web'. It has no repositories yet, so it cannot associate commits.

Try:
  sentry integration list acme/

Note: Connect GitHub, GitLab, Bitbucket, or Azure DevOps to Sentry and add the repository: https://acme.sentry.io/settings/integrations/?category=source%20code%20management
# exit 21

Repository not in Sentry, similar names exist (org acme has acme/website, acme/web-app, acme/api)

Before and after are the same:

$ sentry release set-commits acme/1.0.0 --commit 'Acme/Web@abc1234..def5678'
Error: Sentry organization 'acme' has no repository named 'Acme/Web'. It has similarly named repositories: acme/website, acme/web-app.

Try:
  sentry release set-commits acme/1.0.0 --commit 'acme/website@abc1234..def5678'
  sentry release set-commits acme/1.0.0 --commit 'acme/web-app@abc1234..def5678'
  sentry repo list acme/

Note: Add the repository to Sentry through your source code integration: https://acme.sentry.io/settings/repos/
# exit 21

Why the CLI and not only the plugin

The fix applies to every --commit caller: the bundler plugin, CI scripts and people. The plugin keeps passing Vercel's previous deployment SHA, so the range doesn't change.

Tests

• correctRefRepositories: case-only correction (with its warning), no match, a later name with no match (no warning, no retry), other errors (no lookup), lookup failure.
• set-commits --commit retries with the corrected refs.
• The release, error-reporting and URL suites pass (284 tests), and pnpm run lint passes. I did not run the full suite.

via @betegon.

--

View Session [Sentry]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Nov 4, 2026 5:46pm UTC

[cursor]

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

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

^{Reviewed by Cursor Bugbot for commit ecefc07. Configure here.}