release @elastic/opentelemetry-node@1.10.0 (#1396)

Author: trentm

docs/release-notes/breaking-changes.md

@@ -42,7 +42,7 @@ Breaking changes can impact your Elastic applications, potentially disrupting no
 % 4. You can then call the link from any Kibana code. For example: `href: docLinks.links.upgradeAssistant.id`
 % Check https://docs.elastic.dev/docs/kibana-doc-links (internal) for more details about the Doc links service.
 
-## version.next [edot-node-X.X.X-breaking-changes]
+## 1.10.0 [edot-node-1.10.0-breaking-changes]
 
 ::::{dropdown} `OTEL_NODE_ENABLED_INSTRUMENTATIONS=fastify,...` will no longer enable Fastify instrumentation
 

docs/release-notes/index.md

@@ -29,25 +29,21 @@ To check for security updates, go to [Security announcements for the Elastic sta
 % ### Fixes [edot-node-X.X.X-fixes]
 % *
 
-## version.next [edot-node-X.X.X-release-notes]
+## 1.10.0 [edot-node-1.10.0-release-notes]
 
-### Features and enhancements [edot-node-X.X.X-features-enhancements]
+### Features and enhancements [edot-node-1.10.0-features-enhancements]
 
+* Because `@opentelemetry/instrumentation-fastify` is no longer being maintained, it has been removed from EDOT Node.js. This matches the removal from `@opentelemetry/auto-instrumentations-node`. See the [breaking changes note for this release](./breaking-changes.md#edot-node-1.10.0-breaking-changes) for details on how to switch to `@fastify/otel` instrumentation.
 * Change the docker image (`docker.elastic.co/observability/elastic-otel-node`), used primarily for [Kubernetes auto-instrumentation with the OpenTelemetry Operator](/reference/edot-node/setup/k8s.md), to run as the `nonroot` user. This allows using EDOT Node.js in with the OpenTelemetry Operator in Kubernetes clusters configured with a strict pod security policy that disallows running as root (`securityContext.runAsNonRoot`).
 
-### Fixes [edot-node-X.X.X-fixes]
-
-### Chores [edot-node-X.X.X-chores]
+### Chores [edot-node-1.10.0-chores]
 
 * Update all `@opentelemetry/*` upstream package dependencies to the latest releases:
     - [`v2.6.1` release](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.6.1) from opentelemetry-js
     - [`experimental/v0.214.0` release](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.214.0) from opentelemetry-js
     - [opentelemetry-js-contrib release](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/3415)
       - Notably, [`@opentelemetry/instrumentation-fastify` is no longer being updated](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/3409), in favor of `@fastify/otel`.
 
-* Because `@opentelemetry/instrumentation-fastify` is no longer being maintained, it has been removed from EDOT Node.js. This matches the removal from `@opentelemetry/auto-instrumentations-node`. See the [breaking changes note for this release](./breaking-changes.md) for details on how to switch to `@fastify/otel` instrumentation.
-
-
 ## 1.9.0 [edot-node-1.9.0-release-notes]
 
 ### Features and enhancements [edot-node-1.9.0-features-enhancements]

packages/opentelemetry-node/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@elastic/opentelemetry-node",
-  "version": "1.9.0",
+  "version": "1.10.0",
   "type": "commonjs",
   "description": "Elastic Distribution of OpenTelemetry Node.js (EDOT Node.js)",
   "publishConfig": {