Since substrate-specific dependencies are used throughout the workspace, they could be added as workspace-level dependencies. This would make updating them easier (as versions, etc. are changed at a single point) and would reduce boilerplate. We should also check whether subxt can be updated (but that requires changes to the oracle code, due to breaking changes they introduced in the last update).
Solution
[x] check what dependencies would make sense to include at workspace level
[x] try to update dependencies to the latest published version (instead of using git deps)
[x] try to update subxt to use the published version instead of our fork (this requires some thought on the wasm side)
[x] remove the unused (accidentally pushed to main) hashbrown dependency from pallet-guild
Description
Since substrate-specific dependencies are used throughout the workspace, they could be added as workspace-level dependencies. This would make updating them easier (as versions, etc. are changed at a single point) and would reduce boilerplate. We should also check whether
subxtcan be updated (but that requires changes to the oracle code, due to breaking changes they introduced in the last update).Solution
hashbrowndependency frompallet-guildmock.rsfor each pallet