Skip to content

chore: rename variable to SENTRY_DSN_FRONTEND#2010

Merged
latin-panda merged 1 commit into
nextfrom
update-sentry-fe-variable
Jun 23, 2026
Merged

chore: rename variable to SENTRY_DSN_FRONTEND#2010
latin-panda merged 1 commit into
nextfrom
update-sentry-fe-variable

Conversation

@latin-panda

Copy link
Copy Markdown
Contributor

What has been done to verify that this works as intended?

Run docker, variable passed

Why is this the best possible solution? Were any other approaches considered?

Matches other pre-existing variables names

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

no

Does this change require updates to documentation? If so, please file an issue here and include the link below.

Updated readme file

Before submitting this PR, please make sure you have:

  • branched off and targeted the next branch OR only changed documentation/infrastructure (master is stable and used in production)
  • verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

@latin-panda latin-panda requested a review from lognaturel June 23, 2026 03:03
@latin-panda latin-panda changed the title chore: rename variable from ODK_CENTRAL_FRONTEND_SENTRY_DSN to SENTRY_DSN_FRONTEND chore: rename variable to SENTRY_DSN_FRONTEND Jun 23, 2026
@latin-panda latin-panda merged commit 259f9fa into next Jun 23, 2026
14 checks passed
@latin-panda latin-panda deleted the update-sentry-fe-variable branch June 23, 2026 03:31
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