From d66289a039347ecc76c30c2b5d38bd3f6c6921d1 Mon Sep 17 00:00:00 2001 From: Daniel Dyla Date: Mon, 16 Dec 2024 16:40:14 -0500 Subject: [PATCH] Changelog --- .chloggen/feature-flag-eval-value-type.yaml | 22 +++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100755 .chloggen/feature-flag-eval-value-type.yaml diff --git a/.chloggen/feature-flag-eval-value-type.yaml b/.chloggen/feature-flag-eval-value-type.yaml new file mode 100755 index 0000000000..7b71825caf --- /dev/null +++ b/.chloggen/feature-flag-eval-value-type.yaml @@ -0,0 +1,22 @@ +# Use this changelog template to create an entry for release notes. +# +# If your change doesn't affect end users you should instead start +# your pull request title with [chore] or use the "Skip Changelog" label. + +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' +change_type: enhancement + +# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db) +component: feature_flag + +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). +note: Add `feature_flag.evaluation.value_type` event attribute. + +# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. +# The values here must be integers. +issues: [4349] + +# (Optional) One or more lines of additional information to render under the primary note. +# These lines will be padded with 2 spaces and then inserted directly into the document. +# Use pipe (|) for multiline entries. +subtext: