Skip to content

build(deps): Bump sentry-cli to 3.6.2 - #1373

Open
runningcode wants to merge 1 commit into
mainfrom
no/bump-sentry-cli-3.6.2
Open

build(deps): Bump sentry-cli to 3.6.2#1373
runningcode wants to merge 1 commit into
mainfrom
no/bump-sentry-cli-3.6.2

Conversation

@runningcode

Copy link
Copy Markdown
Contributor

Bumps the bundled sentry-cli from 3.6.1 to 3.6.2.

Why the repo needs reconfiguring

sentry-cli 3.6.2 no longer combines a URL and a non-embedded auth token from different configuration sources: when the URL and token come from different sources, one is ignored with a warning.

The integration-tests-sentry-cli CI job hit exactly this: it provides the URL via the SENTRY_URL environment variable (a runtime source) while the tests wrote auth.token into sentry.properties (a file source). Under 3.6.2 the file token gets discarded and the uploads fail with Auth token is required.

Verified against the real 3.6.2 binary:

  • token in sentry.properties + SENTRY_URL env → Ignoring an auth token because the selected URL comes from a different configuration sourceMethod: Unauthorized
  • URL and token both via env → Method: Auth Token

This only affects CI — locally the upload integration tests are skipped via assumeFalse(SENTRY_URL is blank), so they never exercise the combination.

Changes

  • Bump plugin-build/sentry-cli.properties to 3.6.2 (triggers a re-download on the next build).
  • Set SENTRY_AUTH_TOKEN alongside SENTRY_URL in the integration-tests-sentry-cli workflow so the URL and token share one runtime source.
  • Drop the now-obsolete auth.token writes from the integration tests (3.6.2 discards a file token whenever SENTRY_URL is set in the env; org/project still come from the fixture's sentry.properties).

sentry-cli 3.6.2 discards a non-embedded auth token when the URL is resolved from a different configuration source (getsentry/sentry-cli#3378). The sentry-cli integration test job supplies the URL via the SENTRY_URL environment variable while the tests wrote the auth token into sentry.properties, so the token would now be ignored and the uploads would fail with "Auth token is required".

Provide the token via SENTRY_AUTH_TOKEN in the same CI job so the URL and token share a single runtime source, and drop the now-obsolete auth.token writes from the integration tests.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@runningcode
runningcode force-pushed the no/bump-sentry-cli-3.6.2 branch from dfdb0cd to f663946 Compare July 23, 2026 12:28
@runningcode
runningcode marked this pull request as ready for review July 23, 2026 12:32
Comment thread CHANGELOG.md
- Bump CLI from v3.6.0 to v3.6.1 ([#1367](https://github.com/getsentry/sentry-android-gradle-plugin/pull/1367))
- [changelog](https://github.com/getsentry/sentry-cli/blob/master/CHANGELOG.md#361)
- [diff](https://github.com/getsentry/sentry-cli/compare/3.6.0...3.6.1)
- Bump CLI from v3.6.0 to v3.6.2 ([#1367](https://github.com/getsentry/sentry-android-gradle-plugin/pull/1367), [#1373](https://github.com/getsentry/sentry-android-gradle-plugin/pull/1373))

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we call out this breaking change more explicitly here? The fact that this is a minor bump on the CLI but is a breaking change might be confusing.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, let's have a breaking change section (or behavior change something like that) and reference Daniel's comment on the sentry-cli PR

@romtsn romtsn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pre-approving, but let's update the changelog too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants