Pinned dependency with rust-version defined is causing a version downgrade instead of ugprade

[hackaugusto]

With this Cargo.toml:

[package]
name = "example"
version = "0.1.0"
edition = "2021"
rust-version = "1.65"

[dependencies]
winter-utils = { version = "0.5.1", package = "winter-utils" }

and running cargo upgrade --pinned, I get the following:

name                        old req compatible latest new req
====                        ======= ========== ====== =======
winter-utils (winter-utils) 0.5.1   -          0.4.2  0.4.2

The latest version is actually 0.6.4

> cargo upgrade --version
cargo-edit-upgrade 0.12.0
> cargo --version
cargo 1.69.0 (6e9a83356 2023-04-12)

edit: also tested with cargo 1.70.0 (ec8a8a0ca 2023-04-25)

[hackaugusto]

Humm, it seems the behavior is correct. The version 0.4.2 is the latest version of that packaged that is compatible with 1.65, from 0.5.0 it requires 1.67.

It would be nice to be able to use cargo upgrade to bump the rust-version instead of downgrading the dependency. Or to have some sort of message explaining why the downgrade happened.

This is the current full output:

    Updating 'https://github.com/rust-lang/crates.io-index' index
    Checking example's dependencies
name                        old req compatible latest new req
====                        ======= ========== ====== =======
winter-utils (winter-utils) 0.5.1   -          0.4.2  0.4.2
   Upgrading recursive dependencies

[epage]

We normally report why a version is being held back. #857 covers adding that for MSRV.

You can pass in --ignore-rust-version to upgrade anyways.

[hackaugusto]

@epage thank you for the reply! To clarify, the version change was not held back, it was downgraded instead.

I guess this is a duplicate of #857, closing it.