Added release.sh for easy release automation and updated README.mds (#146)

* Added release.sh for easy release automation

* Addressed comments

* Addressed comments

* Addressed comments

* Addressed commits

* Addressed commits

* Addressed commits

Author: filip-parity

README.md

@@ -14,8 +14,7 @@ curl -L https://raw.githubusercontent.com/paritytech/foundry-polkadot/refs/heads
 
 This will install `foundryup-polkadot`. Simply follow the on-screen instructions, and the `foundryup-polkadot` command will become available in your CLI.
 
-
-Running `foundryup-polkadot --install v1.1.0-rc3` will automatically install the latest version of the [precompiled binaries](https://github.com/paritytech/foundry-polkadot/releases): forge, cast. For additional options, such as installing a specific version or commit, run `foundryup-polkadot --help`.
+Running `foundryup-polkadot` will automatically install the latest version of the [precompiled binaries](https://github.com/paritytech/foundry-polkadot/releases): forge, cast. For additional options, such as installing a specific version or commit, run `foundryup-polkadot --help`.
 
 ℹ️ Note: if you're using Windows, you'll need to install and use [Git BASH](https://gitforwindows.org/) or [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) as your terminal, since Foundryup currently doesn't support Powershell or Command Prompt (CMD).
 

release-test/README.md

@@ -35,15 +35,27 @@ This folder contains scripts and resources for running comprehensive release tes
 You can specify the Foundry version using the `VERSION` build argument. If omitted, it defaults to `stable`.
 
 ```sh
+cd release-test
 docker build --build-arg VERSION=1.1.0-rc3 -t foundry .
 ```
 
 Or, to use the default `stable` version:
 
 ```sh
+cd release-test
 docker build -t foundry .
 ```
 
+Alternatively, you can get the latest changes from the `master` branch to use the latest version of the `foundry-polkadot` repository:
+
+Comment out the `ENTRYPOINT` line in the `Dockerfile` to use the default entrypoint (and not `ENTRYPOINT ["/bin/sh", "-c"]`).
+
+```sh
+docker build --platform=linux/amd64 -t foundry .
+```
+
+Update `forge.sh` and `cast.sh` under `docker_run()` to use `docker run --platform=linux/amd64` instead of `docker run` to run the commands.
+
 ### 2. Run the Test Scripts
 
 #### Logical Prerequisites for Test Scripts
@@ -105,6 +117,20 @@ docker build -t foundry .
 - **To change the RPC endpoint or test accounts:**  
   Edit the `RPC_URL`, `ADDRESS`, or `PRIVATE_KEY` variables at the top of the scripts.
 
+## How to Run Interactively
+
+If you want to run a command interactively, you can use the following command to get a shell in the container:
+
+```sh
+docker run --rm -it foundry sh
+```
+
+For example, to run `forge --help` in the container while mounted the current `test/` directory:
+
+```sh
+docker run --rm -v $PWD/test:/test -w /test foundry forge --help
+```
+
 ## Notes
 
 - If a script fails, check the output log (`forge.txt` or `cast.txt`) for the last successful command and the error message.

release.sh

@@ -0,0 +1,40 @@
+#!/bin/bash
+
+set -e  # exit on error.
+
+### Check parameters for the new tag.
+
+if [ -z "$1" ]; then
+  echo "Error: No new TAG provided."
+  echo "Example: $0 v1.1.0"
+  exit 1
+fi
+
+TAG="$1"
+
+### Verify and prepare.
+
+git checkout master
+git pull origin master
+
+# git tag -d "$TAG" || true
+# git push --delete origin "$TAG" 2>/dev/null || true
+
+# cargo build --release
+
+### Update CHANGELOG.md.
+
+LATEST_TAG=$(git tag --list 'v*' | sort -V | tail -n 1) # get the latest tag.
+git log --oneline --no-merges "$LATEST_TAG"..HEAD       # get the latest changes.
+# TODO (@filip-parity): Update CHANGELOG.md with the latest changes.
+
+### Update stable tag if needed.
+
+# git push origin :refs/tags/stable           # delete the remote stable tag.
+# git tag -fa stable -m "Update stable tag"   # create or move the local stable tag (force, annotated).
+# git push origin --tags                      # push the new stable tag.
+
+### Create and push version tag.
+
+git tag -a "$TAG" -m "Created release tag $TAG" # create an annotated version tag.
+git push origin "$TAG"                          # push the version tag.