Merge branch 'main' into feat/confignet-npipe-security-descriptor

Author: swiatekm

.chloggen/codeboten_configoptional.AddEnabledField.yaml

@@ -10,6 +10,7 @@ components:
     - all
     - cmd/builder
     - cmd/mdatagen
+    - cmd/schemagen
     - connector/forward
     - connector/sample
     - docs/rfcs
@@ -31,6 +32,7 @@ components:
     - pkg/config/confignet
     - pkg/config/configopaque
     - pkg/config/configretry
+    - pkg/config/configstorage
     - pkg/config/configtelemetry
     - pkg/config/configtls
     - pkg/confighttp
@@ -103,3 +105,4 @@ components:
     - receiver/sample
     - receiver/sampleentity
     - scraper/sample
+    - scraper/samplemigration

.chloggen/codeboten_rm-UseLocalHostAsDefaultMetricsAddress.yaml

@@ -1,25 +1,28 @@
 # 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: 'bug_fix'
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
 component: cmd/mdatagen
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Fix known acronyms at the end of generated Go identifiers to be all-caps, same as in any other position
+note: Versioned metrics don't handle renamed attributes with same type
 
 # One or more tracking issues or pull requests related to the change
-issues: [15438]
+issues: [15595]
 
 # (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: |
+  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: [user, api]
+change_logs: []

.chloggen/codeboten_rm-confighttp-gate.yaml

@@ -4,24 +4,27 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp)
-component: pkg/pdata
+component: cmd/mdatagen
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add `DisallowUnknownFields` option to `JSONUnmarshaler` in plog, ptrace, pmetric, pprofile, and xpdata to error on JSON fields not defined by the OTLP schema.
+note: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml
 
 # One or more tracking issues or pull requests related to the change
-issues: [15279]
+issues: [15513]
 
 # (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: |
-  When `DisallowUnknownFields` is false (the default), unknown fields are silently ignored, matching the previous behavior.
-  Warning: enabling this option breaks forwards compatibility with future evolutions of the OTLP format, as fields added to the format in newer versions will be rejected as unknown.
+  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.
 
 # 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]
+change_logs: [user, api]