Website: update docs according to the new script

Author: dannywillems

website/docs/developers/updating-ocaml-node.md

@@ -18,58 +18,50 @@ Visit the
 find the latest release version and associated container image tags.
 
 For example, release `3.2.0-alpha1` provides updated container images and
-configuration files.
+configuration files. You'll need:
 
-## 2. Update GCR Links in Code
+- The new version number (e.g., `3.2.0-alpha1`)
+- The 8-character configuration hash from the release page
 
-Use `git grep` to find all Google Container Registry (GCR) references that need
-updating:
+## 2. Automated Update with Script
 
-```bash
-# Search for GCR image references
-git grep "gcr.io/o1labs-192920/mina-daemon"
+OpenMina provides an automation script to handle the bulk of the update process:
 
-# Search for any mina-daemon references
-git grep "mina-daemon"
+```bash
+./website/docs/developers/scripts/update-ocaml-node.sh <old_hash> <new_hash> <old_version> <new_version>
 ```
 
-Update the image tags in the found files to match the new release version.
-Typically this involves changing version strings in Docker Compose files,
-testing configurations, and CI workflows.
+**Example usage:**
 
-## 3. Update Configuration Files
+```bash
+./website/docs/developers/scripts/update-ocaml-node.sh 12345678 87654321 3.1.0 3.2.0-alpha1
+```
 
-Update the configuration file hash to match the new release. The config files
-with the pattern `config_[8-character-hash]` come from the OCaml node release
-and need to be referenced in the OpenMina codebase.
+**Parameters:**
 
-The configuration hash corresponds to the genesis state and network parameters
-for the specific release. You may need to:
+- `old_hash`: Current 8-character config hash
+- `new_hash`: New 8-character config hash from the release
+- `old_version`: Current version (e.g., `3.1.0`)
+- `new_version`: New version (e.g., `3.2.0-alpha1`)
 
-- Update references to the config filename in code to match the new hash
-- Download or reference the new config files from the OCaml node release
-- Verify the new configuration is compatible with OpenMina
+The script automatically updates:
 
-## 4. Example Workflow
+- Configuration file references in testing code
+- Docker image tags in CI workflows and compose files
+- Version strings throughout the codebase
 
-Based on PR #1236, a typical update involves:
+## 3. Manual Verification
+
+After running the script, verify all references were updated correctly:
 
 ```bash
-# 1. Find current references
+# Search for any remaining old references
 git grep "gcr.io/o1labs-192920/mina-daemon"
-git grep "3\.1\.0" # Search for old version numbers
-
-# 2. Update image tags throughout the codebase
-# Replace old tags with new release version
-
-# 3. Search for config file references in code
-git grep "config_"
-
-# 4. Update any hardcoded version references
-git grep -i "mina.*3\.1\.0" # Example for version 3.1.0
+git grep "config_<old_hash>"
+git grep "<old_version>"
 ```
 
-## 5. Verification Steps
+## 4. Verification Steps
 
 After making updates:
 
@@ -80,7 +72,7 @@ After making updates:
    with the updated OCaml node
 5. **CI Pipeline**: Verify that automated testing passes with new versions
 
-## 6. Commit Structure
+## 5. Commit Structure
 
 Following the pattern from PR #1236: