Skip to content
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.

fix(scripts): Generate semver tag within post-release.sh #263

Merged
merged 1 commit into from
Feb 7, 2017

Conversation

traviskaufman
Copy link
Contributor

This commit modifies post-release.sh to auto-generate a semver tag based
on the highest tagged version of material-components-web by lerna. E.g.,
'[email protected]' would be translated into a v0.4.0 repo
tag.

This mainly addresses the issue where standard-changelog fails to
generate a correct changelog due to lack of semver tags. However, having
an auto-generated semver tag for the entire repo seems useful both for
automated tools relying on semver, and also for non-automated humans
looking to get a general worldview of our latest release :)

Fixes #209
[ci skip]

@traviskaufman traviskaufman requested a review from sgomes February 6, 2017 22:32
This commit modifies post-release.sh to auto-generate a semver tag based
on the highest tagged version of material-components-web by lerna. E.g.,
'[email protected]' would be translated into a `v0.4.0` repo
tag.

This mainly addresses the issue where standard-changelog fails to
generate a correct changelog due to lack of semver tags. However, having
an auto-generated semver tag for the _entire_ repo seems useful both for
automated tools relying on semver, and also for non-automated humans
looking to get a general worldview of our latest release :)

Fixes #209
[ci skip]
@traviskaufman traviskaufman force-pushed the fix/post-release-gen-semver-tag branch from 326dd4b to 83bbe95 Compare February 6, 2017 22:32
Copy link
Contributor

@sgomes sgomes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like your shell-fu :) LGTM!

@traviskaufman traviskaufman merged commit 82c3ffe into master Feb 7, 2017
@traviskaufman traviskaufman deleted the fix/post-release-gen-semver-tag branch February 7, 2017 15:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants