3.47.0 (#3429)

Author: david-luna

CHANGELOG.asciidoc

@@ -31,18 +31,18 @@ Notes:
 [[release-notes-3.x]]
 === Node.js Agent version 3.x
 
-==== Unreleased
-
-[float]
-===== Breaking changes
+[[release-notes-3.47.0]]
+==== 3.47.0 - 2023/06/14
 
 [float]
 ===== Features
 
-* Add support for 'knex' version v1 and v2. ({pull}3355[#3355])
+* Add support for `knex` version v1 and v2. ({pull}3355[#3355])
+
 * Add `[email protected]` support. ({pull}3366[#3366])
-* Add `apm.setGlobalLabel()` to dynamically extend the `globalLabels` set in the initial config.
-  Refer to <<apm-set-global-label>> for details. ({pull}3337[#3337])
+
+* Add `apm.setGlobalLabel()` to dynamically extend the `globalLabels` set in
+  the initial config. Refer to <<apm-set-global-label>> for details. ({pull}3337[#3337])
 
 [float]
 ===== Bug fixes

docs/agent-api.asciidoc

@@ -294,7 +294,7 @@ Defining too many unique fields in an index is a condition that can lead to a
 [[apm-set-global-label]]
 ==== `apm.setGlobalLabel(name, value)`
 
-[small]#Added in: REPLACEME#
+[small]#Added in: v3.47.0#
 
 * `name` +{type-string}+
 * `value` +{type-string}+ | +{type-number}+ | +{type-boolean}+

docs/set-up.asciidoc

@@ -100,7 +100,7 @@ import 'elastic-apm-node/start.js';
 
 A limitation of this approach is that you cannot configure the agent with an options object, but instead have to rely on <<configuring-the-agent,one of the other methods of configuration>>, such as setting `ELASTIC_APM_...` environment variables.
 
-Note: As of elastic-apm-node version REPLACEME, the "elastic-apm-node/start.js" will *not start the agent in a Node.js Worker thread.*
+Note: As of elastic-apm-node version 3.47.0, the "elastic-apm-node/start.js" will *not start the agent in a Node.js Worker thread.*
 
 
 [[start-option-node-require-opt]]
@@ -122,7 +122,7 @@ export NODE_OPTIONS='-r elastic-apm-node/start.js'
 node app.js
 ----
 
-Note: As of elastic-apm-node version REPLACEME, the "elastic-apm-node/start.js" will *not start the agent in a https://nodejs.org/api/worker_threads.html[Node.js Worker thread].* New Worker threads inherit the `process.execArgv` and environment, so "elastic-apm-node/start.js" is executed again. Starting a new APM agent in each Worker thread because of "start.js" is deemed surprise, so is disabled for now.
+Note: As of elastic-apm-node version 3.47.0, the "elastic-apm-node/start.js" will *not start the agent in a https://nodejs.org/api/worker_threads.html[Node.js Worker thread].* New Worker threads inherit the `process.execArgv` and environment, so "elastic-apm-node/start.js" is executed again. Starting a new APM agent in each Worker thread because of "start.js" is deemed surprise, so is disabled for now.
 
 
 [[start-option-separate-init-module]]

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "elastic-apm-node",
-  "version": "3.46.0",
+  "version": "3.47.0",
   "description": "The official Elastic APM agent for Node.js",
   "main": "index.js",
   "types": "index.d.ts",