Skip to content

Latest commit

 

History

History
29 lines (17 loc) · 1.14 KB

RELEASE.md

File metadata and controls

29 lines (17 loc) · 1.14 KB
Raw

Release

How to publish new releases for this project.

Versioning

semver should be followed when deciding new release versions.

You can either set versions in the package.json files manually, or use the lerna version command to set them via the Lerna CLI. When setting versions manually, you will also need to set the git tags for each package and version. For this reason, it is recommended you use the lerna version command, which will create these tags automatically.

ex: rsocket-adapter-rxjs@1.0.0-alpha.1

Lerna will not push the git tags after creation. You should push the git tags once you are confident in your changes.

Example

lerna version prerelease --sign-git-commit

Publishing

The Test, Build, Release Workflow on GitHub can be run to manually trigger publishing of packages to NPM. This workflow will only publish versions which do not already exist on NPM.

The Test, Build, Release Workflow will:

  • Run automated linting & tests
  • Compile/build various packages
  • Publish built packages to NPM