Merge branch 'main' into mx-psi/document-module-split-guidelines

.chloggen/deprecate-connectorprofiles.yaml → .chloggen/remove-connectorprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: connector
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate connectorprofiles module in favor of xconnector to allow adding more experimental data types.
+note: Remove deprecated connectorprofiles module, use xconnector instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-consumererrorprofiles.yaml → .chloggen/remove-consumererrorprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: consumererror
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate consumererrorprofiles module in favor of xconsumererror to allow adding more experimental data types.
+note: Remove deprecated consumererrorprofiles module, use xconsumererror instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-consumerprofiles.yaml → .chloggen/remove-consumerprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: consumer
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate consumerprofiles module in favor of xconsumer to allow adding more experimental data types.
+note: Remove deprecated consumerprofiles module, use xconsumer instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-exporterhelperprofiles.yaml → .chloggen/remove-exporterhelperprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: exporterhelper
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate exporterhelperprofiles module in favor of xexporterhelper to allow adding more experimental data types.
+note: Remove deprecated exporterhelperprofiles module, use xexporterhelper instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-exporterprofiles.yaml → .chloggen/remove-exporterprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: exporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate exporterprofiles module in favor of xexporter to allow adding more experimental data types.
+note: Remove deprecated exporterprofiles module, use xexporter instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-pipelieneprofiles.yaml → .chloggen/remove-pipelineprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: pipeline
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate pipelineprofiles module in favor of xpipeline to allow adding more experimental data types.
+note: Remove deprecated pipelineprofiles module, use xpipeline instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-processorhelperprofiles.yaml → .chloggen/remove-processorhelperprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: processorhelper
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate processorhelperprofiles module in favor of xprocessorhelper to allow adding more experimental data types.
+note: Remove deprecated processorhelperprofiles module, use xprocessorhelper instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-processorprofiles.yaml → .chloggen/remove-processorprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: processor
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate processorprofiles module in favor of xprocessor to allow adding more experimental data types.
+note: Remove deprecated processorprofiles module, use xprocessor instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/deprecate-receiverprofiles.yaml → .chloggen/remove-receiverprofiles.yaml

@@ -1,13 +1,11 @@
-# Use this changelog template to create an entry for release notes.
-
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
 component: receiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Deprecate receiverprofiles module in favor of xreceiver to allow adding more experimental data types.
+note: Remove deprecated receiverprofiles module, use xreceiver instead.
 
 # One or more tracking issues or pull requests related to the change
 issues: [11778]

.chloggen/rm-deprecated-scraper.yaml → .chloggen/remove_net_interface_warn.yaml

@@ -4,13 +4,13 @@
 change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: scraperhelper
+component: otelcol
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Remove deprecated scraperhelper.Scraper and helpers
+note: This PR removes the warning when 0.0.0.0 is used
 
 # One or more tracking issues or pull requests related to the change
-issues: [11803]
+issues: [11713, 8510]
 
 # (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: [api]
+change_logs: [user]

.github/CODEOWNERS

@@ -28,16 +28,10 @@ service/internal/graph          @open-telemetry/collector-approvers @djaglowski
 extension/experimental/storage  @open-telemetry/collector-approvers @swiatekm
 
 # Profiling-related modules
-pdata/pprofile                                 @open-telemetry/collector-approvers @mx-psi @dmathieu
-consumer/consumerprofiles                      @open-telemetry/collector-approvers @mx-psi @dmathieu
-consumer/xconsumer                             @open-telemetry/collector-approvers @mx-psi @dmathieu
-connector/connectorprofiles                    @open-telemetry/collector-approvers @mx-psi @dmathieu
-connector/xconnector                           @open-telemetry/collector-approvers @mx-psi @dmathieu
-exporter/exporterhelper/exporterhelperprofiles @open-telemetry/collector-approvers @mx-psi @dmathieu
-exporter/exporterhelper/xexporterhelper        @open-telemetry/collector-approvers @mx-psi @dmathieu
-exporter/exporterprofiles                      @open-telemetry/collector-approvers @mx-psi @dmathieu
-exporter/xexporter                             @open-telemetry/collector-approvers @mx-psi @dmathieu
-processor/processorprofiles                    @open-telemetry/collector-approvers @mx-psi @dmathieu
-processor/xprocessor                           @open-telemetry/collector-approvers @mx-psi @dmathieu
-receiver/receiverprofiles                      @open-telemetry/collector-approvers @mx-psi @dmathieu
-receiver/xreceiver                             @open-telemetry/collector-approvers @mx-psi @dmathieu
+pdata/pprofile                          @open-telemetry/collector-approvers @mx-psi @dmathieu
+consumer/xconsumer                      @open-telemetry/collector-approvers @mx-psi @dmathieu
+connector/xconnector                    @open-telemetry/collector-approvers @mx-psi @dmathieu
+exporter/exporterhelper/xexporterhelper @open-telemetry/collector-approvers @mx-psi @dmathieu
+exporter/xexporter                      @open-telemetry/collector-approvers @mx-psi @dmathieu
+processor/xprocessor                    @open-telemetry/collector-approvers @mx-psi @dmathieu
+receiver/xreceiver                      @open-telemetry/collector-approvers @mx-psi @dmathieu

.github/workflows/api-compatibility.yml

@@ -32,7 +32,7 @@ jobs:
           path: ${{ github.head_ref }}
 
       - name: Setup Go
-        uses: actions/setup-go@41dfa10bad2bb2ae585af6ee5bb4d7d973ad74ed # v5.1.0
+        uses: actions/setup-go@3041bf56c941b39c61721a86cd11f3bb1338122a # v5.2.0
         with:
           go-version: ~1.22.9
 

.github/workflows/build-and-test-arm.yml

@@ -30,7 +30,7 @@ jobs:
     runs-on: ${{ matrix.os }}
     steps:
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
-      - uses: actions/setup-go@41dfa10bad2bb2ae585af6ee5bb4d7d973ad74ed # v5.1.0
+      - uses: actions/setup-go@3041bf56c941b39c61721a86cd11f3bb1338122a # v5.2.0
         with:
           go-version: "~1.22.8"
           cache: false