This is an automated email from the ASF dual-hosted git repository. paulk pushed a commit to branch paulk-asert-patch-1 in repository https://gitbox.apache.org/repos/asf/grails-core.git
commit db825e5701ac4af74c511c86e2c2ba5201d0ebf7 Author: Paul King <[email protected]> AuthorDate: Sat Oct 18 16:16:28 2025 +1000 Fix Gradle bootstrap command in RELEASE.md Typo: Corrected the command for bootstrapping the Gradle project. --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 00c6926fb0..0a88afa85e 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -138,7 +138,7 @@ Example: ### Manual Verification: Reproducible Jar Files After all jar files are verified to be signed by a valid Grails key, we need to build a local copy to ensure the file was built with the right code base. The `very-reproducible.sh` script handles this check, but if the bootstrap needs to be manually bootstrapped, perform the following step: - gradle -p gradle bootstrap + gradle -p gradle-bootstrap Further details on the building can be found in the [INSTALL](INSTALL) document. Otherwise, run the `verify-reproducible.sh` shell script to compare the published jar files to a locally built version of them. @@ -576,4 +576,4 @@ If you wish to fork these workflows, please ensure you update project specific i ## Step 4 - Next Steps After the workflows are setup, they should be tested per this Release document. GitHub releases can be deleted and -recreated as needed to test the release process up to voting. Use the `Release Abort` workflow to rollback as needed. \ No newline at end of file +recreated as needed to test the release process up to voting. Use the `Release Abort` workflow to rollback as needed.
