Skip to content

Latest commit

 

History

History
25 lines (17 loc) · 908 Bytes

RELEASING.md

File metadata and controls

25 lines (17 loc) · 908 Bytes

Releasing

In order to release a new version, we can follow steps below.

First get a recommended release type by running

npm run version:recommend

This will recommend one of the following release types depending on the commit history: patch, minor or major . We can use the recommended bump to release a new version.

npm run version:bump patch

This command;

  • Runs tests and linters, builds project.
  • Updates version number in package.json.
  • Generates a CHANGELOG based on the latest commits. (See Conventional Changelog)
  • Commits these changes with a message like chore(release): publish %s and creates a new tag with the version number.
  • Pushes all these changes to upstream.

CI/CD will take care of the rest and publish the project to the npm registry and GitHub releases with the newly tagged version.