commit | 20694561f9e77c49b2d904c38f78d7075f15ce16 | [log] [tgz] |
---|---|---|
author | Andrew Walbran <qwandor@google.com> | Mon Nov 13 22:12:08 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Nov 13 22:12:08 2023 +0000 |
tree | 75e5d94f0bf4521a46efd4cb178cf102d04c6da2 | |
parent | 5150419994efee334c11c81cf53569f2beefc3e5 [diff] | |
parent | 09575c621f115769c5d1b25cf3003746a74022e2 [diff] |
Migrate to cargo_embargo. am: 9d79354ae3 am: 09575c621f Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/semver/+/2828130 Change-Id: I5b5dce56131bd4e19d5afbcb8b93f1648de47714 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
A parser and evaluator for Cargo's flavor of Semantic Versioning.
Semantic Versioning (see https://semver.org) is a guideline for how version numbers are assigned and incremented. It is widely followed within the Cargo/crates.io ecosystem for Rust.
[dependencies] semver = "1.0"
Compiler support: requires rustc 1.31+
use semver::{BuildMetadata, Prerelease, Version, VersionReq}; fn main() { let req = VersionReq::parse(">=1.2.3, <1.8.0").unwrap(); // Check whether this requirement matches version 1.2.3-alpha.1 (no) let version = Version { major: 1, minor: 2, patch: 3, pre: Prerelease::new("alpha.1").unwrap(), build: BuildMetadata::EMPTY, }; assert!(!req.matches(&version)); // Check whether it matches 1.3.0 (yes it does) let version = Version::parse("1.3.0").unwrap(); assert!(req.matches(&version)); }
Besides Cargo, several other package ecosystems and package managers for other languages also use SemVer: RubyGems/Bundler for Ruby, npm for JavaScript, Composer for PHP, CocoaPods for Objective-C...
The semver
crate is specifically intended to implement Cargo's interpretation of Semantic Versioning.
Where the various tools differ in their interpretation or implementation of the spec, this crate follows the implementation choices made by Cargo. If you are operating on version numbers from some other package ecosystem, you will want to use a different semver library which is appropriate to that ecosystem.
The extent of Cargo's SemVer support is documented in the Specifying Dependencies chapter of the Cargo reference.