sentry-cli releases 2.36.2 breaks with existing auth token

[pchorus]

CLI Version

2.36.2

Operating System and Architecture

• macOS (arm64)
• macOS (x86_64)
• Linux (i686)
• Linux (x86_64)
• Linux (armv7)
• Linux (aarch64)
• Windows (i686)
• Windows (x86_64)

Operating System Version

Ubuntu 22.04

Link to reproduction repository

No response

CLI Command

sentry-cli releases --org foo --project bar deploys '1234abcdef' new -e dev

Exact Reproduction Steps

Since version 2.36.2 the above command failed with error message

error: API request failed
  caused by: sentry reported an error: request failure (http status: 400)
  Object {"projects": Array [String("Insufficient access to project")]}

Our auth token has the following scopes according to the current documentation: org:read, project:releases.
Above command was working successfully with version 2.36.1.

It seems there are additional scopes required since 2.36.2, please see getsentry/sentry-cli#2160.

Expected Results

Command should work in v2.36.2 as it did in v2.36.1 with auth scopes org:read and project:releases.

Actual Results

See above

Logs

See above

[szokeasaurusrex]

Hey @pchorus, thanks for reporting this issue! I need to investigate a bit further before I can give you a full response here, but for now, you can workaround the problem by omitting the --project argument, like so:

sentry-cli releases --org foo deploys '1234abcdef' new -e dev

Since the --project argument was completely ignored prior to version 2.36.2 (that is the bug getsentry/sentry-cli#2160 fixes), this command is equivalent to what you were running before.

[szokeasaurusrex]

Hi @pchorus, after investigating further, I think this might be a bug in the Sentry backend. Since your auth token has project:releases permissions, and since these permissions are already sufficient to associate a release with specific projects via the releases new command, I think it is reasonable that you should also be able to associate a deploy with specific projects with an auth token with the same scope.

I am going to transfer this issue over to the correct repository.

[getsantry]

Assigning to @getsentry/support for routing ⏲️