funkyness surrounding version changes of git packages?

[kairoswater-jason]

I use a handful of git cargo packages. I often update them with cargo update and sometimes even remember to increment the semantic version number.

Sometimes rust-analyzer seems to get stuck on an older version, and nothing I do, even restarting seems to fix it.
(ie. the compiler will use the new version, but rust-analyzer will continue to use the old version giving false warnings and also linking to the wrong file when clicked in something like vscode)

[lnicola]

If restarting r-a fixes it, it's probably a file watching bug. If restarting r-a doesn't fix it, but cargo clean does, it's a Cargo fingerprint issue on our side that's hopefully going to be solved after 1.89.

[kairoswater-jason]

Neither cleaning cargo nor restarting rust-analyzer fixes it, it is permanently stuck, going so far as to delete the local cargo package registry/folder does nothing except make it link to a nonexistant file.

(also vscode >reload window, nor any of the server widget options like restart server)