From d45a9dc9331c99535ec293860311727fb2e67e21 Mon Sep 17 00:00:00 2001 From: Serhii Snitsaruk Date: Thu, 26 Feb 2026 21:57:06 +0100 Subject: [PATCH] docs(godot): Document environment variable fallbacks for release and environment options Add explicit mentions of SENTRY_RELEASE and SENTRY_ENVIRONMENT env var fallbacks to the Godot SDK options and environments pages, consistent with how other SDKs (Unreal, Python) document them. Co-Authored-By: Claude --- docs/platforms/godot/configuration/environments.mdx | 2 ++ docs/platforms/godot/configuration/options.mdx | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/platforms/godot/configuration/environments.mdx b/docs/platforms/godot/configuration/environments.mdx index 71a8cf9446de34..905e4006e6430f 100644 --- a/docs/platforms/godot/configuration/environments.mdx +++ b/docs/platforms/godot/configuration/environments.mdx @@ -12,4 +12,6 @@ Environments are case-sensitive. The environment name can't contain newlines, sp +If you do not set `environment` explicitly, the SDK will check for the `SENTRY_ENVIRONMENT` environment variable. If that is also not set, the SDK will automatically detect the environment based on the current runtime context. + Environments help you better filter issues, releases, and user feedback in the Issue Details page of sentry.io, which you learn more about in our [documentation that covers using environments](/product/sentry-basics/environments/). diff --git a/docs/platforms/godot/configuration/options.mdx b/docs/platforms/godot/configuration/options.mdx index 06d018130edd0b..39fe5f17f00c3e 100644 --- a/docs/platforms/godot/configuration/options.mdx +++ b/docs/platforms/godot/configuration/options.mdx @@ -42,7 +42,7 @@ Specifies the minimum level of messages to be printed if `debug` is turned on. P -Release version of the application. This value must be unique across all projects in your organization. By default, the SDK reads from the `application/config/name` and `application/config/version` project settings to generate the release identifier in the format `"{app_name}@{app_version}"`. Alternatively, you can set `release` to a custom value [programmatically](#programmatic-configuration), optionally using the `{app_name}` and `{app_version}` placeholders. +Release version of the application. This value must be unique across all projects in your organization. If not set explicitly, the SDK will try to read this value from the `SENTRY_RELEASE` environment variable. Otherwise, the SDK reads from the `application/config/name` and `application/config/version` project settings to generate the release identifier in the format `"{app_name}@{app_version}"`. You can also set `release` to a custom value [programmatically](#programmatic-configuration), optionally using the `{app_name}` and `{app_version}` placeholders. Release names are strings, but some formats are detected by Sentry and might be rendered differently. Learn more about how to send release data so Sentry can tell you about regressions between releases and identify the potential source in [the releases documentation](/product/releases/) or the sandbox. @@ -58,7 +58,7 @@ Sets the distribution of the application. Distributions are used to disambiguate Sets the environment. Environments indicate where an error occurred, such as in a release export, headless server, QA build, or another deployment. A release can be associated with more than one environment to separate them in the UI (think `staging` vs `production` or similar). -This option defaults to `{auto}`, which automatically detects the environment based on the current runtime context and sets it to one of the following values: `editor_dev`, `editor_dev_run`, `export_debug`, `export_release`, or `dedicated_server`. +If not set explicitly, the SDK will try to read this value from the `SENTRY_ENVIRONMENT` environment variable. Otherwise, this option defaults to `{auto}`, which automatically detects the environment based on the current runtime context and sets it to one of the following values: `editor_dev`, `editor_dev_run`, `export_debug`, `export_release`, or `dedicated_server`.