chore: remove state nodes from standard release process (ethereum#1665)

morph-dev · Feb 4, 2025 · 3b5056d · 3b5056d
1 parent 5c4bbd1
commit 3b5056d
Showing 1 changed file with 2 additions and 5 deletions.
diff --git a/book/src/developers/contributing/releases/deployment.md b/book/src/developers/contributing/releases/deployment.md
@@ -61,11 +61,8 @@ This step directs Ansible to use the current master version of trin. Read [about
 - Run the deployment:
     - Trin nodes:
         - `ansible-playbook playbook.yml --tags trin`
-    - State network nodes (check with the team if there is a reason not to update them):
-        - Recently, we don't regularly deploy state bridge nodes (because they run for a long time and we don't want to restart them). To deploy all other state nodes, use following command:
-            - `ansible-playbook playbook.yml --tags state-network --limit state_stun,state_bootnode,state_regular`
-        - To deploy to all state network nodes:
-            - `ansible-playbook playbook.yml --tags state-network`
+    <!-- - State network nodes (check with the team if there is a reason not to update them):
+            - `ansible-playbook playbook.yml --tags state-network` -->
 - Run Glados deployment: updates glados + portal client (currently configured as trin, but this could change)
     - `cd ../../glados/ansible`
     - `ansible-playbook playbook.yml --tags glados`