You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Waiting for .22 would likely be optimal to reduce amount of changes, despite .21 seeming fine if we don't use SGX (we do not). Just a minor tracking issue here.
Labelled substrate yet technically applies to ethers as well. cargo update should resolve all when the time comes.
The text was updated successfully, but these errors were encountered:
It looks like this advisory was actually withdrawn, and I do not mean to draw negative attention to chrono, yet solely keep things as pristine as possible over here. If GH didn't ping everyone all the time, I wouldn't have...
chronotope/chrono#674 for the original security issue, which pinged for us and still does (though it may not apply).
chronotope/chrono#755 and chronotope/chrono#770 for the .20/.21 issues.
Waiting for .22 would likely be optimal to reduce amount of changes, despite .21 seeming fine if we don't use SGX (we do not). Just a minor tracking issue here.
Labelled substrate yet technically applies to ethers as well.
cargo update
should resolve all when the time comes.The text was updated successfully, but these errors were encountered: