Release
Using GitFlow branching model and tools for Versioning, Semantic Release

standard-version

standard-versionwill do the following:
    1.
    "Bump" the version in package.json
    2.
    Update the CHANGELOG.md file
    3.
    Commit the package.json and CHANGELOG.md files
    4.
    Tag a new release in the git history

standard-version commands

1
npm whoami
2
# create the initial release and create the `CHANGELOG.md`
3
yarn run release --first-release --dry-run
4
# This will tag a release without bumping the version in package.json (et al.).
5
# Cut a Release
6
yarn run release --dry-run
7
# create a pre-release instead of a regular one
8
yarn run release --prereleas --dry-run
9
# cut a new alpha release version
10
yarn run release --prerelease alpha --dry-run
11
# fource a version
12
yarn run release --release-as 1.1.0 --dry-run
Copied!

Developer Workflow

versioning and release
1
# from develop branch start a new release branch (use next version)
2
git flow release start '0.1.4'
3
# on release branch, do any release changes e.g., generate `CompoDoc`
4
# then update CHANGELOG, Bump version and Commit both with:
5
yarn run release
6
# Optionally publish this release (if you have CI actions to do)
7
git flow release publish
8
# now finish release. you have to commit 3 times.
9
git flow release finish
10
# now you are back to develop. push all changes to remote
11
# git push origin --all && git push origin --tags
12
gpoat
Copied!
"release": "standard-version && git push — follow-tags origin master && yarn publish"
Last modified 9mo ago