"Versioning support" is the wording from the release notes. I don't know why cargo's version resolution logic can't be applied to git dependencies, treating a tag like "v4.2" or "4.2" as a version 4.2 doesn't seem very contentious. I also don't know what you mean by local git dep.
> I also don't know what you mean by local git dep.
Presumably, the `git` URL for dependencies, in `Cargo.toml`, can point to a local git repository.
That should let you refer to a branch / commit of that repository, other than the one currently checked out (which is what using a `path` dependency would give you).
