| commit | 95b2e0a59e4e968f8233b44b181e26214930451b | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Sat Aug 31 01:14:56 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Sat Aug 31 01:14:56 2024 +0000 |
| tree | f6bc5adbb77666f7eba851b3188d736d1757bb04 | |
| parent | bb3755e32a4e64bbd028ab132b50df9fb8e738fc [diff] | |
| parent | 55bd0337c680eec273f32555e2d8c67147caccc1 [diff] |
Snap for 12304452 from 55bd0337c680eec273f32555e2d8c67147caccc1 to 24Q4-release Change-Id: I7c9b5ee701e2753fbb48c130b595cc9ede1d6d61
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.