From 22474f76939526b3de59339e83b173edbd0ff545 Mon Sep 17 00:00:00 2001 From: Martin Mattel Date: Fri, 13 Sep 2024 10:44:35 +0200 Subject: [PATCH] [docs-only] Clarify introduction version when adding an envvar to an existing one --- docs/services/general-info/envvar-scopes.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/services/general-info/envvar-scopes.md b/docs/services/general-info/envvar-scopes.md index f043cf36d..8d7dbbb2b 100644 --- a/docs/services/general-info/envvar-scopes.md +++ b/docs/services/general-info/envvar-scopes.md @@ -58,6 +58,10 @@ For the documentation to show the correct value for the `IV` (introduction versi During the releasing process for a production release, the placeholder `%%NEXT%%` has to be replaced with the new production version number like `%%NEXT%%` → `7.0.0`. +### Adding Envvars to Existing Ones + +If an envvar has been introduced with a particular version, the `introductionVersion` gets a value accordingly. If an additional envvar like a global one is added to this existing envvar later on, the introduction version will *not* be changed. + ### Deprecate Existing Envvars See the [deprecation rules]({{< ref "./deprecating-variables.md" >}}) documentation for more details.