Skip to content

Conversation

@markushi
Copy link
Member

As we're moving towards some more dashboard centric insights, we want to learn more about the usage of primary and secondary releases.

@markushi markushi requested a review from a team as a code owner November 25, 2025 08:45
@markushi
Copy link
Member Author

@sentry review

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 25, 2025
@markushi
Copy link
Member Author

I manually tested this by executing window.localStorage.setItem('DEBUG_ANALYTICS', 1); in the browser developer console, and checking the log output. If there's a better way please let me know 😅 (seems like for full amplitude testing getsentry needs to be configured as well).

@DominikB2014
Copy link
Contributor

I manually tested this by executing window.localStorage.setItem('DEBUG_ANALYTICS', 1); in the browser developer console, and checking the log output. If there's a better way please let me know 😅 (seems like for full amplitude testing getsentry needs to be configured as well).

I think you can test amplitude with the chrome extension too

@markushi markushi merged commit 360bb91 into master Nov 27, 2025
49 checks passed
@markushi markushi deleted the markushi/feat/release-selection-tracking branch November 27, 2025 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants