Skip to content

Latest commit

 

History

History
61 lines (40 loc) · 2.02 KB

RELEASE.md

File metadata and controls

61 lines (40 loc) · 2.02 KB
Raw

Webpack merge, tag and release process

Webpack standard Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended workflow for conventional-changelog.

Pull requests into master

  1. When you land commits on your master branch, select the Squash and Merge option.
  2. Add a title and body that follows the conventional-changelog-standard conventions.
  3. Land It!

Cut a standard release

# npm run script
npm run release
# or global bin
standard-version

This will increment the package version based on commit history from the last tag, update the changelog accordingly, commits the changes & cuts a local tag

When satisfied with the local tag, push it up to master.

# commandline
git push --follow-tags origin master

Cut a pre-release

Use the flag --prerelease to generate pre-releases:

Example: Given the last version of the package is 1.0.0, and your code to be committed has semver: patch level changes...

# npm run script ( name === alpha, beta, rc )
npm run release -- --prerelease <name>

this will tag the version 1.0.1-alpha.0

Cut a target release version imperatively like npm version

To forgo the automated version bump use --release-as with the argument major, minor or patch:

Suppose the last version of your code is 1.0.0, you've only landed fix: commits, but you would like your next release to be a minor. Simply do:

# npm run script
npm run release -- --release-as minor

you will get version 1.1.0 rather than the auto generated version 1.0.1.

NOTE: you can combine --release-as and --prerelease to generate a release. This is useful when publishing experimental feature(s).

Signing commits and tags

If you have your GPG key set up, add the --sign or -s flag to your standard-version command.