commit | b7ba4cc8b85841ec26d69031792966c631324c93 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Tue Apr 04 04:30:31 2023 +0000 |
committer | Automerger Merge Worker <[email protected]> | Tue Apr 04 04:30:31 2023 +0000 |
tree | 8d9f6d7719ba1ff0dc5cdbd5c35fea9dfaa2ef8a | |
parent | f5630666471db524f7f41eb75cfc21070ab96c47 [diff] | |
parent | a4d07f6398304bf852f779c5c128a849d16198d5 [diff] |
Snap for 9875146 from 16cf22cc9af59c7544258d8831f0a8aa84be6f8c to udc-release am: a4d07f6398 Original change: https://googleplex-android-review.googlesource.com/c/platform/external/rust/crates/semver/+/22445305 Change-Id: Ib2dce5ca0e285dfd6530089774e368a48cb41f5f Signed-off-by: Automerger Merge Worker <[email protected]>
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.