killercup / killercup/cargo-edit

`cargo upgrade` downgrades packages

Open
#875 9 comments 0 reactions 0 assignees View on GitHub
cargo-upgrade
Dominant language
Rust
Stars
3.5k
Forks
166
PR merge metrics
No merged PRs in 30d

Description

For example, here's the output of `cargo upgrade --incompatible=allow --pinned=allow`:

![Screenshot 2023-10-11 at 3 24 23 PM](https://github.com/killercup/cargo-edit/assets/225668/99269941-3e57-4a2f-82f2-37c30f338183)

Note that it incorrectly detects the latest versions of most of the packages.
I have similar behavior with `cargo upgrade --incompatible=allow`.
Also, these commands take about 5 minutes to finish, which seems very slow to me.

FYI, I'm fully up to date as of time of writing (`rustc 1.73.0 (cc66ad468 2023-10-03)` and `cargo-edit-upgrade 0.12.2`.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported behavior with `cargo upgrade --incompatible=allow` and `--pinned=allow`, using the Rust and cargo-edit-upgrade versions noted in the issue. Trace the `cargo upgrade` command's version discovery and timing, then verify that packages select their latest compatible versions and that the commands no longer take about five minutes.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.