Since the move to the sentry CLI SDK (#23398, in 11.0), sentry-upload-sourcemaps calls release.create({ orgVersion }) without a project. The release API requires one, and the SDK's default project does not reach that call, so every run fails with Failed to create release: 400 Bad Request. The unit test mocks the SDK, so it did not catch this. Reproduced against a real org.
@sentry/react-router's Vite build end (handleOnBuildEnd) has the same call, so its release creation fails too; the upload still runs. sentry-remix-v3-upload-sourcemaps passes --project through, but does not fall back to SENTRY_PROJECT.
Fix: pass the project to release.create everywhere (flag, then SENTRY_PROJECT for the scripts), and fail with a clear message when neither is set. Update the unit tests to assert the project is passed. @sentry/bundler-plugins already does this.
Since the move to the
sentryCLI SDK (#23398, in 11.0),sentry-upload-sourcemapscallsrelease.create({ orgVersion })without a project. The release API requires one, and the SDK's default project does not reach that call, so every run fails withFailed to create release: 400 Bad Request. The unit test mocks the SDK, so it did not catch this. Reproduced against a real org.@sentry/react-router's Vite build end (handleOnBuildEnd) has the same call, so its release creation fails too; the upload still runs.sentry-remix-v3-upload-sourcemapspasses--projectthrough, but does not fall back toSENTRY_PROJECT.Fix: pass the project to
release.createeverywhere (flag, thenSENTRY_PROJECTfor the scripts), and fail with a clear message when neither is set. Update the unit tests to assert the project is passed.@sentry/bundler-pluginsalready does this.