From 20ce680c8942e40c12fe5e799db3ba9fee84e392 Mon Sep 17 00:00:00 2001 From: Daz DeBoer Date: Tue, 9 Jun 2026 19:55:28 -0600 Subject: [PATCH] Update RELEASING.md --- RELEASING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 83a960f9..27c877a0 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -11,16 +11,16 @@ - Note: The gradle actions follow the GitHub Actions convention of including a .0 patch number for the first release of a minor version, unlike the Gradle convention which omits the trailing .0. ## Release gradle/actions -- Create a tag for the release. The tag should have the format `v5.0.0` - - From CLI: `git tag -s -m "v5.0.0" v5.0.0 && git push --tags` +- Create a tag for the release. The tag should have the format `v6.2.0` + - From CLI: `git tag -s -m "v6.2.0" v6.2.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 `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 && git push -f --tags` +- Force push the `v6` 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 "v6.2.0" v6 && 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.