Broken Cargo Update

[haerdib]

A general cargo update or a cargo update -p of substrate-api-client/sgx-runtime/my-node-runtime is currently not possible (see issue integritee-network/sgx-runtime#16).

There's a discussion ongoing about adding a release branch to substrate-api-client (scs/substrate-api-client#141). The question is now what we should do with the worker. In case of changes in the substrate-api-client (or the node or anything that depends on substrate) a cargo update is not possible and will stay impossible as long as substrate includes the version-dev.
If the substrate-api-client offers a release branch, the worker could switch to this branch, but we'd need to add this specific commit to all substrate dependencies within the .tomls..

I can't really see a good solution for this issue.. we have the option of eventual cargo update break intervals or readding commits to the toml..

Or is there a better solution?

[haerdib]

We've decided to upgrade to substarte version 4.0.0-dev : paritytech/substrate@f651d45