release @elastic/opentelemetry-node@1.8.0 (#1315)

Author: trentm

RELEASING.md

@@ -27,7 +27,7 @@ Assuming "x.y.z" is the release verison:
 2. Create a PR with these changes:
     - Bump the "version" in "packages/opentelemetry-node/package.json".
     - Run `npm install` in "packages/opentelemetry-node/" to update "packages/opentelemetry-node/package-lock.json".
-    - Update release notes in "docs/release-notes/*" as necessary.
+    - Update release notes in "docs/release-notes/\*" as necessary.
     - Name the PR something like "release @elastic/opentelemetry-node@x.y.z".
 
 3. Get the PR approved and merged.

docs/release-notes/index.md

@@ -29,15 +29,18 @@ To check for security updates, go to [Security announcements for the Elastic sta
 % ### Fixes [edot-node-X.X.X-fixes]
 % *
 
-## version.next [edot-node-next-release-notes]
+## 1.8.0 [edot-node-1.8.0-release-notes]
 
-### Features and enhancements [edot-node-next-features-enhancements]
+### Fixes [edot-node-1.8.0-fixes]
 
-*
+* Fix the handling of the `deactivate_all_instrumentations` [central configuration](elastic-otel-node://reference/edot-node/configuration.md#central-configuration) setting. If the value is `false`, it is now treated the same as if the setting had not been specified in central configuration. This means that `deactivate_all_instrumentations=false` and `deactivate_instrumentations=foo` will result in the "bar" instrumentation *not* being deactivated, which is the intended behavior. Before this change, `deactivate_all_instrumentations=false` would result in the `deactivate_instrumentations` setting being completely ignored. [#1236](https://github.com/elastic/elastic-otel-node/issues/1236)
 
-### Fixes [edot-node-next-fixes]
+### Chores [edot-node-1.8.0-chores]
 
-* Fix the handling of the `deactivate_all_instrumentations` [central configuration](elastic-otel-node://reference/edot-node/configuration.md#central-configuration) setting. If the value is `false`, it is now treated the same as if the setting had not been specified in central configuration. This means that `deactivate_all_instrumentations=false` and `deactivate_instrumentations=foo` will result in the "bar" instrumentation *not* being deactivated, which is the intended behavior. Before this change, `deactivate_all_instrumentations=false` would result in the `deactivate_instrumentations` setting being completely ignored. [#1236](https://github.com/elastic/elastic-otel-node/issues/1236)
+* Update all `@opentelemetry/*` upstream package dependencies to the latest releases:
+    - [`v2.5.0` release](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.5.0) from opentelemetry-js
+    - [`experimental/v0.211.0` release](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.211.0) from opentelemetry-js
+    - [opentelemetry-js-contrib releases](https://github.com/open-telemetry/opentelemetry-js-contrib/releases) up to 2026-01-22
 
 ## 1.7.0 [edot-node-1.7.0-release-notes]
 

packages/opentelemetry-node/package-lock.json

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