* Currently we are publishing to `DevVersion/material-builds` for testing purposes and everything seems to work as expected.
* Switching the repository to the `material2-builds` repository on the Angular organization
* When retrieving the last commit message, the script currently pipes it through the head command.
Since the git log command using the less command will exit immediately the pipe will fail with a 141 exit code (because it can't read from a closed stream)
* chore: create build artifacts for each commit
* Switch to new npm package
* Update version to latest
* Publish the builds after all modes succeeded.
* Address comments
* Change snake_case to camelCase
* chore(changelog): properly name tags for github compare links
* The convention changelog currently auto-prefixes the previous semver tag with a `v`, which causes the github compare links to not work.
* Manually resolve the previous and current tag from the git metadata. (As in https://github.com/angular/material/pull/9264)
* Remove prefixed compare links in previous generated chaneglog
* Change `getTags` to `getAvailableTags`
* Add comment explaining how we resolve the tags
> Removes the module ids of the component metadata.
> Since the templates and styles are now inlined, the module id has become unnecessary and
> can cause unexpected issues
This also fixes https://github.com/angular/material2/issues/974 in meanwhile.
* update stage-release to include .metadata.json files
* bump version from alpha.6 to alpha.6-2
* remove test files from packages
* add skipTemplateCodegen option
* add desc to enact-release script
* improve script comments
Change the template regex to support minified js files. This partially addresses inlining resources for an angular-cli prod build.
(cherry picked from commit ba47c8d)
* build: separate demo-app in its own directory.
* chore: replace gulp-inline-resources with a script
This also improves upon the relative path problem. All template paths
now should be relative. Also, we can now include double-quotes in
CSS/HTML.
* The script prepends the new conventional changelog from the latest tag to HEAD.
* When using the `--force` flag, the complete changelog will be generated and overwrites, when present the previous changelog.
Fixes#171.
Closes#179