Skip to content

Latest commit

 

History

History
51 lines (35 loc) · 971 Bytes

RELEASE.md

File metadata and controls

51 lines (35 loc) · 971 Bytes

Tag and Release process

Starting from a state where everything is in master that we want released.

The GitHub Portion

Standard release tag

# npm run script
npm run release

This will ...

  1. bumps the version in _package.json (based on the commit history)
  2. updates CHANGELOG.md for the currnet version
  3. commits package.json and CHANGELOG.md
  4. tags a new release

Pre-Release tag

# npm run script
npm run release -- --prerelease <alpha || beta || rc>

this does the above but tags the version 2.0.1-alpha.0, 2.0.1-beta.0, 2.0.1-rc.0

Push new tag to GitHub

# npm run script
npm run release:tag:v2

this pushes the newly created tag to github

Publish to NPM

# npm run script
npm login
# npm run script
npm run release:publish

this runs the build ( with clean & linting ) and publishes karma-webpack to npm using the latest github tag (created above)