Add change log for upcoming release (#1385)

.github/scripts/draft-change-log-entries.sh

@@ -32,6 +32,7 @@ component_names["compressors/"]="Compressors"
 component_names["consistent-sampling/"]="Consistent sampling"
 component_names["disk-buffering/"]="Disk buffering"
 component_names["gcp-resources/"]="GCP Resources"
+component_names["inferred-spans/"]="Inferred spans"
 component_names["jfr-connection/"]="JFR connection"
 component_names["jfr-events/"]="JFR events"
 component_names["jmx-metrics/"]="JMX metrics"

CHANGELOG.md

@@ -2,6 +2,36 @@
 
 ## Unreleased
 
+### AWS resources
+
+- Add ECS cluster detection
+  ([#1354](https://github.com/open-telemetry/opentelemetry-java-contrib/pull/1354))
+
+### Baggage processor
+
+- Add config support
+  ([#1330](https://github.com/open-telemetry/opentelemetry-java-contrib/pull/1330))
+
+### Inferred spans - New 🌟
+
+An OpenTelemetry extension for generating spans via profiling instead of instrumentation.
+This extension enhances traces by running [async-profiler](https://github.com/async-profiler/async-profiler) in wall-clock profiling mode
+whenever there is an active sampled OpenTelemetry span.
+
+The resulting profiling data is analyzed afterward and spans are "inferred".
+This means there is a delay between the regular and the inferred spans being visible
+in your OpenTelemetry backend/UI.
+
+### JFR connection
+
+- Fix for using diagnostic command to start a recording
+  ([#1352](https://github.com/open-telemetry/opentelemetry-java-contrib/pull/1352))
+
+### JMX metrics
+
+- Support both a script and target systems
+  ([#1339](https://github.com/open-telemetry/opentelemetry-java-contrib/pull/1339))
+
 ## Version 1.36.0 (2024-05-29)
 
 ### AWS resources

inferred-spans/README.md

@@ -3,7 +3,7 @@
 OpenTelemetry extension for generating spans via profiling instead of instrumentation.
 This extension enhances traces by running [async-profiler](https://github.com/async-profiler/async-profiler) in wall-clock profiling mode whenever there is an active sampled OpenTelemetry span.
 
-The resulting profiling data is afterwards analyzed and spans are "inferred".
+The resulting profiling data is analyzed afterward and spans are "inferred".
 This means there is a delay between the regular and the inferred spans being visible in your OpenTelemetry backend/UI.
 
 Only platform threads are supported. Virtual threads are not supported and will not be profiled.