| commit | a7790db68d33637e70790f14fcb65e00d67e8bd8 | [log] [tgz] |
|---|---|---|
| author | Sam Saccone <[email protected]> | Tue Jul 18 22:11:34 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Jul 18 22:11:34 2023 +0000 |
| tree | 04577552a98038f6e3c97091d8c8bb6d2a67f102 | |
| parent | f49397d6e6cfe5eeabe598702b1015c14ebdaf25 [diff] | |
| parent | fe93c0d7f4ecfce3daa6876ae8d9a7c9d00107d6 [diff] |
Move OWNER reference master=>main. am: 317c85ecbb am: e94adfafea am: 04625b3a4c am: 01e6da6a3c am: fe93c0d7f4 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/semver/+/2662746 Change-Id: I492e6edc6caae48b1854b409fb4df67eca5446bf 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.