Skip to content

Commit

Permalink
chore: bump versionize from 0.1.10 to 0.2.0 and rust version
Browse files Browse the repository at this point in the history
Signed-off-by: Yang Kaiyong <[email protected]>
  • Loading branch information
Yang Kaiyong committed Jan 22, 2025
1 parent 1392b84 commit 786d0f2
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/bvt.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ on:
- main
workflow_dispatch:
env:
RUST_VERSION: 1.73.0
RUST_VERSION: 1.84.0
jobs:
build:
name: Build
Expand Down
4 changes: 2 additions & 2 deletions Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "dbs-snapshot"
version = "1.5.1"
version = "1.5.2"
authors = [
"Amazon Firecracker team <[email protected]>",
"Kata Containers Developers",
Expand All @@ -18,7 +18,7 @@ bench = false

[dependencies]
libc = "0.2.117"
versionize = "0.1.10"
versionize = "0.2.0"
versionize_derive = "0.1.5"
thiserror = "1.0.32"
displaydoc = "0.2.4"
Expand Down
4 changes: 2 additions & 2 deletions src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,8 @@
//! Each structure, union or enum is versioned separately and only needs to increment their version
//! if a field is added or removed. For each state snapshot we define 2 versions:
//! - **the format version** which refers to the SnapshotHdr, CRC, or the representation of
//! primitives types (currently we use versionize that uses serde bincode as a backend). The current
//! implementation does not have any logic dependent on it.
//! primitives types (currently we use versionize that uses serde bincode as a backend). The current
//! implementation does not have any logic dependent on it.
//! - **the data version** which refers to the state.
mod persist;
use std::fmt::Debug;
Expand Down

0 comments on commit 786d0f2

Please sign in to comment.