mirror of
https://github.com/rust-vmm/vhost-device.git
synced 2025-12-26 22:48:17 +00:00
Bumps the vhost-device group in /staging with 13 updates: | Package | From | To | | --- | --- | --- | | [anyhow](https://github.com/dtolnay/anyhow) | `1.0.79` | `1.0.80` | | [futures-timer](https://github.com/async-rs/futures-timer) | `3.0.2` | `3.0.3` | | [hermit-abi](https://github.com/hermit-os/hermit-rs) | `0.3.6` | `0.3.8` | | [semver](https://github.com/dtolnay/semver) | `1.0.21` | `1.0.22` | | [syn](https://github.com/dtolnay/syn) | `2.0.49` | `2.0.50` | | [windows-targets](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | | [windows_aarch64_gnullvm](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | | [windows_aarch64_msvc](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | | [windows_i686_gnu](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | | [windows_i686_msvc](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | | [windows_x86_64_gnu](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | | [windows_x86_64_gnullvm](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | | [windows_x86_64_msvc](https://github.com/microsoft/windows-rs) | `0.52.0` | `0.52.3` | Updates `anyhow` from 1.0.79 to 1.0.80 - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.79...1.0.80) Updates `futures-timer` from 3.0.2 to 3.0.3 - [Commits](https://github.com/async-rs/futures-timer/commits/v3.0.3) Updates `hermit-abi` from 0.3.6 to 0.3.8 - [Release notes](https://github.com/hermit-os/hermit-rs/releases) - [Commits](https://github.com/hermit-os/hermit-rs/commits) Updates `semver` from 1.0.21 to 1.0.22 - [Release notes](https://github.com/dtolnay/semver/releases) - [Commits](https://github.com/dtolnay/semver/compare/1.0.21...1.0.22) Updates `syn` from 2.0.49 to 2.0.50 - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/2.0.49...2.0.50) Updates `windows-targets` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) Updates `windows_aarch64_gnullvm` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) Updates `windows_aarch64_msvc` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) Updates `windows_i686_gnu` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) Updates `windows_i686_msvc` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) Updates `windows_x86_64_gnu` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) Updates `windows_x86_64_gnullvm` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) Updates `windows_x86_64_msvc` from 0.52.0 to 0.52.3 - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Commits](https://github.com/microsoft/windows-rs/commits) --- updated-dependencies: - dependency-name: anyhow dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: futures-timer dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: hermit-abi dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: semver dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows-targets dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows_aarch64_gnullvm dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows_aarch64_msvc dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows_i686_gnu dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows_i686_msvc dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows_x86_64_gnu dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows_x86_64_gnullvm dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device - dependency-name: windows_x86_64_msvc dependency-type: indirect update-type: version-update:semver-patch dependency-group: vhost-device ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|---|---|---|
| .. | ||
| vhost-device-video | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| coverage_config_x86_64.json | ||
| README.md | ||
vhost-device staging workspace
This directory includes a separate Cargo workspace to include working vhost-user backend implementations that concern devices that have partial functionality and devices (and/or functionality) not yet ratified in the VIRTIO specification. For more details about vhost-device you can refer to the repository README.
To add a new member crate:
- Place it under this directory,
./staging. - Append its name in the
workspace.membersarray field of the workspace manifest file. - Update the crate list in the repository README.
Testing and Continuous Integration
ℹ️ Notice ℹ️ : The CI runs on the root workspace only.
This means that staging crates can have failing tests and bring down code coverage without automatic checks.
Tests can still be run locally as part of the development process.
To add a crate to the CI, add it to the root Cargo.toml workspace.members array as well as the staging manifest.