From 492d0f33bc447ee8eeccc4b7c9f76d2d32ea11aa Mon Sep 17 00:00:00 2001 From: Alex Boten Date: Mon, 18 Sep 2023 12:08:26 -0700 Subject: [PATCH] changelog Signed-off-by: Alex Boten --- .chloggen/codeboten_rm-pipelineconfig.yaml | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100755 .chloggen/codeboten_rm-pipelineconfig.yaml diff --git a/.chloggen/codeboten_rm-pipelineconfig.yaml b/.chloggen/codeboten_rm-pipelineconfig.yaml new file mode 100755 index 00000000000..3a434ba9363 --- /dev/null +++ b/.chloggen/codeboten_rm-pipelineconfig.yaml @@ -0,0 +1,25 @@ +# Use this changelog template to create an entry for release notes. + +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' +change_type: breaking + +# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) +component: service + +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). +note: remove deprecated service.PipelineConfig + +# One or more tracking issues or pull requests related to the change +issues: [8485] + +# (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: + +# 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: [api] \ No newline at end of file