From e237fdb359d56370c457e8042e10d7315ae1d905 Mon Sep 17 00:00:00 2001
From: nyg <nyg@users.noreply.github.com>
Date: Sat, 29 Nov 2025 16:31:50 +0100
Subject: [PATCH] chore(doc): update release process summary

---
 RELEASE.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/RELEASE.md b/RELEASE.md
index 8f1d6ba..f04ad72 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -93,18 +93,21 @@ The `perform` goal is simpler than the `prepare` goal. Its documentation can be
 ## Summary
 
 ```sh
+# stay safe even if the examples module is not published
+rm examples/src/main/resources/api-keys.properties
+
 # dry run
 mvn --serial -Dtag=v2.0.0 -DreleaseVersion=2.0.0 -DdevelopmentVersion=2.0.1-SNAPSHOT -DdryRun release:prepare
 
+# clean after dry run
+mvn release:clean
+
 # prepare release
 mvn --serial -Dtag=v2.0.0 -DreleaseVersion=2.0.0 -DdevelopmentVersion=2.0.1-SNAPSHOT release:prepare
 
 # zsh gitstatusd bug?
 git fetch
 
-# stay safe even if the examples module is not published
-rm examples/src/main/resources/api-keys.properties
-
 # perform release
 mvn --serial clean release:perform
 ```