Merge branch 'main' into goleak_configtls

.chloggen/codeboten_mdatagen.yaml → .chloggen/cipher_suites.yaml

@@ -4,18 +4,19 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: mdatagen
+component: configtls
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: move component from contrib to core
+note: add `cipher_suites` to configtls.
 
 # One or more tracking issues or pull requests related to the change
-issues: [9172]
+issues: [8105]
 
 # (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:
+subtext: |
+  Users can specify a list of cipher suites to pick from. If left blank, a safe default list is used.
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'

.chloggen/fix_dependency_otlpreceiver_otlpexporter.yaml → .chloggen/codeboten_cleanup-deprecated.yaml

@@ -1,16 +1,16 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: otlpexporter
+component: exporterhelper
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: remove dependency of otlphttpreceiver on otlpexporter
+note: remove deprecated exporterhelper.RetrySettings and exporterhelper.NewDefaultRetrySettings
 
 # One or more tracking issues or pull requests related to the change
-issues: [6454]
+issues: [9256]
 
 # (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.

.chloggen/confignet-add-dialertimeout.yaml → .chloggen/codeboten_mark-stable-otel.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: confignet
+component: service
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add `dialer_timeout` config option.
+note: mark `telemetry.useOtelForInternalMetrics` as stable
 
 # One or more tracking issues or pull requests related to the change
-issues: [9066]
+issues: [816]
 
 # (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.

.chloggen/mx-psi_deprecate-memory-ballast.yaml → .chloggen/codeboten_rm-deprecated-obsreport2.yaml

@@ -4,23 +4,27 @@
 change_type: deprecation
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: extension/ballast
+component: obsreporttest
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate `memory_ballast` extension.
+note: deprecate test funcs/structs
 
 # One or more tracking issues or pull requests related to the change
-issues: [8343]
+issues: [8492]
 
 # (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: | 
-    Use `GOMEMLIMIT` environment variable instead.
+subtext: |
+  The following methods/structs have been moved from obsreporttest to componenttest:
+  - obsreporttest.TestTelemetry -> componenttest.TestTelemetry
+  - obsreporttest.SetupTelemetry -> componenttest.SetupTelemetry
+  - obsreporttest.CheckScraperMetrics -> TestTelemetry.CheckScraperMetrics
+  - obserporttest.TestTelemetry.TelemetrySettings -> componenttest.TestTelemetry.TelemetrySettings()
 
 # 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: []
+change_logs: [api]

.chloggen/confignet-now-with-ctx.yaml → .chloggen/confignet-remove-deprecated-functions.yaml

@@ -7,15 +7,15 @@ change_type: deprecation
 component: confignet
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecates the `Dial` and `Listen` functions in favor of `DialContext` and `ListenContext`.
+note: Deprecates `DialContext` and `ListenContext` functions. Use `Dial` and `Listen` instead.
 
 # One or more tracking issues or pull requests related to the change
-issues: [9163]
+issues: [9258]
 
 # (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:
+subtext: Unlike the previous `Dial` and `Listen` functions, the new `Dial` and `Listen` functions take a `context.Context` like `DialContext` and `ListenContext`.
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'

.chloggen/make_error_unused_default.yaml → .chloggen/configopaque_stringer.yaml

@@ -4,24 +4,24 @@
 change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: confmap
+component: configopaque
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Make the option `WithErrorUnused` enabled by default when unmarshaling configuration
+note: configopaque.String implements `fmt.Stringer` and `fmt.GoStringer`, outputting [REDACTED] when formatted with the %s, %q or %#v verbs`
 
 # One or more tracking issues or pull requests related to the change
-issues: [7102]
+issues: [9213]
 
 # (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: |
-  The option `WithErrorUnused` is now enabled by default, and a new option `WithIgnoreUnused` is introduced to ignore
-  errors about unused fields.
+subtext: | 
+  This may break applications that rely on the previous behavior of opaque strings with `fmt.Sprintf` to e.g. build URLs or headers.
+  Explicitly cast the opaque string to a string before using it in `fmt.Sprintf` to restore the previous behavior.
 
 # 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: []
+change_logs: [user, api]

.chloggen/memory-limiter-update-config-validation-errors.yaml → .chloggen/exporter-helper-cleanup-error-logs.yaml

@@ -1,27 +1,27 @@
-# 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: processor/memory_limiter
+component: exporters
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Update config validation errors
+note: Cleanup log messages for export failures
 
 # One or more tracking issues or pull requests related to the change
-issues: [9059]
+issues: [9219]
 
 # (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: |
-  - Fix names of the config fields that are validated in the error messages
-  - Move the validation from start to the initialization phrase 
+  1. Ensure an error message is logged every time and only once when data is dropped/rejected due to export failure.
+  2. Update the wording. Specifically, don't use "dropped" term when an error is reported back to the pipeline.
+     Keep the "dropped" wording for failures happened after the enabled queue.
+  3. Properly report any error reported by a queue. For example, a persistent storage error must be reported as a storage error, not as "queue overflow".
 
 # 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: [user]
+change_logs: [user]

.chloggen/fix-leaking-goroutine-in-memorylimiter.yaml → .chloggen/handle-grpc-status-codes.yaml

@@ -1,25 +1,16 @@
-# 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. otlpreceiver)
-component: memorylimiterprocessor
+component: otlpreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fixed leaking goroutines from memorylimiterprocessor
+note: Ensure OTLP receiver handles consume errors correctly
 
 # One or more tracking issues or pull requests related to the change
-issues: [9099]
+issues: [4335]
 
 # (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: []
+subtext: Make sure OTLP receiver returns correct status code and follows the receiver contract (gRPC)