Release v0.22.1

README.md

@@ -131,6 +131,7 @@ Agent runners are recommended to create a [backup](https://github.com/valory-xyz
 ### Skip user prompts
 
 You can optionally pass `--attended=false` or export the environment variable `ATTENDED=false` to skip asking for inputs from the user.
+Note: In this case, if the service is staked, then it will not update the on-chain service, to avoid unstaking. If you choose a staking contract with different parameters (e.g., different bond), then you have to execute the attended mode of the script to update the on-chain service.
 
 ## Observe your agents
 

run_service.sh

@@ -737,7 +737,7 @@ directory="trader"
 service_repo=https://github.com/$org_name/$directory.git
 # This is a tested version that works well.
 # Feel free to replace this with a different version of the repo, but be careful as there might be breaking changes
-service_version="v0.21.0"
+service_version="v0.21.2"
 
 # Define constants for on-chain interaction
 gnosis_chain_id=100
@@ -1027,13 +1027,17 @@ if [ "$local_service_hash" != "$remote_service_hash" ] || [ "$on_chain_agent_id"
     echo ""
 
     response="y"
-    if [ "${USE_STAKING}" = true ] && [ "$ATTENDED" = true ]; then
+    if [ "${USE_STAKING}" = true ]; then
       echo "If your service is in a staking program, updating your on-chain service requires that it is first unstaked."
       echo "Unstaking your service will retrieve the accrued staking rewards."
       echo ""
-      echo "Do you want to continue updating your service? (yes/no)"
-      read -r response
-      echo ""
+      if [ "$ATTENDED" = true ]; then
+        echo "Do you want to continue updating your service? (yes/no)"
+        read -r response
+        echo ""
+      else
+        response="n"
+      fi
     fi
 
     if [[ ! "$response" =~ ^([yY][eE][sS]|[yY])$ ]]; then