diff --git a/RELEASING.md b/RELEASING.md
index 62a76c9..56e0e96 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -12,15 +12,16 @@
 
 ## Release gradle/actions
 - Create a tag for the release. The tag should have the format `v4.1.0`
-  - From CLI: `git tag v4.1.0 && git push --tags`
+  - From CLI: `git tag -s -m "v4.1.0" v4.1.0 && git push --tags`
+  - Note that we sign the tag and set the commit message for the tag to the newly released version.
 - Go to https://github.com/gradle/actions/releases and "Draft new release"
   - Use the newly created tag and copy the tag name exactly as the release title.
   - Craft release notes content based on issues closed, PRs merged and commits
   - Include a Full changelog link in the format https://github.com/gradle/actions/compare/v2.12.0...v3.0.0
 - Publish the release.
 - Force push the `v4` tag (or current major version) to point to the new release. It is conventional for users to bind to a major release version using this tag.
-  - From CLI: `git tag -f -a -m "v4.0.0" v4 v4.0.0 && git push -f --tags`
-  - Note that we set the commit message for the tag to the newly released version.
+  - From CLI: `git tag -f -s -a -m "v4.0.0" v4 v4.0.0 && git push -f --tags`
+  - Note that we sign the tag and set the commit message for the tag to the newly released version.
 
 ## Post release steps