[elastic-observability-automation]

Prepare EDOT Android 1.10.0.

• Bump: minor
• Previous release: v1.9.0
• Included pull requests:
• #906 Prepare for the next release
• #907 fix(deps): update otel-core
• #908 fix(deps): update dependency com.github.gmazzo.buildconfig:com.github.gmazzo.buildconfig.gradle.plugin to v6.1.0
• #904 fix(deps): update Robolectric to 4.17 with required JDK 17+ JVM flags
• #910 fix(deps): update bytebuddy to v1.18.13
• #911 Lower the published consumer toolchain floors
• #913 fix(deps): update android to v9.4.1
• #914 fix(deps): update dependency org.slf4j:slf4j-api to v2.0.20
• #912 fix(deps): update dependency com.github.gmazzo.buildconfig:com.github.gmazzo.buildconfig.gradle.plugin to v6.1.1
• #909 Enhance the release process
• #916 fix(deps): update dependency androidx.annotation:annotation to v1.11.0
• #921 fix(deps): update dependency com.github.gmazzo.buildconfig:com.github.gmazzo.buildconfig.gradle.plugin to v6.1.2
• #918 Derive the release bump from a per-item breaking flag
• #920 fix(deps): update dependency com.diffplug.spotless:spotless-plugin-gradle to v8.10.3
• #919 chore(deps): update gradle to v9.8.0
• #922 Add patch releases to the release automation

Merging this pull request publishes 1.10.0 to Maven Central and the Gradle Plugin Portal and tags the merge commit. Review it, then merge when the checks are green. The automation then opens a second pull request from releasing/1.10.0 into main.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)