From d0a504d08903bc88b713a9071ed1a0e40c086654 Mon Sep 17 00:00:00 2001 From: Jan Mottl Date: Tue, 10 Dec 2024 17:03:38 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Improve=20RELEASING=20notes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- RELEASING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 5e45b2b..9efd685 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -11,8 +11,8 @@ explains the steps in a great detail. Otherwise you can use TLDR version. 2. Update `CHANGELOG` for the new release. 3. Create a tag for the new BOM version in the required format. 4. Run `prePublishCheck` Gradle task and fix all found issues if needed. -5. If you were forced to publish more artifacts, update `CHANGELOG` and fast-forward the tag to the - latest commit. +5. If you were forced to do some changes, fast-forward the tag to the latest commit. Don't forget + to update `CHANGELOG` if you were forced to publish more artifacts. 6. Push the tag. CI will perform necessary checks and publish all artifacts. ## Long version @@ -40,7 +40,7 @@ Once you are ready to publish new versions of library artifacts, you can start p runs all custom check tasks mentioned above, so you actually do not have to run them separately and you can just run `prePublishCheck`, but it is good to know that they exist and what they do. You can also find more detailed information in the documentation comments in the source code of those tasks. -5. If you were forced to publish more artifacts, update `CHANGELOG` and fast-forward the tag to the - latest commit. +5. If you were forced to do some changes, fast-forward the tag to the latest commit. Don't forget + to update `CHANGELOG` if you were forced to publish more artifacts. 6. Push the tag. CI will perform necessary checks and publish all artifacts.