Skip to content

fix: warn about missing SENTRY_RELEASE when it's set to empty string#2394

Merged
a-hariti merged 5 commits intomasterfrom
warn-empty-sentry-release-var
Feb 19, 2025
Merged

fix: warn about missing SENTRY_RELEASE when it's set to empty string#2394
a-hariti merged 5 commits intomasterfrom
warn-empty-sentry-release-var

Conversation

@a-hariti
Copy link
Collaborator

I'm not sure if this covers all instances/paths

closes #2385

@szokeasaurusrex
Copy link
Member

szokeasaurusrex commented Feb 19, 2025

@a-hariti i think this will only cover the environment variable. However, release can also be set in other ways, e.g. via command line argument. I think we should instead change where we serialize the data for the HTTP request. I would be happy to point you in the right direction.

@a-hariti
Copy link
Collaborator Author

Yes, I would love to

@a-hariti
Copy link
Collaborator Author

Copy link
Member

@szokeasaurusrex szokeasaurusrex left a comment

Choose a reason for hiding this comment

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

Looks good, nice first PR! I noticed a couple small things to change before we merge, but I'll approve once those are addressed

Copy link
Member

@szokeasaurusrex szokeasaurusrex left a comment

Choose a reason for hiding this comment

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

Nice!

@a-hariti a-hariti merged commit c7919f5 into master Feb 19, 2025
14 checks passed
@a-hariti a-hariti deleted the warn-empty-sentry-release-var branch February 19, 2025 17:51
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.

Sentry reported an error: '' does not match '^[^/]+$' (http status: 400)

2 participants