Skip to content

Commit

Permalink
docs: add npm publish steps to release/readme (apache#23730)
Browse files Browse the repository at this point in the history
Co-authored-by: Nicolas Charpentier <[email protected]>
Co-authored-by: Evan Rusackas <[email protected]>
  • Loading branch information
3 people authored May 3, 2024
1 parent 3e74ff1 commit 49992dd
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions RELEASING/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -506,3 +506,18 @@ and re-push the proper images and tags through this interface. The action
takes the version (ie `3.1.1`), the git reference (any SHA, tag or branch
reference), and whether to force the `latest` Docker tag on the
generated images.

### Npm Release
You might want to publish the latest @superset-ui release to npm
```bash
cd superset/superset-frontend
```
An automated GitHub action will run and generate a new tag, which will contain a version number provided as a parameter.
```bash
export GH_TOKEN={GITHUB_TOKEN}
npx lerna version {VERSION} --conventional-commits --create-release github --no-private --yes --message {COMMIT_MESSAGE}
```
This action will publish the specified version to npm registry.
```bash
npx lerna publish from-package --yes
```

0 comments on commit 49992dd

Please sign in to comment.