fix: SENTRY_LOG_LEVEL env naming #1051
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Litarnus
reviewed
Oct 17, 2025
Contributor
Litarnus
left a comment
Litarnus
left a comment
There was a problem hiding this comment.
Thanks for opening the PR! I added a suggestion to remain BC. It's a bit unfortunate and we will aim to remove the inconsistent option in the next major
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changelog states we are to use
SENTRY_LOG_LEVEL, but the config is looking forSENTRY_LOGS_LEVEL, which doesn't appear to conform to the baseLOG_LEVELenv variable.