Version bumps to Rust 1.74.0 and srtool 0.13.0 (#78)

.github/workflows/manual-acala.yml

@@ -8,7 +8,7 @@ on:
     inputs:
       srtool_tag:
         description: The SRTOOL tag to use
-        default: 1.73.0
+        default: 1.74.0
         required: false
       ref:
         description: The ref to be used for the repo

.github/workflows/manual-fellow-runtimes.yml

@@ -12,7 +12,7 @@ on:
         default: paritytech/srtool
       srtool_tag:
         description: The SRTOOL tag to use
-        default: 1.73.0
+        default: 1.74.0
         required: false
       repo:
         description: The repo to be used to build runtimes from

.github/workflows/manual-moonbeam.yml

@@ -8,7 +8,7 @@ on:
     inputs:
       srtool_tag:
         description: The SRTOOL tag to use
-        default: 1.73.0
+        default: 1.74.0
         required: false
       ref:
         description: The ref to be used for the repo

.github/workflows/manual-polkadot-sdk.yml

@@ -12,7 +12,7 @@ on:
         default: paritytech/srtool
       srtool_tag:
         description: The SRTOOL tag to use
-        default: 1.73.0
+        default: 1.74.0
       repo:
         description: The repo to be used to build runtimes from
         default: paritytech/polkadot-sdk

.github/workflows/manual-shiden.yml

@@ -8,7 +8,7 @@ on:
     inputs:
       srtool_tag:
         description: The SRTOOL tag to use
-        default: 1.73.0
+        default: 1.74.0
         required: false
       ref:
         description: The ref to be used for the repo

.github/workflows/manual.yml

@@ -8,7 +8,7 @@ on:
     inputs:
       srtool_tag:
         description: The SRTOOL tag to use
-        default: 1.73.0
+        default: 1.74.0
         required: false
       srtool_image:
         description: The SRTOOL image to use

.vscode/settings.json

@@ -5,5 +5,6 @@
         "srtool",
         "wbuild",
         "workdir"
-    ]
+    ],
+    "asciidoc.antora.enableAntoraSupport": false
 }

Dockerfile

@@ -3,7 +3,7 @@ FROM docker.io/library/ubuntu:22.04
 LABEL maintainer "[email protected]"
 LABEL description="This image contains tools for Substrate blockchains runtimes."
 
-ARG RUSTC_VERSION="1.73.0"
+ARG RUSTC_VERSION="1.74.0"
 ENV RUSTC_VERSION=$RUSTC_VERSION
 ENV DOCKER_IMAGE="paritytech/srtool"
 ENV PROFILE=release

README.md

@@ -1,4 +1,4 @@
-# Substrate Runtime Toolbox: srtool v0.12.0
+# Substrate Runtime Toolbox: srtool v0.13.0
 
 <figure>
 <img src="resources/srtool-docker_128px.png" alt="srtool docker 128px" />
@@ -20,11 +20,11 @@ The Docker images are tagged with both the rustc version used internally as well
 
 You may find for instance the following:
 
--   `paritytech/srtool:1.73.0-0.12.0`
+-   `paritytech/srtool:1.74.0-0.13.0`
 
--   `paritytech/srtool:1.73.0`
+-   `paritytech/srtool:1.74.0`
 
-The tags not mentioning the build version always point to the latest one. In the example above, `paritytech/srtool:1.73.0` is the same image than `paritytech/srtool:1.73.0-0.12.0`.
+The tags not mentioning the build version always point to the latest one. In the example above, `paritytech/srtool:1.74.0` is the same image than `paritytech/srtool:1.74.0-0.13.0`.
 
 ## Related tools
 
@@ -51,7 +51,7 @@ You may also want to have a look at [subwasm](https://github.com/chevdor/subwasm
 The project was initially developed by <https://gitlab.com/chevdor>.
 It has now moved to Github under the [Parity Technologies](https://www.github.com/paritytech) organisation to simplify the developement and the integration with other Parity products such as Polkadot and Kusama.
 
-The last version hosted on Gitlab has been built using Rust Stable 1.73.0. It is tagged as v0.12.0 and there is no plan on updating the Gitlab repository further. New versions will be available from [this repository](https://www.github.com/paritytech/srtool) only. The functionalities remain the same so you can (and should!) simply swap `chevdor/srtool` for `paritytech/srtool` in your workflows. The [srtool-actions](https://github.com/chevdor/srtool-actions) will remain available as `chevdor/srtool-actions@<version>` and will be updated to point at the paritytech image.
+The last version hosted on Gitlab has been built using Rust Stable 1.74.0. It is tagged as v0.13.0 and there is no plan on updating the Gitlab repository further. New versions will be available from [this repository](https://www.github.com/paritytech/srtool) only. The functionalities remain the same so you can (and should!) simply swap `chevdor/srtool` for `paritytech/srtool` in your workflows. The [srtool-actions](https://github.com/chevdor/srtool-actions) will remain available as `chevdor/srtool-actions@<version>` and will be updated to point at the paritytech image.
 
 ## Install
 
@@ -67,7 +67,7 @@ This method is legacy and deprecated. It is recommended to use the `srtool-cli`
 
 Creating an alias helps hiding the docker complexity behind one simple command. We will see more powerful options but this one is simple enough.
 
-        export RUSTC_VERSION=1.73.0; export PACKAGE=kusama-runtime; alias srtool='docker run --rm -it -e PACKAGE=$PACKAGE -v $PWD:/build -v $TMPDIR/cargo:/cargo-home paritytech/srtool:$RUSTC_VERSION'
+        export RUSTC_VERSION=1.74.0; export PACKAGE=kusama-runtime; alias srtool='docker run --rm -it -e PACKAGE=$PACKAGE -v $PWD:/build -v $TMPDIR/cargo:/cargo-home paritytech/srtool:$RUSTC_VERSION'
 
 Note that defining the alias as done above will hardcode the runtime. Using `kusama-runtime` as shown above means you will **always** check the Kusama runtime. If you need more, check the next chapter.
 
@@ -95,9 +95,9 @@ Invoking `srtool build` with
 
 will output something that looks like this:
 
-        🧰 Substrate Runtime Toolbox - srtool v0.12.0 🧰
+        🧰 Substrate Runtime Toolbox - srtool v0.13.0 🧰
                   - by Chevdor -
-        🏗  Building polkadot-runtime as release using rustc 1.73.0
+        🏗  Building polkadot-runtime as release using rustc 1.74.0
         ⏳ That can take a little while, be patient... subsequent builds will be faster.
         Since you have to wait a little, you may want to learn more about Substrate runtimes:
         https://docs.substrate.io/learn/architecture/
@@ -108,7 +108,7 @@ and finally …​
 
     ✨ Your Substrate WASM Runtime is ready! ✨
     Summary:
-      Generator  : srtool v0.12.0
+      Generator  : srtool v0.13.0
       Version    : null
       GIT commit : 56b9e95a9b634695f59a7c699bc68a5cfb695f03
       GIT tag    : moonriver-genesis
@@ -138,13 +138,13 @@ If you prefer a json output, srtool has you covered:
 The output will look something like:
 
     {
-        "gen": "srtool v0.12.0",
+        "gen": "srtool v0.13.0",
         "src": "git",
         "version": "1.0.0",
         "commit": "85cad2ef48f123d7475385b00d113bc900324ad6",
         "tag": "statemine-v1.0.0",
         "branch": "wk-gh-actions",
-        "rustc": "rustc 1.73.0 (...)",
+        "rustc": "rustc 1.74.0 (...)",
         "pkg": "statemine-runtime",
         "tmsp": "2021-06-22T18:08:50Z",
         "size": "1538747",
@@ -155,7 +155,7 @@ The output will look something like:
         "info": {
           "generator": {
             "name": "srtool",
-            "version": "0.12.0"
+            "version": "0.13.0"
           },
           "src": "git",
           "version": "1.0.0",
@@ -164,7 +164,7 @@ The output will look something like:
             "tag": "statemine-v1.0.0",
             "branch": "wk-gh-actions"
           },
-          "rustc": "rustc 1.73.0 (...)",
+          "rustc": "rustc 1.74.0 (...)",
           "pkg": "statemine-runtime",
           "profile": "release"
         },
@@ -305,7 +305,7 @@ You can see the list of available scripts in the `/scripts` folder:
 
 -   `scan`: Scan a repo for runtimes
 
-The `info` and `version` scripts pass any arguments you pass to the script to `jq`. So you can play with `c` (compact), `-M` (monochrome), `-C` color output. For instance `docker run --rm -it -v $PWD:/build chevdor/srtool:1.73.0 info -cM` shows a monochrome output on a single line.
+The `info` and `version` scripts pass any arguments you pass to the script to `jq`. So you can play with `c` (compact), `-M` (monochrome), `-C` color output. For instance `docker run --rm -it -v $PWD:/build chevdor/srtool:1.74.0 info -cM` shows a monochrome output on a single line.
 
 ## Build your custom chain / parachain
 
@@ -336,7 +336,7 @@ If you mount this docker volume, you will find the wasm on your local filesystem
         # REPO=fellowship-runtimes
         podman run --rm -it \
             -v $REPO:/build \
-            `paritytech/srtool:1.73.0-0.12.0` scan
+            `paritytech/srtool:1.74.0-0.13.0` scan
 
 ## ZSH/ Zinit users
 
@@ -364,6 +364,6 @@ First you may want to double check what rustc versions are available as you will
 
     rustup check
 
-So say you want to build a builder for rustc 1.73.0:
+So say you want to build a builder for rustc 1.74.0:
 
-        RUSTC_VERSION=1.73.0 && docker build --build-arg RUSTC_VERSION=$RUSTC_VERSION -t paritytech/srtool:$RUSTC_VERSION .
+        RUSTC_VERSION=1.74.0 && docker build --build-arg RUSTC_VERSION=$RUSTC_VERSION -t paritytech/srtool:$RUSTC_VERSION .

README_src.adoc

@@ -1,6 +1,6 @@
 :name: paritytech/srtool
-:rsversion: 1.73.0
-:version: 0.12.0
+:rsversion: 1.74.0
+:version: 0.13.0
 // :rsversion: pass:m[include:RUSTC_VERSION[]] // TODO: not working...
 :toc: right
 :sectnums:

RUSTC_VERSION

@@ -1 +1 @@
-1.73.0
+1.74.0

VERSION

@@ -1 +1 @@
-0.12.0
+0.13.0