Merge branch 'dev' into fix/empty_response_handling

CHANGELOG.md

@@ -5,12 +5,17 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/)
 and this project adheres to [Semantic Versioning](http://semver.org/).
 
-## [3.12.0] - 2023-XX-XX
+## [3.12.1] - 2023-XX-XX
+
+### Added
+- Added `failOnEmptyBody` flag for `callServer` to specify wether or not a request should fail if it has no body.
+
+## [3.12.0] - 2023-12-03
 
 ### Added 
 - Support for header-based logger feature
 - Added `risk_start_time` and `enforcer_start_time` fields to enforcer activities.
-- Added `failOnEmptyBody` flag for `callServer` to specify wether or not a request should fail if it has no body.
+
 
 ### Changed
 - Changed the structure of the headers field on async activities to array

README.md

@@ -6,7 +6,7 @@
 [PerimeterX](http://www.perimeterx.com) Shared base for NodeJS enforcers
 =============================================================
 
-> Latest stable version: [v3.11.0](https://www.npmjs.com/package/perimeterx-node-core)
+> Latest stable version: [v3.12.0](https://www.npmjs.com/package/perimeterx-node-core)
 
 This is a shared base implementation for PerimeterX Express enforcer and future NodeJS enforcers. For a fully functioning implementation example, see the [Node-Express enforcer](https://github.com/PerimeterX/perimeterx-node-express/) implementation.
 

package.json

@@ -1,6 +1,6 @@
 {
     "name": "perimeterx-node-core",
-    "version": "3.11.0",
+    "version": "3.12.0",
     "description": "PerimeterX NodeJS shared core for various applications to monitor and block traffic according to PerimeterX risk score",
     "main": "index.js",
     "scripts": {