Immutable solution version
Sentry: upload fails, release not found
Complete solution
Source map or release commands failing because the release does not exist yet. Create-then-upload ordering, and why auto-created releases still lack commits.
Sentry: upload fails, release not found
The error
A sentry-cli sourcemaps upload --release [version] (or similar) fails because the release does not exist in Sentry yet.
Why it happens
Upload commands attach artifacts to a release. If nothing created that release, there is nothing to attach to. Sentry does auto-create a release when the first event arrives with that identifier, but your CI upload runs before any event exists, so at upload time the release is absent.
The fix: create, then upload
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 releases command, 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 identifier must match everywhere
The [version] in the CLI, the release in SDK init (or SENTRY_RELEASE), and the deployed code must be byte-identical. 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. Pick one scheme (service@version recommended) and generate it once per pipeline run.
Verify
After the pipeline, open the Releases page and confirm the version shows with commits and the uploaded artifacts. Auto-created releases (from events alone) work for grouping but lack commits and deploy markers, so the explicit create step is worth keeping.
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 1 · 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>