SENTRY_RELEASE error message instead of Project/Organisation not found

[simonlee-test]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

1. Change org slug from old_slug to new_slug
2. Define SENTRY_AUTH_TOKEN = old_slug_token
3. Run the following command in pipepline: sentry-cli sourcemaps inject --org old_slug --project my-frontend build && sentry-cli sourcemaps upload --org old_slug --project my-frontend build

Note: SENTRY_RELEASE does not play a role here, because once I replaced the old_slug token and org in step 2 and 3 to new_slug, I could build my project successfully. However, I did get the expected result (correct debugging message) after appending SENTRY_RELEASE in the .env file.

Expected Result

##[error]#12 126.5 > Analyzing 5 sources
##[error]#12 126.5 > Rewriting sources
##[error]#12 126.7 > Adding source map references
##[error]#12 126.9 error: Project not found. Ensure that you configured the correct project and organization.

Actual Result

##[error]#12 131.7 > Analyzing 5 sources
##[error]#12 131.8 > Rewriting sources
##[error]#12 131.9 error: This version of Sentry does not support artifact bundles. A release slug is required (provide with --release)

Product Area

Issues - Source Maps

Link

No response

DSN

https://2ef95a8f36cb4f1ff9867d5c0e4278e1@o4508335283306496.ingest.us.sentry.io/4508600353619968

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️