chore: bump srtool to rust 1.93.0 (port of #1497 to main)#1508
Merged
Conversation
Ports #1497 from release/node-1.0.0 to main. midnight-storage-core 1.2.0-rc.3 pulled in konst 0.4.3, which raised its MSRV to Rust 1.89. The srtool image was pinned to paritytech/srtool:1.88.0-0.18.3, so deterministic runtime WASM builds failed at the cargo dependency check before producing any artifact. Bumping both srtool-build and srtool-info targets to paritytech/srtool:1.93.0-0.18.4 restores the build. Signed-off-by: Giles Cope <gilescope@gmail.com>
Signed-off-by: Giles Cope <gilescope@gmail.com>
ddc8b9b to
a3e09d1
Compare
justinfrevert
approved these changes
May 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Ports #1497 (merged into
release/node-1.0.0) ontomain.midnight-storage-core1.2.0-rc.3 pulled inkonst0.4.3, which raised its MSRVto Rust 1.89. The srtool image was pinned to
paritytech/srtool:1.88.0-0.18.3,so deterministic runtime WASM builds failed at the cargo dependency check before
producing any artifact. Bumping both
srtool-buildandsrtool-infotargets toparitytech/srtool:1.93.0-0.18.4restores the build.The toolchain change shifts the deterministic build baseline — downstream
consumers verifying srtool digests should re-anchor against the new image.
🗹 TODO before merging
📌 Submission Checklist
🧪 Testing Evidence
Same diff as #1497, which has already passed CI on `release/node-1.0.0`.
Local sanity:
```
$ git diff main..HEAD -- Earthfile | diffstat
Earthfile | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
```
🔱 Fork Strategy
Links
Cherry-pick of #1497.