crosvm/common/assertions/Cargo.lock

# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3

[[package]]
name = "assertions"
version = "0.1.0"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> 2022-08-01 22:42:35 +00:00			`# This file is automatically @generated by Cargo.`
			`# It is not intended for manual editing.`
			`version = 3`

			`[[package]]`
			`name = "assertions"`
			`version = "0.1.0"`