Closed wischli closed 1 year ago
Thanks for reporting this issue @wischli.
I am still checking but I am pretty confident the issue is NOT on your side. There are several ways to use srtool and I think this problem only occures when using the default output.
The issue is related to subwasm
no longer reporting the version as a string. You can see the fix I did in the polkadot release note. A similar fix is required in the default templates of srtool.
Using
paritytech/srtool:1.64.0-0.9.23
, the version numbers of our WASMs are unfortunately not stringified properly and just displayed as[object]
instead of displaying the spec version:Since others haven't posted this issue yet, it appears to be something off on our side. However, in
1.60.0
it worked fine. We upgraded from 1.60.0 to 1.64.0 roughly a month ago.Any help would be appreciated!
Update: Running
subwasm v0.18.0
works fine:Our environment