This is an automated email from the ASF dual-hosted git repository.

jamesfredley pushed a commit to branch two-manual-final-release-steps
in repository https://gitbox.apache.org/repos/asf/grails-core.git

commit a442297b38c9975e02b3e97be34bd84a365086cf
Author: James Fredley <[email protected]>
AuthorDate: Mon Nov 24 12:54:20 2025 -0500

    Add manual steps for release workflow
    
    Added manual steps for blog post creation, merging release PR, and 
deploying SNAPSHOT to Forge.
---
 .github/workflows/release.yml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 566d690d2a..3018661b17 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -637,6 +637,16 @@ jobs:
           echo "::group::Blog Post Creation - MANUAL"
           echo "Publish a blog post on https://grails.apache.org/blog/ about 
the new release [${VERSION}] using the repo 
https://github.com/apache/grails-static-website";
           echo "::endgroup::"
+      - name: "🌎 MANUAL - Merge Close Release PR"
+        run: |
+          echo "::group::Merge Close Release PR - MANUAL"
+          echo "The last step in the grails-core release workflow will create 
a merge branch for the original tag with version number and then open a PR to 
merge back into the next branch. You will need to merge this PR into the branch 
after correcting any merge conflict."
+          echo "::endgroup::"
+      - name: "🌎 MANUAL - deploy the new SNAPSHOT to Forge"
+        run: |
+          echo "::group::Deploy the new SNAPSHOT to Forge - MANUAL"
+          echo "After the Close Release PR is merged, deploy the new SNAPSHOT 
to Forge via: 
https://github.com/apache/grails-core/actions/workflows/forge-deploy-snapshot.yml";
+          echo "::endgroup::"
       - name: '📧 Announcement Email'
         run: |
           echo "::group::Announcement Email"

Reply via email to