From 87ccf3f607169249365d00864990e430b4ea7f3b Mon Sep 17 00:00:00 2001 From: Mike Dame Date: Tue, 9 Jul 2024 16:38:17 +0000 Subject: [PATCH] Add changelog --- .chloggen/fix-docker-telemetrygen.yaml | 27 ++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 .chloggen/fix-docker-telemetrygen.yaml diff --git a/.chloggen/fix-docker-telemetrygen.yaml b/.chloggen/fix-docker-telemetrygen.yaml new file mode 100644 index 000000000000..a1341821962e --- /dev/null +++ b/.chloggen/fix-docker-telemetrygen.yaml @@ -0,0 +1,27 @@ +# Use this changelog template to create an entry for release notes. + +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' +change_type: bug_fix + +# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) +component: cmd/telemetrygen + +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). +note: Fix `make docker-telemetrygen` command. + +# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. +issues: [33989] + +# (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: + +# If your change doesn't affect end users or the exported elements of any package, +# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. +# Optional: The change log or logs in which this entry should be included. +# e.g. '[user]' or '[user, api]' +# Include 'user' if the change is relevant to end users. +# Include 'api' if there is a change to a library API. +# Default: '[user]' +change_logs: []