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.

Sign up for GitHub

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

Jump to bottom

feat(cargo-update): --precise to allow yanked versions #13333

Merged
merged 7 commits into from
Jan 29, 2024
Merged

feat(cargo-update): --precise to allow yanked versions #13333

merged 7 commits into from
Jan 29, 2024

Commits on Jan 21, 2024

  1. refactor(registry): merge called flags into one

    @weihanglo
    weihanglo committed Jan 21, 2024
    Configuration menu
    Copy the full SHA
    70e7868 View commit details
    Browse the repository at this point in the history

  2. refactor: rename items in OptVersionReq 

    * `OptVersionReq::update_precise` to `precise_to`
* `OptVersionReq::UpdatePrecise` to `Precise`
    @weihanglo
    weihanglo committed Jan 21, 2024
    Configuration menu
    Copy the full SHA
    515f6e3 View commit details
    Browse the repository at this point in the history

  3. test(update): demonstrate not able to update --precise <yanked>

    @weihanglo
    weihanglo committed Jan 21, 2024
    Configuration menu
    Copy the full SHA
    4f1e41e View commit details
    Browse the repository at this point in the history

Commits on Jan 22, 2024

  1. feat(cargo-update): --precise to allow yanked versions

    @weihanglo
    weihanglo committed Jan 22, 2024
    Configuration menu
    Copy the full SHA
    3f2f4ed View commit details
    Browse the repository at this point in the history

Commits on Jan 29, 2024

  1. doc(cargo-update): --precise to allow yanked versions

    @weihanglo
    weihanglo committed Jan 29, 2024
    Configuration menu
    Copy the full SHA
    8c392fd View commit details
    Browse the repository at this point in the history

  2. test(cargo-update): verify `--precise <yanked> warns twice 

    This is not ideal and we need to track selected yanked versions.
    @weihanglo
    weihanglo committed Jan 29, 2024
    Configuration menu
    Copy the full SHA
    bc5da43 View commit details
    Browse the repository at this point in the history

  3. fix(cargo-update): once warn once for --precise <yanked> 

    This also tweaks the error message a bit.
    @weihanglo
    weihanglo committed Jan 29, 2024
    Configuration menu
    Copy the full SHA
    caeaaa5 View commit details
    Browse the repository at this point in the history