Merge pull request #1419 from o1-labs/dw/clean-doc-release

Website/release: update documentation following first concrete release

Author: dannywillems

website/docs/appendix/release-process.mdx

@@ -281,14 +281,7 @@ git checkout main
 git pull origin main
 
 # Create and push annotated tag
-make release-create-tag TAG=v1.5.0 MESSAGE="Release v1.5.0
-
-## Highlights
-- Feature 1: Description
-- Feature 2: Description
-- Bug fix: Description
-
-See CHANGELOG.md for complete details."
+make release-create-tag TAG=v1.5.0 MESSAGE="Release v1.5.0. See CHANGELOG.md for complete details."
 ```
 
 <!-- prettier-ignore-start -->
@@ -401,17 +394,6 @@ make release-merge-back
 
 This target includes safety confirmations since it pushes directly to develop.
 
-### Tag Docker Images as Latest (for major releases)
-
-For major releases, you may want to tag as `latest`:
-
-```bash
-# This would typically be done via additional CI job or manually
-docker pull o1labs/mina-rust:v2.0.0
-docker tag o1labs/mina-rust:v2.0.0 o1labs/mina-rust:latest
-docker push o1labs/mina-rust:latest
-```
-
 ## Hotfix Process
 
 For urgent patches to released versions:

website/docs/developers/scripts/release/merge-back.sh

@@ -12,9 +12,12 @@ if [ "$confirm" != "y" ] && [ "$confirm" != "Y" ]; then
 fi
 
 echo "Merging main back to develop..."
+BRANCH_NAME=tmp-merge-branch-"$(date +%s)"
 git checkout develop
 git pull origin develop
+git checkout -b "${BRANCH_NAME}"
 git merge main --no-edit
-git push origin develop
+git push origin "${BRANCH_NAME}"
+gh pr create --title "Merge main back to develop" --body "Automated merge of main into develop." --base develop --head "${BRANCH_NAME}"
 
-echo "Successfully merged main back to develop"
+echo "Successfully merged main back to develop"