-
Notifications
You must be signed in to change notification settings - Fork 1
how to release new version
David Sklář edited this page Nov 3, 2017
·
1 revision
It's strongly recommended following the SemVer guidelines.
Release new version means:
- bump package version in relevant files,
- update CHANGELOG according to Git commit message conventions,
- commit, tag and push the change to origin.
-
Run grunt release task;
grunt release
-
Set SemVer
path
/minor
/major
level -
Refuse
commit/tag/push
option (if you want to extend CHANGELOG in next step) -
Update or extend generated CHANGELOG
-
Finish the release task with
commit/tag/push
grunt bump-commit
-
Provide version codename;
That's optional (leave it blank), recommended for major release