Merge branch 'main' into 15256

Author: iblancasa

.chloggen/config.yaml

@@ -93,6 +93,7 @@ components:
     - pkg/xscraperhelper
     - processor/batch
     - processor/memory_limiter
+    - processor/queuebatch
     - processor/sample
     - provider/env
     - provider/file

…-handle-attribute-renames-correctly.yaml …loggen/confighttp-auth-named-config.yaml.chloggen/mdatagen-versioned-metrics-handle-attribute-renames-correctly.yaml renamed to .chloggen/confighttp-auth-named-config.yaml .chloggen/mdatagen-versioned-metrics-handle-attribute-renames-correctly.yaml renamed to .chloggen/confighttp-auth-named-config.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: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: cmd/mdatagen
+component: pkg/confighttp
 
 # 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: 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: [15595]
+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: |
-  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.
 
 # 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/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 .chloggen/migrate_configretry.yaml.chloggen/mdatagen_extended_types.yaml renamed to .chloggen/migrate_configretry.yaml

@@ -4,27 +4,22 @@
 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: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml
+note: Migrate `BackOffConfig` to schema-based configuration generated by mdatagen.
 
 # One or more tracking issues or pull requests related to the change
-issues: [15513]
+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: |
-  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.
+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, api]
+change_logs: [api]

.chloggen/migrate_tls_config.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: enhancement
+
+# The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
+component: pkg/config/configtls
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+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: [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.
+# 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]

.chloggen/zpages-named-serverconfig.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. receiver/otlp)
+component: extension/zpages
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+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: [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: |
+
+# 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]

.github/CODEOWNERS

@@ -99,6 +99,7 @@ processor/memorylimiterprocessor/                      @open-telemetry/collector
 processor/processorhelper/                             @open-telemetry/collector-approvers
 processor/processorhelper/xprocessorhelper/            @open-telemetry/collector-approvers
 processor/processortest/                               @open-telemetry/collector-approvers
+processor/queuebatchprocessor/                         @open-telemetry/collector-approvers @jmacd @iblancasa
 processor/xprocessor/                                  @open-telemetry/collector-approvers @mx-psi @dmathieu
 receiver/                                              @open-telemetry/collector-approvers
 receiver/nopreceiver/                                  @open-telemetry/collector-approvers @evan-bradley

.github/workflows/contrib-tests.yml

@@ -51,6 +51,8 @@ jobs:
           - processor
           - exporter-0
           - exporter-1
+          - exporter-2
+          - exporter-3
           - extension
           - connector
           - internal

.github/workflows/utils/cspell.json

@@ -282,6 +282,7 @@
       "httpprovider",
       "httpsprovider",
       "httptest",
+      "iblancasa",
       "icmpcheck",
       "icmpcheckreceiver",
       "illumos",

CHANGELOG-API.md

@@ -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 🛑