Prepare release 3.17.0

.github/workflows/integration.yml

@@ -13,7 +13,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [20.x]
+        node-version: [22.x]
 
     steps:
     - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/node.js-linux-arm64.yml

@@ -12,7 +12,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [20.x, 22.x, 24.x]
+        node-version: [22.x, 24.x]
 
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/node.js-windows.yml

@@ -13,7 +13,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [20.x, 22.x, 24.x]
+        node-version: [22.x, 24.x]
 
     steps:
     - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/node.js.yml

@@ -14,7 +14,7 @@ jobs:
     strategy:
       matrix:
         os: [ubuntu-latest]
-        node-version: [20.x, 22.x, 24.x]
+        node-version: [22.x, 24.x]
 
     steps:
     - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/npm-publish.yml

@@ -16,7 +16,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
       - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
         with:
-          node-version: 12
+          node-version: 22
       - run: npm ci
       - run: npm test
 
@@ -27,7 +27,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
       - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
         with:
-          node-version: 12
+          node-version: 22
           registry-url: https://registry.npmjs.org/
       - run: npm i
       - run: npm publish

CHANGELOG.md

@@ -2,8 +2,24 @@
 
 ## Unreleased
 
+### 3.17.0 (2026-10-06)
+
+#### Breaking Changes
+
+- Minimum supported Node.js version is now 22.0.0, matching the Azure Monitor OpenTelemetry dependencies.
+- Database telemetry now follows the stable OpenTelemetry database semantic conventions introduced by the updated instrumentations. Dependency names can change from legacy values such as `mongodb.insert` to low-cardinality names such as `insert <collection>` or `createIndexes <namespace>`. Update alerts, dashboards, and queries that match exact database dependency names.
+
+#### Telemetry Changes
+
+- Database spans now use `db.system.name`, `db.namespace`, `db.query.text`, and `db.operation.name` instead of the deprecated `db.system`, `db.name`, `db.statement`, and `db.operation` attributes.
+- `@azure/monitor-opentelemetry-exporter` 1.0.0-beta.46 maps the stable database attributes to Application Insights dependency type, target, and data fields. Attributes consumed by that mapping are no longer duplicated in custom properties.
+- HTTP instrumentation can provide the request method as the span name and carry the path in route or URL attributes. Azure Monitor derives the Application Insights request name from the method and route or URL when those attributes are available.
+
 #### Other Changes
 
+- Updated `@azure/monitor-opentelemetry` to 1.20.1 and `@azure/monitor-opentelemetry-exporter` to 1.0.0-beta.46.
+- Added Azure Container Apps resource detection and programmatic console log severity configuration through the updated Azure Monitor distribution.
+- Included Azure Monitor fixes for performance-counter sampling, resource detector dependencies, `OTEL_BSP_*` environment variable handling, instrumentation lifecycle, Live Metrics recovery, and stable OpenTelemetry database attributes.
 - Updated OpenTelemetry dependencies to stable 2.10.0 and experimental 0.221.0.
 - Refreshed performance harness dependencies to resolve npm audit vulnerabilities.