Making a Release

If you have commit access to the main repository, the way to make a release depends on what exactly has happened.

• for cosmetic changes, bug fixes, or new features (none of which change the public API of existing code), execute gulp bump to bump the patch section of the version number.
• execute gulp yolo to build the minified package assets, automatically making a commit named after the current version, and automatically pushing the code out to the NPM package repository. Sit back, this takes a while.
• cd to the Primrose-Site directory and execute npm update && gulp yolo

Other things you can do:

• for any changes that break the public API, so long as we're still at 0 for the major version, use gulp bumpMinor to bump the minor version of the project.
• just gulp runs the development build of the site, with a dev server automatically.
• gulp debug performs a full DEV build, without running the watch process to restart tasks, or starting the dev server.
• gulp release performs the full, production build, without making any changes to the package.json or making any commits.
• both debug and release tags can be prefixed with js:, html:, or css: to run the build process for only those parts, e.g. gulp html:debug or gulp js:release.