I'm trying to use 'cargo publish' to a private registry which uses 'git' (I need to use the dependency a coming from a registry and not directly using the git url as otherwise I have other issues with specifying versions which I cannot do if I refer to the dependency using git url).
I've added a [registry.myregistry] section in .cargo/config.toml of my project, containing the 'index' property pointing to my git repository I plan to use as a registry.
Whenever I run 'cargo publish', I get the following issues:
cargo publish -vvvv -p my_package Updating `myregistry` index Running `git fetch --verbose --force --update-head-ok 'https://...../myregistry.git' '+HEAD:refs/remotes/origin/HEAD'` POST git-upload-pack (321 bytes) From https://..../myregistry.git = [up to date] -> origin/HEAD thread 'main' panicked at 'remote registries must have config', src/cargo/ops/registry/mod.rs:135:13
looks like I'm missing some registry configuration on my side but I can't find what it is.
Does anybody know what is the "remote registry config" cargo publish is complaining about?