Closed Daanvdplas closed 1 week ago
Can you please explain in more detail what your problem was? I don't get it based on the current description. Sorry
My bad, apologies!
The last upgrades we have done we had to set the specific version of certain crates in the Cargo.lock
file.
Upgrading to stable gave us this issue for example:
Which required us to bump the patch version of one of the rococo-runtime
related packages
During the 1.13 upgrade we were facing similar issues as described here: https://substrate.stackexchange.com/questions/11774/unable-to-compile-upgrade-parachain-node-after-running-psvm-v1-13-0/11775#11775 & https://substrate.stackexchange.com/questions/11781/frame-support-cannot-find-vec-when-upgrade-to-sdk-1-13
I can still not really follow. Next time the best would be that you directly report these issues, maybe some crate was not released properly or whatever. However, if you don't exactly know how you solved your issues, we can also not fix them. Sorry.
Will make a proper issue next time. Apologies for wasting your time!
You didn't wasted my time :) Better to ask than us not improving this!
The last upgrades (1.13 - stable) we have done for our parachain projects have all been suffering the fact that we had to update certain packages in the
Cargo.lock
file. This is a tedious effort and bad developer experience.Is there a way we can prevent this? It seems like this shouldn't be the case as prior upgrades didn't require this.