From 0e270825984ef2ae0ff2e8488666f708702779ea Mon Sep 17 00:00:00 2001 From: Mykola Fant Date: Thu, 16 May 2024 18:42:49 +0300 Subject: [PATCH] v1.3.2 (#548) * v1.3.2 * fix --- README.md | 43 ++++++++++++++++++++++--------------------- 1 file changed, 22 insertions(+), 21 deletions(-) diff --git a/README.md b/README.md index 2c76934f0..11220207d 100644 --- a/README.md +++ b/README.md @@ -195,35 +195,36 @@ Assuming you're on latest master and the build is alright (`pnpm run build` runs 1. First we create a release branch for the next version locally (in this case v1.1.0): -``` -git checkout -b release/v1.1.0 -``` + ``` + git checkout -b release/v1.1.0 + ``` -We push this new branch to Github: + We push this new branch to Github: -``` -git push -u origin release/v1.1.0 -``` + ``` + git push -u origin release/v1.1.0 + ``` -2. Then we run `lerna version`: - This updates the package versions (in package.json, package-lock.json), creates a commit with necessary tags and pushes to Github automatically. +2. Then we run: -``` -pnpm exec lerna version 1.1.0 -``` + ``` + pnpm exec lerna version 1.1.0 + ``` -At this point you should create a pull request and merge the new version branch (v1.1.0) to master. + This updates the package versions (in package.json, package-lock.json), creates a commit with necessary tags and pushes to Github automatically. + + At this point you should create a pull request and merge the new version branch (v1.1.0) to master. 3. Now, after merging this pull request, we have the latest version available on GitHub. And it will be automatically published to npm with the required tags and releases; -Wait for a few seconds/minutes (depends on how busy npm is at the time), and you should see the latest version we just released in the list returned by: + Wait for a few seconds/minutes (depends on how busy npm is at the time), and you should see the latest version we just released in the list returned by: -``` -pnpm view @hazelcast/ui versions -``` + ``` + pnpm view @hazelcast/ui versions + ``` -If something went wrong and npm did not create a new release, then you can manually inform it about our new release: + If something went wrong and npm did not create a new release, then you can manually inform it about our new release: -``` -pnpm exec lerna publish from-git -``` + ``` + pnpm exec lerna publish from-git + ```