chore: bump snapshot version for release 1.3.0

Even though no change to snapshot format was introduced,
we need to keep firecracker minor versions and snapshot versions
in one-to-one correspondence. Without the version number, trying
to take a snapshot with `target_version=1.3` would fail, as no
entry for 1.3 was in the version mapping.

Signed-off-by: Patrick Roy <[email protected]>

Author: roypat

src/vmm/src/version_map.rs

@@ -29,6 +29,8 @@ pub const FC_V1_0_SNAP_VERSION: u16 = 4;
 pub const FC_V1_1_SNAP_VERSION: u16 = 5;
 /// Snap version for Firecracker v1.2
 pub const FC_V1_2_SNAP_VERSION: u16 = 6;
+/// Snap version for Firecracker v1.3
+pub const FC_V1_3_SNAP_VERSION: u16 = 7;
 
 lazy_static! {
     // Note: until we have a better design, this needs to be updated when the version changes.
@@ -58,6 +60,11 @@ lazy_static! {
         #[cfg(target_arch = "x86_64")]
         version_map.set_type_version(VcpuState::type_id(), 3);
 
+        // v1.3 - no changes introduced, but we need to bump as mapping
+        // between firecracker minor versions and snapshot versions needs
+        // to be 1-to-1 (see below)
+        version_map.new_version();
+
         version_map
     };
 
@@ -82,6 +89,7 @@ lazy_static! {
         mapping.insert(String::from("1.0.0"), FC_V1_0_SNAP_VERSION);
         mapping.insert(String::from("1.1.0"), FC_V1_1_SNAP_VERSION);
         mapping.insert(String::from("1.2.0"), FC_V1_2_SNAP_VERSION);
+        mapping.insert(String::from("1.3.0"), FC_V1_3_SNAP_VERSION);
 
         mapping
     };