Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test(semver): track the behavior of --precise <prerelease> #14013

Merged
merged 1 commit into from
Jun 5, 2024

Commits on Jun 5, 2024

  1. test(semver): track the behavior of --precise <prerelease>

    As of the writing, this test is not the final semantic of pre-release
    semver matching. Part of the behavior is buggy. This test just tracks
    the current behavior of the unstable `--precise <prerelease>`.
    
    The below transformation proposed in the RFC is hard to implement
    outside the semver crate.
    
    ```
    >=1.2.3, <2.0.0 -> >=1.2.3, <2.0.0-0
    ```
    
    The upper bound semantic is also not resolved. So, at least two
    outstanding issues are required to be fixed before the stabilization:
    
    * Bug 1: `x.y.z-pre.0` shouldn't match `x.y.z`.
    * Upper bound: Whether `>=x.y.z-0, <x.y.z` should match `x.y.z-0`.
    
    See the RFC 3493 for the unresolved upper bound issue:
    https://rust-lang.github.io/rfcs/3493-precise-pre-release-cargo-update.html#version-ranges-with-pre-release-upper-bounds
    weihanglo committed Jun 5, 2024
    Configuration menu
    Copy the full SHA
    050f88c View commit details
    Browse the repository at this point in the history