Update Substrate dependencies to use crates.io versions about parity-bridges-common

[tomusdrw]

we already do that I believe.

[svyatonik]

we already do that I believe.

I'm not sure - Wwe still have something like that all across the codebase:

[dependencies.frame-support]
version = "2.0.0-rc6"
tag = 'v2.0.0-rc6'
default-features = false
git = "https://github.com/paritytech/substrate/"

[tomusdrw]

I've tried that and it seems that some crates are not really released. It failed for me at substrate-test-runtime-client (CC @gnunicorn )
Afaict it means we can't really use crates.io versions anywhere else because of conflicts.

[svyatonik]

We may just remove this dependency - it isn't super-important. I guess the other missing dependency will be node-primitives, but we should avoid using it. I'm introducing millau-primitives and rialto-primitives in #376 anyway.

But generally, imo, we should switch to crates.io anyway (sooner or later). If we're unable to reuse our own crates from crates.io, then noone can't :)

[gnunicorn]

It failed for me at substrate-test-runtime-client (CC @gnunicorn )

For which crates? I have a todo to fix the releasing process to publish everything that is not marked publish = false rather than matching specific names (as we do now). It seems that at least one or two matches were false and we didn't release a package or two - which I then added after. If you have any other misses, let me know.

I guess the other missing dependency will be node-primitives

Yeah, we are currently not releasing the binaries stuff, mainly because it changes soo often that it feels futile to even try to keep that semver compliant. That said, I have the plan to release at least the primitives and runtimes for both node and polkadot at some point, too.

Either way, even with that dependency missing, if you were to only pull that in via git (using the v2.0.0-tag) and everything else from crates.io should be working. Please let me know if not.