Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.3.2 #548

Merged
merged 2 commits into from
May 16, 2024
Merged

v1.3.2 #548

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bef083b
v1.3.2
fantkolja May 16, 2024
1a47087
fix
fantkolja May 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 22 additions & 21 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
```
Loading