From ac0e9f1ef225348e3a664af1e989dbff9d01f604 Mon Sep 17 00:00:00 2001
From: "Mark S. Lewis" <Mark.S.Lewis@outlook.com>
Date: Fri, 18 Jun 2021 08:36:58 +0100
Subject: [PATCH] Release v2.2.7 (#462)

Signed-off-by: Mark S. Lewis <mark_lewis@uk.ibm.com>
---
 CHANGELOG.md             |  6 ++++++
 package.json             |  4 ++--
 release_notes/v2.2.7.txt | 18 ++++++++++++++++++
 3 files changed, 26 insertions(+), 2 deletions(-)
 create mode 100644 release_notes/v2.2.7.txt

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 46eb59821e..cf4e94f6ae 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,9 @@
+## v2.2.7
+Thu 17 Jun 2021 15:44:36 BST
+
+* [b48a1b77](https://github.com/hyperledger/fabric-sdk-node/commit/b48a1b77) [FABN-1714](https://jira.hyperledger.org/browse/FABN-1714): Fix JSDoc generation of Transaction class (#461)
+* [c905a9e5](https://github.com/hyperledger/fabric-sdk-node/commit/c905a9e5) [FABN-1714](https://jira.hyperledger.org/browse/FABN-1714): Allow transactions to be serialized (#459)
+
 ## v2.2.6
 Thu 27 May 2021 09:46:52 BST
 
diff --git a/package.json b/package.json
index 7873d9ec9b..96a9f0c2b7 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "fabric-sdk-node",
-  "version": "2.2.7-snapshot",
-  "tag": "unstable-2.2",
+  "version": "2.2.7",
+  "tag": "latest",
   "main": "index.js",
   "private": true,
   "repository": {
diff --git a/release_notes/v2.2.7.txt b/release_notes/v2.2.7.txt
new file mode 100644
index 0000000000..36f1f1db02
--- /dev/null
+++ b/release_notes/v2.2.7.txt
@@ -0,0 +1,18 @@
+Release Notes
+-------------
+This v2.2.7 version is the latest of the v2.2 long-term support (LTS) release
+of the fabric-node-sdk packages that support Fabric 2.x, and supersedes previous
+v2.x releases. Please see the Fabric LTS release strategy document for more
+information on LTS releases:
+
+https://github.com/hyperledger/fabric-rfcs/blob/main/text/0005-lts-release-strategy.md
+
+Changes in v2.2.7:
+
+- Transaction objects can be serialized using their serialize() method, and
+  later reconstructed using the Contract's deserializeTransaction() method.
+  This allows a transaction to be persisted and resubmitted with the same
+  transaction ID (and nonce) following a client application restart, and may
+  be useful to recover from a client application failure while an in-flight
+  transaction is in an indeterminate state as its commit status has not yet
+  been observed.