Releasing a new version
A GH Action allows you to create a new release of @elastic/charts thanks to semantic-release: the release version and change logs will be automatically generated from the commits available in master between the latest release tag and the current HEAD. This procedure will publish the new version in the NPM registry.
To release: Go to Actions -> Publish release -> Run Workflow on master branch and press Run
The same GH Action used to publish a new release can be used to publish a backported PR by selecting the backported branch in the Run Workflow dropdown menu.
If a bad package was released (e.g. with wrong semantic versioning due to badly formatted commits) you can follow these steps:
- Delete the release in GH
- Delete the tag in GH
- Unpublish package version
npm unpublish @elastic/[email protected] - Remove the latest commit, the one auto-generated by the release
- Interactive rebase and reword bad commit, force push
upstream
Steps 1-3 are used to remove the old version, these are required to release the same version. In this case, it was not needed but good to remove all traces of the bad version.
Notes:
The unpublish command only works shortly after release, depending on the time since release and the number of package downloads. If unpublish doesn’t work just use the npm deprecate. These commands are only available to select Elastic users.