Skip to content

Conversation

@falsyvalues
Copy link

@jeremypeter
Copy link
Contributor

@falsyvalues This really isn't needed since we're using the caret range, ^2.0.0, which will update users to v2.1.2 of email-builder-core

@falsyvalues
Copy link
Author

falsyvalues commented Dec 6, 2018

@jeremypeter I'm aware of that but since it suggests also version that shouldn't be used I recommend to change it. It will also cover < 3.0.0 scenario but it won't allow affected version (npm caret ranges).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants