Immutable solution version
Sentry: upload fails, release not found
Complete solution
Shows how to fix sentry: upload fails, release not found. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
A sentry-cli sourcemaps upload --release [version] (or similar) fails because the release does not exist in Sentry yet. Usual culprits: a v prefix in one place, trailing whitespace from CI variables, or the SDK inferring the git SHA while CI passes a tag name.
Steps
- A
sentry-cli sourcemaps upload --release [version](or similar) fails because the release does not exist in Sentry yet.
sentry-cli releases -o [your org] new -p [your project] [version]
sentry-cli releases -o [your org] -p [your project] set-commits [version] --auto
sentry-cli sourcemaps upload --release [version] [maps dir]- Note the scoping: org on the
releasescommand, project on the subcommand. Get this backwards and the release is created on the wrong project, which produces the same not-found error on the next step. - The
[version]in the CLI, thereleasein SDK init (orSENTRY_RELEASE), and the deployed code must be byte-identical. Usual culprits: avprefix in one place, trailing whitespace from CI variables, or the SDK inferring the git SHA while CI passes a tag name. Pick one scheme (service@versionrecommended) and generate it once per pipeline run.
When to use
You are seeing this: Upload commands attach artifacts to a release. Use this skill when you run into "Sentry: upload fails, release not found".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
Upload commands attach artifacts to a release.
Evidence
Researched against live Sentry docs 2026-09-26. The releases page (docs.sentry.io/product/releases/) documents that Sentry auto-creates a release entity on the first event carrying that identifier, but recommends notifying before deploy; releases link to one or more projects; and commit association requires the set-commits step. The CLI configuration page (docs.sentry.io/cli/configuration/) documents the releases command scoping (org on the command, project on the subcommand).
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_yhi1AOgHzIka00eIPMidHA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Sentry: upload fails, release not found <span>— Vectle</span></a>