prepare 0.2.0 release

Releases of virtio-queue and virtio-queue-ser need to happen at the same time because otherwise we won't have a corresponding compatible version in virtio-queue-ser when we release a new version of virtio-queue. Signed-off-by: Andreea Florescu <[email protected]>
rust-vmm · Jun 22, 2022 · 6f18c87 · 6f18c87
1 parent be9d270
commit 6f18c87
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 2 deletions.
diff --git a/crates/virtio-queue-ser/CHANGELOG.md b/crates/virtio-queue-ser/CHANGELOG.md
@@ -1,3 +1,8 @@
+# v0.2.0
+
+- Relax the dependency on `virtio-queue` so that we do not need to publish a release of this crate
+  whenever we have a new release of `virtio-queue`.
+
 # v0.1.0
 
 This is the first release of the crate, compatible with version `0.3.x` of `virtio-queue`.
diff --git a/crates/virtio-queue-ser/Cargo.toml b/crates/virtio-queue-ser/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "virtio-queue-ser"
-version = "0.1.0"
+version = "0.2.0"
 authors = ["rust-vmm AWS maintainers <[email protected]>"]
 description = "Serialization for virtio queue state"
 repository = "https://github.com/rust-vmm/vm-virtio"
@@ -14,5 +14,5 @@ serde = { version = ">=1.0.27", features = ["derive"] }
 versionize = ">=0.1.6"
 versionize_derive = ">=0.1.3"
 # The `path` part gets stripped when publishing the crate.
-virtio-queue = { path = "../../crates/virtio-queue", version = "^0.3.0" }
+virtio-queue = { path = "../../crates/virtio-queue", version = ">=0.4.0" }
 vm-memory = ">=0.8.0"