fix(tag): set input dependency to correct version

elmariofredo commented 7 years ago

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/wc-catalogue/blaze-elements/blob/master/docs/CONTRIBUTING.md#commit
[x] There are no linting errors and code is properly formatted (your run before push yarn ts:format && yarn ts:lint:fix)
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Wrong version is set in tag/package.json which leads to errors on build See #236 for details

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

elmariofredo commented 7 years ago

I didn't add BREAKING CHANGE: as there is not really any breaking change it's just fixing bad release as someone in the past did release version input 2.0.0 for unknown reason. If you want can add it there but not sure if it's really necessary.

Hotell commented 7 years ago

pls let's read what I've written one more time :) I think we are not on the same page

Hotell commented 7 years ago

as discussed on internal status meeting, we can move forward as release will be resolved within another PR. thanks @elmariofredo

wc-catalogue / blaze-elements

fix(tag): set input dependency to correct version #237