diff --git a/.chloggen/add-exemplars-logging.yaml b/.chloggen/add-exemplars-logging.yaml deleted file mode 100644 index 1c30277435e..00000000000 --- a/.chloggen/add-exemplars-logging.yaml +++ /dev/null @@ -1,16 +0,0 @@ -# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' -change_type: enhancement - -# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) -component: loggingexporter - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Adds exemplars logging to the logging exporter when `detailed` verbosity level is set. - -# One or more tracking issues or pull requests related to the change -issues: [7912] - -# (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: diff --git a/.chloggen/exporter-helper-v2.yaml b/.chloggen/exporter-helper-v2.yaml deleted file mode 100644 index 600a71f1b0c..00000000000 --- a/.chloggen/exporter-helper-v2.yaml +++ /dev/null @@ -1,12 +0,0 @@ -# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' -change_type: enhancement - -# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) -component: exporter/exporterhelper - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Introduce a new exporter helper that operates over client-provided requests instead of pdata - -# One or more tracking issues or pull requests related to the change -issues: [7874] - diff --git a/.chloggen/fix-public-api-otlpreceiver.yaml b/.chloggen/fix-public-api-otlpreceiver.yaml deleted file mode 100644 index afba971a5aa..00000000000 --- a/.chloggen/fix-public-api-otlpreceiver.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Use this changelog template to create an entry for release notes. - -# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' -change_type: enhancement - -# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) -component: otlpreceiver - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Export HTTPConfig as part of the API for creating the otlpreceiver configuration. - -# One or more tracking issues or pull requests related to the change -issues: [8175] - -# (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: Changes signature of receiver/otlpreceiver/config.go type httpServerSettings to HTTPConfig. - -# 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 diff --git a/.chloggen/otlp_with_authority.yaml b/.chloggen/otlp_with_authority.yaml deleted file mode 100755 index a7af2870d4c..00000000000 --- a/.chloggen/otlp_with_authority.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Use this changelog template to create an entry for release notes. - -# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' -change_type: enhancement - -# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) -component: configgrpc - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: "Add support for :authority pseudo-header in grpc client" - -# One or more tracking issues or pull requests related to the change -issues: [8228] - -# (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: []