Currently we don't detect breaking changes from the polkadot-api in a timely manner. This means our master can be broken for a long time without us even realizing. This leads to situations where I want to work on something only to realize after a while that master is already broken.
Implementing a nightly build job that executes a 'cargo update' before compiling could help us to react more quickly.
Niederb
commented
5 months ago
Currently we don't detect breaking changes from the polkadot-api in a timely manner. This means our master can be broken for a long time without us even realizing. This leads to situations where I want to work on something only to realize after a while that master is already broken.
Implementing a nightly build job that executes a 'cargo update' before compiling could help us to react more quickly.