From 38e92f86f21e8dbf44533d914c238735679ecdc1 Mon Sep 17 00:00:00 2001
From: Mattias Reichel <mattias.reichel@gmail.com>
Date: Mon, 10 Nov 2025 11:22:40 +0100
Subject: [PATCH 1/2] [skip ci] post 7.0.2 release adjustments

---
 etc/bin/Dockerfile | 2 +-
 etc/bin/verify.sh  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/etc/bin/Dockerfile b/etc/bin/Dockerfile
index 9a630fe50b4..902c3970876 100644
--- a/etc/bin/Dockerfile
+++ b/etc/bin/Dockerfile
@@ -19,7 +19,7 @@
 FROM bellsoft/liberica-openjdk-debian:17.0.17
 
 USER root
-RUN apt-get update && apt-get install -y curl unzip coreutils libdigest-sha-perl gpg vim sudo psmisc locales groovy rsync
+RUN apt-get update && apt-get install -y curl unzip coreutils libdigest-sha-perl gpg vim sudo psmisc locales groovy rsync nano
 
 RUN sed -i -e 's/# en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/locale.gen && \
     dpkg-reconfigure --frontend=noninteractive locales && \
diff --git a/etc/bin/verify.sh b/etc/bin/verify.sh
index 69588380195..6a3a53a44ec 100755
--- a/etc/bin/verify.sh
+++ b/etc/bin/verify.sh
@@ -120,7 +120,7 @@ echo "☑️   3. Verify running the wrapper forge-created app: cd ${DOWNLOAD_LO
 echo "☑️   4. Verify running the cli shell-created app: cd ${DOWNLOAD_LOCATION}/apache-grails-${VERSION}-bin/bin/ShellApp && ./gradlew bootRun --init-script ${DOWNLOAD_LOCATION}/use-staging-repo.gradle"
 echo "☑️   5. Verify running the cli forge-created app: cd ${DOWNLOAD_LOCATION}/apache-grails-${VERSION}-bin/bin/ForgeApp && ./gradlew bootRun --init-script ${DOWNLOAD_LOCATION}/use-staging-repo.gradle"
 echo "☑️   6.1. Add the staging repository ('https://repository.apache.org/content/groups/staging') to the 'build.gradle' file in one of the apps above."
-echo "☑️   6.2. Run 'grails help' inside that app directory."
+echo "☑️   6.2. Run './grailsw help' inside that app directory."
 echo "☑️   6.3. Verify that the scaffolding commands (e.g. 'generate-*') are listed."
 echo "          This confirms that dynamic command resolution is working correctly."
 

From 9154c0cb44081f8e587b3eab2f6fd80a29a6aa44 Mon Sep 17 00:00:00 2001
From: Mattias Reichel <mattias.reichel@gmail.com>
Date: Mon, 10 Nov 2025 13:38:55 +0100
Subject: [PATCH 2/2] [skip ci] update release instructions

---
 RELEASE.md | 24 +++++++++++-------------
 1 file changed, 11 insertions(+), 13 deletions(-)

diff --git a/RELEASE.md b/RELEASE.md
index 21137ed77e2..ac7ee64f505 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -291,24 +291,22 @@ release as published or go to https://reporter.apache.org/addrelease.html?grails
 For example, if the release is out of core with version `7.0.0-M4`, then the release name with be `CORE-7.0.0-M4`. Enter
 the date you moved the distribution artifacts and report the release.
 
-### Deploy grails-forge so the release is accessible on start.grails.org
+### Deploy the release to Grails Forge
 
-On the `grails-core` repository, using the release tag, deploy the grails-forge-web-netty docker container to Google Cloud Run using one of the GCP Deploy actions.
+Publish the released version to [Grails Forge](https://start.grails.org) using one of the [GCP Deploy Actions](https://github.com/apache/grails-core/actions) available in the `grails-core` repository.
 
-On https://start.grails.org, versions are listed in the following order:  RELEASE, NEXT, SNAPSHOT, PREV and PREV-SNAPSHOT.  Use the corresponding action to deploy to each location.
+Grails Forge organizes deployments into version slots as follows:
 
-RELEASE - GA releases only
+- **RELEASE** - GA releases only
+- **NEXT** - Milestones and Release Candidate
+- **SNAPSHOT** - current or next version snapshot
+- **PREV** - previous release version
+- **PREV-SNAPSHOT** - previous version snapshot
 
-NEXT - Milestones and Release Candidate
+Use the action whose name matches the slot you want to deploy to.\
+In the **“Run workflow/Use workflow from”** dropdown, choose the release tag you just created.
 
-SNAPSHOT - current or next version snapshot
-
-PREV - previous release version
-
-PREV-SNAPSHOT - previous version snapshot
-
-The `release` job in the `Release` workflow has a step entitled `🚀 Deploy grails-forge - MANUAL` that will remind you of
-this step.
+(The `release` job in the `Release` workflow includes a step titled `🚀 MANUAL - Deploy Grails Forge` that serves as a reminder to perform the deployment described above.)
 
 ### Publish `grails-core` documentation