Merge branch 'main' of github.com:open-telemetry/opentelemetry-collector into 15010

Author: iblancasa

.chloggen/queuebatchprocessor.yaml …loggen/confighttp-auth-named-config.yaml.chloggen/queuebatchprocessor.yaml renamed to .chloggen/confighttp-auth-named-config.yaml .chloggen/queuebatchprocessor.yaml renamed to .chloggen/confighttp-auth-named-config.yaml

@@ -1,25 +1,25 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: new_component
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: processor/queuebatch
+component: pkg/confighttp
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "New `queuebatchprocessor` to replace the legacy `batchprocessor`."
+note: Make `configauth.Config` a named field of `AuthConfig` instead of an embedded one.
 
 # One or more tracking issues or pull requests related to the change
-issues: [15047, 13582, 12022, 11308, 8272, 6046]
+issues: [15308]
 
 # (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: "New implementation is based exporterhelper, uses same configuration as `sending_queue`."
+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: [user]
+change_logs: [api]

.chloggen/exporterhelper-queue-batch-gate.yaml

@@ -0,0 +1,13 @@
+change_type: enhancement
+
+component: pkg/exporterhelper
+
+note: Add the `pkg.exporterhelper.queueBatchEnabled` feature gate
+
+issues: [14038, 13582, 12022]
+
+subtext: |
+  When enabled, the batch settings returned by `NewDefaultQueueConfig()` have
+  `batch::enabled` true. See [migration RFC](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/batching-migration.md#phase-1).
+
+change_logs: [user]

.chloggen/mdatagen_extended_types.yaml

@@ -1,28 +1,25 @@
 # 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: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: cmd/mdatagen
+component: pkg/config/configretry
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Versioned metrics don't handle renamed attributes with same type
+note: Migrate `BackOffConfig` to schema-based configuration generated by mdatagen.
 
 # One or more tracking issues or pull requests related to the change
-issues: [15595]
+issues: [15502]
 
 # (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: |
-  Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the
-  attributes names differ. This was not working when the attributes name changed but the type remained the same.
-  Here we add support to versioned metrics with renamed attributes where those attributes have the same type.
+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: []
+change_logs: [api]

…-handle-attribute-renames-correctly.yaml .chloggen/migrate_configretry.yaml.chloggen/mdatagen-versioned-metrics-handle-attribute-renames-correctly.yaml renamed to .chloggen/migrate_configretry.yaml .chloggen/mdatagen-versioned-metrics-handle-attribute-renames-correctly.yaml renamed to .chloggen/migrate_configretry.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: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: cmd/mdatagen
+component: pkg/config/configtls
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Removes the extra line in the documentation.md around description
+note: Migrate `TLS` core types to schema-based configuration generated by mdatagen.
 
 # One or more tracking issues or pull requests related to the change
-issues: [15664]
+issues: [15693]
 
 # (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.
@@ -22,4 +22,4 @@ subtext:
 # 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/description-fix-extline.yaml .chloggen/migrate_tls_config.yaml.chloggen/description-fix-extline.yaml renamed to .chloggen/migrate_tls_config.yaml

@@ -1,29 +1,25 @@
 # 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. receiver/otlp)
-component: cmd/mdatagen
+component: extension/zpages
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix incorrect collision warning for versioned metrics with different emitted names
+note: Make `confighttp.ServerConfig` a named field of `Config` instead of an embedded one.
 
 # One or more tracking issues or pull requests related to the change
-issues: [15648]
+issues: [15308]
 
 # (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: |
-  Same name collision detection (type/attribute checks) was being used for versioned metrics
-  with different names. This caused the legacy metric to be disabled which was incorrect and also
-  a warning msg was being incorrectly logged that stated the metrics had the same name when in
-  fact they had different names.
 
 # 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]

…ix-versioned-metric-different-names.yaml .chloggen/zpages-named-serverconfig.yaml.chloggen/mdatagen-fix-versioned-metric-different-names.yaml renamed to .chloggen/zpages-named-serverconfig.yaml .chloggen/mdatagen-fix-versioned-metric-different-names.yaml renamed to .chloggen/zpages-named-serverconfig.yaml

@@ -7,6 +7,26 @@ If you are looking for user-facing changes, check out [CHANGELOG.md](./CHANGELOG
 
 <!-- next version -->
 
+## v1.64.0/v0.158.0
+
+### 🛑 Breaking changes 🛑
+
+- `pkg/xconfmap`: Remove `Validator` and `Validate` (#15613)
+  Use the equivalent symbols in `confmap` instead.
+
+### 💡 Enhancements 💡
+
+- `cmd/mdatagen`: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513)
+  Authors can now write `type: int64`, `type: duration`, `type: opaque_string`, `type: id`, or
+  `type: opaque_map` directly as a property type in the `config:` section of `metadata.yaml`.
+  Each alias expands to the correct JSON Schema representation and Go type automatically.
+  Existing uses of standard JSON Schema types, `format:`, and `x-customType:` remain supported
+  without migration.
+  
+- `pkg/config/configgrpc`: Mark configgrpc as stable (#9477)
+
+<!-- previous-version -->
+
 ## v1.63.0/v0.157.0
 
 ### 🛑 Breaking changes 🛑

CHANGELOG-API.md

@@ -7,6 +7,59 @@ If you are looking for developer-facing changes, check out [CHANGELOG-API.md](./
 
 <!-- next version -->
 
+## v1.64.0/v0.158.0
+
+### 🚀 New components 🚀
+
+- `processor/queuebatch`: New `queuebatchprocessor` to replace the legacy `batchprocessor`. (#15047, #13582, #12022, #11308, #8272, #6046)
+  New implementation is based exporterhelper, uses same configuration as `sending_queue`.
+
+### 💡 Enhancements 💡
+
+- `cmd/mdatagen`: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513)
+  Authors can now write `type: int64`, `type: duration`, `type: opaque_string`, `type: id`, or
+  `type: opaque_map` directly as a property type in the `config:` section of `metadata.yaml`.
+  Each alias expands to the correct JSON Schema representation and Go type automatically.
+  Existing uses of standard JSON Schema types, `format:`, and `x-customType:` remain supported
+  without migration.
+  
+- `extension/memory_limiter`: Promote the memory limiter extension to beta stability. (#14533)
+
+### 🧰 Bug fixes 🧰
+
+- `cmd/mdatagen`: Removes the extra line in the documentation.md around description (#15664)
+- `cmd/mdatagen`: Auto-enable v1 metrics when legacy metric is enabled and v1 feature gate is on (#15650)
+  When the v1 feature gate is enabled and a legacy metric is enabled, the corresponding
+  v1 metric is now programmatically enabled so users don't need to add the v1 metric
+  to their config.
+  
+- `cmd/mdatagen`: Fix incorrect collision warning for versioned metrics with different emitted names (#15648)
+  Same name collision detection (type/attribute checks) was being used for versioned metrics
+  with different names. This caused the legacy metric to be disabled which was incorrect and also
+  a warning msg was being incorrectly logged that stated the metrics had the same name when in
+  fact they had different names.
+  
+- `cmd/mdatagen`: Versioned metrics don't handle renamed attributes with same type (#15595)
+  Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the
+  attributes names differ. This was not working when the attributes name changed but the type remained the same.
+  Here we add support to versioned metrics with renamed attributes where those attributes have the same type.
+  
+- `exporter/debug`: Fix profile sample attribute formatting for non-string values (#15647)
+  Previously, non-string values produced malformed output such as `%!s(int64=42)`.
+  Profile sample attributes now use the debug exporter's typed attribute format, such as `Int(42)`.
+  This will also change strings from `hello-world` to `Str(hello-world)`.
+  
+- `pkg/config/configtls`: Fix goroutine and file descriptor leak when `client_ca_file_reload` is enabled (#9221)
+  Every call to `ServerConfig.LoadTLSConfig` with `client_ca_file_reload` enabled started a
+  file watcher goroutine that could never be stopped, since the reloader was not reachable
+  from the returned `*tls.Config`. The client CA file is now checked for changes while TLS
+  handshakes are served, at most once per second, matching how `reload_interval` already
+  reloads the server certificate. No background goroutine is started, so nothing is left
+  behind when a server is torn down and recreated.
+  
+
+<!-- previous-version -->
+
 ## v1.63.0/v0.157.0
 
 ### 🛑 Breaking changes 🛑

CHANGELOG.md

@@ -163,7 +163,7 @@ Here is a list of community roles with current and previous members:
 
 ### Maintainers
 
-- [Alex Boten](https://github.com/codeboten), Honeycomb
+- [Alex Boten](https://github.com/codeboten), Grafana Labs
 - [Bogdan Drutu](https://github.com/bogdandrutu), Snowflake
 - [Dmitrii Anoshin](https://github.com/dmitryax), Splunk
 - [Evan Bradley](https://github.com/evan-bradley), Dynatrace

README.md

@@ -4,8 +4,8 @@ go 1.25.0
 
 require (
 	github.com/stretchr/testify v1.11.1
-	go.opentelemetry.io/collector/consumer v1.63.0
-	go.opentelemetry.io/collector/pdata v1.63.0
+	go.opentelemetry.io/collector/consumer v1.64.0
+	go.opentelemetry.io/collector/pdata v1.64.0
 	go.uber.org/goleak v1.3.0
 )
 
@@ -16,7 +16,7 @@ require (
 	github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
 	github.com/modern-go/reflect2 v1.0.3-0.20250322232337-35a7c28c31ee // indirect
 	github.com/pmezard/go-difflib v1.0.0 // indirect
-	go.opentelemetry.io/collector/featuregate v1.63.0 // indirect
+	go.opentelemetry.io/collector/featuregate v1.64.0 // indirect
 	go.uber.org/multierr v1.11.0 // indirect
 	gopkg.in/yaml.v3 v3.0.1 // indirect
 )