Wrong readme link resolution for relative paths with workspace readme

[beeb]

Current Behavior

Consider a repository at https://github.com/foo/bar.git.

The README.md file at the root contains the following:

See [this file](./thisfile.md)

The root Cargo.toml contains:

[workspace]
members = ["crates/mycrate"]
resolver = "2"

[workspace.package]
readme = "./README.md"

The crates/mycrate/Cargo.toml:

[package]
# ...
readme.workspace = true

In that case, the README on crates.io will resolve the link to https://github.com/foo/bar/blob/HEAD/crates/mycrate/thisfile.md.

Expected Behavior

The link in the README on crates.io should resolve to https://github.com/foo/bar/blob/HEAD/thisfile.md.

Steps To Reproduce

See setup in the "Current Behavior" section.

Environment

• Browser: N/A
• OS: N/A

Anything else?

The same problem appears with relative images.

[Turbo87]

this is basically the same issue as #9886. since cargo rewrites the Cargo.toml file to readme = "README.md" there is unfortunately not much we can do on our side. my best advice is to not use relative links/URLs if you rely on a README file that is not inside the crate folder.

[beeb]

Oh I see. Thanks for the clarification. This is unfortunate, maybe cargo should rewrite to ../../README.md instead. Is there an open issue on the cargo side for this?

EDIT: Ah I see, cargo first copies the README.md into the root of the crate (alongside the Cargo.toml of the crate) before rewriting the path.