Publish package v3.5.4

Update version number and CHANGELOG.md.

CHANGELOG.md

@@ -1,5 +1,59 @@
 # AppSignal for Node.js Changelog
 
+## 3.5.4
+
+_Published on 2024-11-22._
+
+### Fixed
+
+- Allow Pino transport to be used as a transport. Before, our Pino transport could only be used as a destination:
+
+  ```js
+  import pino from "pino";
+  import { Appsignal, AppsignalPinoTransport } from "@appsignal/nodejs";
+
+  pino(AppsignalPinoTransport({
+    client: Appsignal.client,
+    group: "pino"
+  }));
+  ```
+
+  This meant it was not possible to log both to our transport and to another destination.
+
+  Now, it is also possible to use it as a Pino transport, with the `transport` Pino config option or the `pino.transport()` function:
+
+  ```js
+  import pino from "pino";
+
+  pino({
+    transport: {
+      target: "@appsignal/nodejs/pino",
+      options: {
+        group: "pino"
+      }
+    }
+  });
+  ```
+
+  It is no longer necessary to pass the AppSignal client to the Pino transport. AppSignal must be active for the Pino transport to work.
+
+  By enabling its use as a transport, it is now possible to use it alongside other transports:
+
+  ```js
+  pino({
+    transport: {
+      targets: [
+        // Send logs to AppSignal...
+        { target: "@appsignal/nodejs/pino" },
+        // ... and to standard output!
+        { target: "pino/file" }
+      ]
+    }
+  });
+  ```
+
+  (patch [11b789d](https://github.com/appsignal/appsignal-nodejs/commit/11b789d924788abf97460727da18ab75c611b361))
+
 ## 3.5.3
 
 _Published on 2024-11-07._

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appsignal/nodejs",
-  "version": "3.5.3",
+  "version": "3.5.4",
   "main": "dist/index",
   "types": "dist/index",
   "license": "MIT",