From c2457a7fb283d2bfe1c94ac0c360c27a79bcffd4 Mon Sep 17 00:00:00 2001 From: Daz DeBoer Date: Mon, 23 Mar 2026 17:46:33 -0600 Subject: [PATCH] Update tagging instructions for release --- RELEASING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index 2ae99005..83a960f9 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -20,8 +20,9 @@ - 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 `v5` 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 -s -a -m "v5.0.0" v5 v5.0.0 && git push -f --tags` + - From CLI: `git tag -f -s -a -m "v5.0.0" v5 && git push -f --tags` - Note that we sign the tag and set the commit message for the tag to the newly released version. + - Your HEAD must point at the commit to be tagged. ## Post release steps