Add changelog

Signed-off-by: Arthur Silva Sens <[email protected]>

Author: ArthurSens

.chloggen/prometheusreceiver_scope_attributes_spec_compliance.yaml

@@ -0,0 +1,34 @@
+# 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. filelogreceiver)
+component: prometheusreceiver
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Implement scope attributes extraction from `otel_scope_` prefixed labels to comply with updated OpenTelemetry specification"
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [40060]
+
+# (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 OpenTelemetry Prometheus specification has been updated to deprecate the `otel_scope_info` metric 
+  in favor of embedding scope attributes directly in metrics using `otel_scope_` prefixed labels.
+  A new feature gate `receiver.prometheusreceiver.RemoveScopeInfo` controls this behavior:
+  - When enabled (new behavior): scope attributes are extracted from `otel_scope_` prefixed labels on all metrics
+  - When disabled (legacy behavior): scope attributes continue to be extracted from the `otel_scope_info` metric
+  This change maintains backward compatibility while enabling compliance with the updated specification.
+  See: https://github.com/open-telemetry/opentelemetry-specification/issues/4223
+
+# If your change doesn't affect end users or the exported elements of any package,
+# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
+# 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]