From 4f0439f4448b5c42e6c2c62f7f3c90e9795c50c7 Mon Sep 17 00:00:00 2001
From: Toufeeq Pasha <47236805+ToufeeqP@users.noreply.github.com>
Date: Thu, 3 Oct 2024 20:58:04 +0530
Subject: [PATCH] bumped runtime & node version (#674)

---
 node/src/lib.rs        | 2 +-
 runtime/src/version.rs | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/node/src/lib.rs b/node/src/lib.rs
index 10bb0bdf5..6a742311d 100644
--- a/node/src/lib.rs
+++ b/node/src/lib.rs
@@ -7,4 +7,4 @@ pub mod cli;
 pub mod rpc;
 pub mod service;
 
-pub const NODE_VERSION: &str = "2.2.0";
+pub const NODE_VERSION: &str = "2.2.1";
diff --git a/runtime/src/version.rs b/runtime/src/version.rs
index 493b243a4..18b5fb859 100644
--- a/runtime/src/version.rs
+++ b/runtime/src/version.rs
@@ -17,7 +17,7 @@ pub const VERSION: RuntimeVersion = RuntimeVersion {
 	// Per convention: if the runtime behavior changes, increment spec_version
 	// and set impl_version to 0. This paramenter is typically incremented when
 	// there's an update to the transaction_version.
-	spec_version: 38,
+	spec_version: 39,
 	// The version of the implementation of the specification. Nodes can ignore this. It is only
 	// used to indicate that the code is different. As long as the authoring_version and the
 	// spec_version are the same, the code itself might have changed, but the native and Wasm